Theme
Data and privacy policy
The data collected depends on the features the app uses.
| Category | Data examples |
|---|---|
| Account | Name, email, phone number, billing address, password hash, and session data |
| App | Domain, appearance, menu, store materials, releases, and plan |
| Payments | Invoices, amounts, statuses, and transaction IDs; Stripe processes card details |
| Push | Installation identifier, FCM token, platform, version, and last activity |
| Analytics | Event type and time, identifier and IP hashes, country, device, URL, and additional parameters |
Do not send names, contact details, passwords, tokens, payment details, exact coordinates, or user message contents to analytics, URLs, or additional parameters.
Privacy policy
Under “Distribution”, you can generate a standard privacy policy and terms of use. Before publication, check the owner's legal name, actual data categories and processing purposes, providers, countries and retention periods, age restrictions, support contact, and account deletion method.
Review the template after adding permissions, analytics, payments, advertising, or third-party services.
Data deletion
End-user accounts, orders, and profiles are usually stored on the connected website. The app owner must provide a deletion method through settings or support. Uninstalling the app from a phone does not delete the website account.
SiteCargo may store technical installation, push, and analytics data. To delete or anonymize it, the app owner submits a support request after securely verifying the user. Do not ask users to send a password, cookie, or full FCM token.
Deleting the SiteCargo owner's account and handling an end-user request are separate operations. Financial and operational documents may be retained beyond the specified period for operational or legal reasons.