Privacy overview
A clear overview of the account, wallet, order, and support data the product needs in order to operate safely.
Early-stage note. This page is intentionally written as a readable product-level privacy overview rather than an inflated policy wall.
What we store
SFollowr stores the account, authentication, wallet, order, remediation, and support data needed to operate the product and answer customer questions.
- Account details such as email and profile information.
- Authentication and session records needed to keep sign-in secure.
- Wallet, top-up, and order records tied to the customer account.
- Support tickets and customer-safe remediation history.
How the data is used
The product uses this data to run the customer experience: access control, wallet funding review, order handling, status visibility, remediation eligibility, and support workflows.
Staff tools can access more operational context than the customer UI, but the customer surface stays intentionally filtered and buyer-safe.
Access separation
Customer, support, ops, and admin areas are separated. Public and customer-facing pages do not expose provider names, raw provider payloads, route logic, or other staff-only internals.
- Customer pages show only customer-safe order and support context.
- Staff tools are role-protected and scoped to the user’s access level.
- Operational and provider details remain out of the public marketing surface.
Retention and requests
Data is retained for as long as it is needed to operate the account, preserve truthful order and wallet history, support audits, and respond to customer or legal requests.
If you want something reviewed or removed, contact support and the request can be handled through the live support flow according to product and legal constraints.
Policy updates
This page is a plain-language overview of the current product behavior. It may evolve as the live customer experience, support process, or operational tooling changes.