Privacy policy

Seven things about you, plus the server records in the last paragraph of this section:

• Your email address. It is how you log in and how we reach you. The password itself is handled by Supabase Auth and stored as a hash; we never see it.
• Your name, if you fill it in. It is optional and only used to address you in the app and in the outreach signature you set up.
• Your outreach sender details, if you fill them in: the agency name, the sender first name and the booking link. They go into the outreach AIgnored writes for you, as the signature and the call to action.
• Your API keys, encrypted. Every provider key you save is encrypted with AES-256-GCM before it reaches the database. Only the provider name, the last 4 characters and the check status are readable in the app. The plaintext key never appears in a page, an export, a log or an error message.
• Scan inputs and results. The niche, city and country you typed, which models you picked, the questions we sent, the answers that came back, the business names we matched, the scores and grades, and any lead you save with its notes and generated outreach text.
• Usage counters. How many scans and outreach messages you ran in a month, so the plan limits can be enforced and shown to you on the usage page.
• Billing identifiers, if you subscribe: the Lemon Squeezy subscription and customer id, the card brand and the last four digits, the renewal date. Never the card number.

Servers also keep short-lived request logs, and Sentry receives an error report when something breaks, from our servers and from your browser. Those carry the account id and the failing request, not your keys.

We do not sell your data, we do not share it with advertisers, and there is no advertising or cross-site tracking anywhere on this site. We do not read your provider accounts beyond making the calls your scans need. We do not email your leads on your behalf.

Your email, name, keys, scans and leads are held to give you the service you asked for, which is the contract between us. Usage counters and billing identifiers are held because a paid plan needs metering and an invoice. Error reports and request logs are held to keep the service working and secure, which is our legitimate interest. Analytics runs on consent where consent is required, and the details are on the cookies page.

These are the companies involved in running AIgnored. There are no others.

The database and its backups sit in the United States. If you are in the EEA, the UK or Switzerland, that is a transfer out of your region, and it happens on the data transfer terms each of those companies publishes.

Google is not a subprocessor for fonts. The two fonts this site uses are downloaded at build time and served from our own domain, so opening a page here sends no request to a Google server and drops no Google cookie.

The Places API is called with your key, under your agreement with Google. When a scan looks up businesses, a results table or the leads board loads names and ratings, or a CSV export fills in the Google fields, the request carries your own Google Places key. So does the daily job described in the next paragraph, which refreshes the snapshot of a lead you are still working and runs without you opening the app. The Places key guide counts every one of those calls. That traffic is between you and Google under the Google Maps Platform terms you accepted when you created the key, and Google bills you for it directly. The same is true of every AI provider key: those calls are yours, made with your credentials.

What we keep from Places, exactly. The place_id, which Google allows us to keep for as long as we like, plus our own scores and grades, which are ours. Next to those we hold one working snapshot per business, taken during the scan: the name, rating, review count and website domain. Matching AI answers to businesses, grading and the outreach draft need a value to work on. For a saved lead marked new, contacted or replied, a daily job refreshes the snapshot with your key once it is more than 25 days old. A results table and the leads board never show the snapshot: they fetch those four fields live with your key, and show nothing in their place while the lookup loads, fails or has no key to use. An outreach draft is written from the saved name, so the draft text contains it. The snapshot is never sold or published, and it is deleted with the scan it belongs to. A CSV export does not read it: its Google fields come from a live lookup at the moment you click. Your data export contains the snapshot, because it is part of the scan you ran.

While the account exists. Delete the account and your profile, keys, scans, probes, businesses, matches, leads, usage counters and subscription row go in the same moment, because each of those tables is tied to your account id and cascades from it.

Six things do not go with it, and we would rather say so.

• Database backups. Once a week an encrypted copy of the database is saved to GitHub and kept for 90 days, and Supabase keeps its own backups on its own schedule. A deleted account stays in those copies until they age out, which takes at most 90 days, and then it is gone.
• Admin action records. If an admin ever acted on the account, for example suspended it, the log keeps the action, the date and the account id; the email address and any written reason are removed when the account is deleted. That is what makes an admin decision checkable later. It holds no scan content and no keys.
• Supabase Auth's own sign-in log. Supabase records sign-ups, logins, password resets and the deletion itself, with the email address and the IP address of the request. That log is kept apart from the tables tied to your account, so deleting the account does not remove it, and it is left out of our weekly backups. Ask us and we delete those entries by hand.
• Contact form messages. A message sent through the contact form is not attached to an account, so deleting the account does not remove it. Ask us and we delete it by hand.
• Rate-limit rows for logins and other account requests, which hold an IP address and the email typed, if there was one. They are not tied to an account either, and a scheduled job deletes them every day.
• Tax records, which the law requires the seller to keep. They are held by Lemon Squeezy as merchant of record, not by us.

You can see, correct, export and delete your data, object to processing, and complain to a regulator. Two of those are buttons rather than an email queue:

• Export my data on privacy and your data builds a JSON file of your profile, including your outreach sender details, and your scans, probes, businesses, mentions, leads and usage counters, and downloads it right there. API keys appear as provider, last 4 characters and status only. Billing identifiers are not in the file: they are on your billing page, and the receipts are in your Lemon Squeezy email.
• Delete my account on the same page removes the account and every row attached to it, immediately, after you type your own email address to confirm. If a subscription is active we cancel it with Lemon Squeezy at the same time. If that fails, the account is still deleted, support is asked to cancel the subscription by hand, and the page tells you so.

To correct your email or name, use account settings. For anything else, email hello@aignored.com and we answer within 30 days, usually the same week. If you are in the EEA or the UK you can also complain to your data protection authority; in Romania that is the ANSPDCP.

Traffic runs over HTTPS. Provider keys are encrypted with AES-256-GCM using a key held in the server environment, never in the database and never in the browser bundle. Every table has row level security, so the database itself refuses a query for another account's rows rather than trusting the application to filter. Sessions last 30 days and you can end them on every device from account settings.

No system is perfect. If you find a hole, email hello@aignored.com and we will fix it and credit you if you want the credit.

If we add a subprocessor or start collecting something new, this page changes first and the date at the foot of the page moves. Changes that matter to you are emailed to the address on the account.