SMS and OTP

SMS and OTP features are highly platform-dependent. Treat them as convenience workflows, not as a guaranteed replacement for your system's native OTP autofill.

What to expect

• Android may support SMS-related source detection or quick extraction depending on permissions and version.
• iOS is more restrictive and may require manual sharing, shortcuts, or foreground actions.
• Desktop platforms usually receive SMS/OTP content only after it is copied, shared, or synced from another device.

Privacy boundary

OTP codes are sensitive. Use short retention, delete after use, and avoid syncing OTP content if your threat model requires local-only handling.

Troubleshooting

1. Confirm the platform supports the SMS/OTP path you are using.
2. Confirm required permissions are granted.
3. Copy a test code manually and verify it appears in Clip History.
4. Check whether filters are excluding SMS-like content.

Related: SMS source and Privacy and Security.