Privacy notice
How Sitalyst handles information in its local demo and how to raise a privacy concern.
This information describes the current demo. The public launch policies will be reviewed against the live service.
Who runs Sitalyst
ReportStudio Ltd is the proposed operator. Registration and business contact details have not been confirmed. See Contact and support for current details.
Reports and local drafts
JSON imports and local backups are read in your browser. If you choose connected storage, Sitalyst processes the shared report and evidence in server memory to validate and transfer them to your drive; it does not persist their contents or client names in its database.
Google Drive and OneDrive connections use a dedicated app folder. Encrypted connection tokens, file identifiers, revision hashes and review decisions are stored in Supabase. Anyone with the required agency permissions can access shared files through Sitalyst. Disconnecting deletes our saved token and pauses schedules; it does not delete your drive files or revoke the provider’s account grant.
If you run a URL audit, the public page address is sent to Google PageSpeed Insights. Query strings and fragments are removed.
We encrypt the Google API key you connect and use it to request audits from Google. You can remove it in your account settings.
Opt-in monitoring stores the selected website URL, device, schedule and metric summaries in Supabase. Each check uses three requests from your own PageSpeed key and saves full audits in your drive. Up to 30 results per schedule, ten revision records per project and 50 review events per project are retained. Removing a schedule deletes its monitoring metadata, while drive files remain. Local data stays until you or your browser delete it. See Cookies and browser storage for browser storage.
Account and demo access
If you create an account, log in or request a password reset, Supabase processes the email address and any password you submit to provide the account, verify your email, and manage your sign-in. The optional studio name is stored with your account. Supabase sends the confirmation and reset emails.
When you use account tools, we store your browser type, a hashed browser identifier, and last use to manage registered browsers. We also store referral codes and attribution, agency names, memberships, and team invitation email addresses to manage workspaces. For signed-in agencies, Supabase also stores shared branding and reusable templates. Store client details in local projects only.
Agency demo invite addresses may be saved locally if you submit an invite. Use example details in the demo. It sends no agency invitation emails.
When you open checkout, Stripe processes payment details through its embedded form. Sitalyst stores subscription and invoice references, paid-through dates, amounts, refund and dispute status, and a pseudonymous payer identifier for billing and referral checks. Card numbers are not stored by Sitalyst. Analytics and advertising trackers are not configured. The deployed host’s handling of access logs must be described before public launch.
Privacy requests and complaints
Depending on how your information is used, you may have rights to access or correct it, ask for deletion or restriction, object to its use, or request a portable copy. Use the privacy contact route for a request or a complaint about information we handle. To remove data saved only on your device, use your browser controls.
You can also raise a concern with the UK Information Commissioner’s Office (ICO).