Your screen
Accessibility powers on-screen help. You control the permission in Android Settings.
Privacy, in plain language.
A readable summary of Surf’s practices and boundaries. Final legal details are still being prepared.
Your secrets
Passwords and OTPs use secure input and are never sent to the model.
Your approval
Anything that spends money needs a tap-to-approve pay card.
1.The short version
Surf is designed to help with tasks across Android apps. This draft summarizes the practices supplied for this preview: sensitive information is redacted before AI calls; passwords and OTPs are never sent to the model; payments require approval; user data is not used for training.
2.Screen access and permissions
With Accessibility permission, Surf can read screen content and tap or type for you. You control this permission in Android Settings and can revoke it. Surf may need your help with restricted screens, authentication or verification.
3.Sensitive input and AI calls
Sensitive data is redacted before AI calls. OTPs and passwords use secure input and are never sent to the model. Do not enter secrets in this website’s demonstration forms.
4.Payments and your control
Before spending, Surf asks you to review the merchant, items and total on a tap-to-approve card. No approval means no payment.
5.Training and learning
Surf does not train on user data. The research notes discuss general task patterns as a development direction, not permission to reuse your personal content.
6.This website and open details
Forms on this static preview are not connected and do not send or save submissions. Google Fonts and optional animation libraries are loaded from external providers. Exact service providers, retention periods, deletion processes and the verified privacy contact still need to be completed and legally reviewed before launch.