This policy explains what Supavigent collects, why, who we share it with and what you can do about it. It covers the website, the dashboard and the API.
1. What we collect about you
Your account. Your email address, and your name and profile picture if you sign in with Google. You can also sign in with a one-time link sent to your email.
Your brands. The brand names, keywords, official domains and allowlist you enter, and your alert settings — including any Slack or webhook URL you give us.
Rights-holder details. The name, company, address, email and other contact details you provide for takedown notices. These are included in the notices you choose to send, so recipients such as registrars and hosting providers will see them.
Billing. Your plan and subscription status. Card details go directly to Stripe and never touch our servers.
API keys and usage. We store a hash of each API key and a short display prefix — never the key itself — and a log of calls made with it (endpoint, status, time), for your usage view and for support.
Technical logs. IP address, browser and timestamps, kept for security and debugging. The free domain check on our home page uses your IP address to enforce its rate limit.
2. Data about the sites we monitor
To find impersonation we collect information that is publicly available about domains and web pages: DNS records, registration data published through RDAP, hosting network, Certificate Transparency entries, search results, the page title and visible text of a page, and a screenshot of it. This is information about websites, not about you. Where registration or abuse-contact data names a person, we use it only to assess the domain and to address a takedown notice to the right party.
If you believe a site of yours has been reported in error, write to [email protected].
3. Why we use it
- To run the monitoring, evidence collection and takedowns you signed up for.
- To send the alerts and digests you configure.
- To bill you correctly and keep an account within its plan.
- To keep the service secure and investigate abuse of it.
- To send service email. We do not sell your data to anyone.
4. Who else sees it
- Notice recipients — registrars, hosting providers, Netcraft, Cloudflare, APWG and others you choose to report to receive the notice, its evidence and your rights-holder details.
- Stripe — payments and subscriptions.
- Google — only if you choose to sign in with a Google account.
- Service providers that host the application and database, deliver our email, and run the AI analysis of suspected pages. They process data only to provide those services to us.
- Destinations you configure, such as your Slack workspace or webhook endpoint.
We also disclose data where the law requires it, and will tell you where we may.
5. How long we keep it
Your account and everything in it stay until you delete them. Deleting a brand deletes its findings and takedown history. Ask us to close your account and we will delete your personal data and revoke your API keys; we keep the billing records tax law requires.
6. Your rights
You can ask for a copy of the personal data we hold about you, ask us to correct or delete it, or object to how we use it. Email us and we will respond within a month. If you are in the UK or EU you may also complain to your data protection authority.
7. Cookies
We set a cookie to keep you signed in, and Stripe sets its own during checkout to prevent fraud. Both are strictly necessary. We do not use advertising or cross-site tracking cookies.
8. Security
The site and API are served over HTTPS. API keys are stored only as hashes. Each customer’s records are scoped to their own account, and access is limited to the people who need it. No system is perfect; if a breach affects you we will tell you promptly.
9. Changes
If we change this policy materially we will email you before it takes effect. The date at the top reflects the current version.