Legal · First draft
Privacy
Updated
This is a short draft for the current beta, pending completion and review before public subscriptions open.
What Quantely processes
The service processes account details such as your name and email address, workspace settings, support requests and technical logs. Connected sources can provide channel reports, public mentions and website activity, including page paths, referrers, timestamps and session identifiers.
Why data is used
Data supports sign-in, reporting, integrations, support and service security. Customers choose their connected sources and reporting settings. Customers remain responsible for the lawful collection of their website data, visitor notices and any required consent.
Cookies and session matching
Account sign-in uses session cookies. Website measurement can use browser or tab storage and, when configured, technical fingerprint matching. These identifiers should not be treated as anonymous simply because a visitor’s name is absent.
Service providers and retention
Quantely uses Vercel for hosting and connections, and Supabase for account and database services. Connected platforms also process data under their own policies. Detailed retention periods, processing locations and any international transfer safeguards still need to be documented in the final notice; this draft does not promise automatic deletion after a fixed period.
Your choices and rights
Depending on the processing and applicable law, you may request access, correction, deletion, restriction or portability of personal data, object to processing, or withdraw consent. You may also complain to a data protection authority. For activity measured on a customer’s website, contact that website’s operator first.
During the beta, customers can raise privacy requests through Contact in their workspace. The service provider’s legal identity, public privacy contact and processing-specific legal bases must be added before this notice is finalised.