Legal

Data Processing Addendum

The terms under which we process personal data that customers put into their Aiscovery workspace.

Last updated
Legal review
Not yet reviewed (draft)
Operator
Not set yet: legal entity name
Privacy contact
privacy@aiscovery.io

Draft: pending legal review

This addendum is a draft prepared by the product team. It is not legal advice and has not been reviewed by counsel. Breach notice times, audit terms, transfer safeguards and liability are confirmed during legal review.

In short

  • You decide what personal data goes into your workspace. We process it only to run Aiscovery for you.
  • Annex 2 lists the security measures we run today; Annex 3 lists our sub-processors.
  • We give 30 days' notice before a new sub-processor, and you may object.
  • When your plan ends you can export for 12 months; then we delete your workspace.

Scope and roles

This addendum applies when Not set yet: legal entity name ("we") processes personal data for a customer ("you") as part of Aiscovery. Words such as controller, processor, personal data and data subject have the meaning given by the data protection law that applies, such as the GDPR or the UK GDPR.

You are the controller of personal data you put into your workspace. We are your processor for it.

We are a separate controller for account security, billing, consent records and support, as our Privacy Notice describes. This addendum doesn't cover that data.

Your instructions

We process your personal data only on your documented instructions: the Terms of Service, this addendum, your settings and actions in the dashboard, and requests you send to support. If we think an instruction breaks data protection law, we tell you.

If the law requires us to process your data in another way, we tell you first unless the law forbids it.

Confidentiality

Everyone at Aiscovery who can access your personal data is bound to keep it confidential and accesses it only as needed to run the service or help you.

Security

We keep the technical and organizational measures in Annex 2 in place, and we may improve them as long as protection doesn't go down.

Sub-processors

You allow us to use the sub-processors in Annex 3, which is also published on our Sub-processors page.

We email owners and admins, and update that page, at least 30 days before we add or replace a sub-processor that will process your personal data. You may object within that time. If we can't resolve your objection, you may cancel and we refund prepaid fees for the rest of your billing period.

Each sub-processor is bound by data protection terms at least as protective as this addendum. We remain responsible for their work.

Helping you

We help you answer requests from data subjects with in-product export and deletion and by email. If a data subject writes to us about your data, we pass the request to you.

We give you the information you reasonably need for a data protection impact assessment or a consultation with an authority about the service.

Personal data breaches

If a personal data breach affects your data, we tell you without undue delay after we become aware of it, with the facts we have and what we are doing about it, and we keep you updated.

Information and audits

On request, we give you the information needed to show that we comply with this addendum, at most once a year unless a breach occurred or an authority asks. If that information isn't enough, we agree with you on a reasonable audit, at your cost, with notice and confidentiality.

International transfers

Some sub-processors process data outside the European Economic Area and the United Kingdom, including in the United States. Where data protection law requires it, we and our sub-processors use the European Commission's standard contractual clauses, the UK addendum to them, or another valid safeguard.

End of processing

When your plan ends, your workspace stays readable for 12 months and a workspace owner can export it. Then we delete it. If an owner deletes the workspace earlier, we delete it then. We keep data longer only where the law requires it.

Liability and order of documents

The limits of liability in the Terms of Service apply to this addendum. For personal data, this addendum wins over the Terms of Service if they conflict.

Annex 1: Processing details

ItemDetails
Subject matterSite checks of your public pages, AI agent runs on your store, Ask Aiscovery, results, fixes and reports, team collaboration and service emails.
DurationYour subscription, plus the 12 months your workspace stays readable after it, unless you delete it sooner.
Nature and purposeCollect limited technical facts from public pages, run AI agent tasks on public pages, store and show results, send service emails and provide support.
Data subjectsYour team members and invitees, and people whose names or contact details appear on your public pages.
Personal dataNames and work emails of team members, invitation emails, limited page facts (titles, descriptions, structured data types), task instructions, masked step screenshots, Ask Aiscovery conversations and support messages.
Special categoriesNone intended. Our checker and agents don't log in, don't send forms and read only public pages, and screenshots are masked.

Annex 2: Security measures

Measures in place in the product today:

  • Each workspace is isolated in the database with forced row-level security. Application roles have the least access they need and can't bypass it.
  • Every account has a verified email. Sessions use httpOnly, Secure cookies, and the API checks the origin of every request that changes data.
  • Data travels encrypted with TLS. Our checker fetches only over HTTPS with a valid certificate.
  • Evidence and history are append-only and not rewritten. Operator actions are written to an audit log.
  • IP addresses in consent records and free checks are stored only as keyed hashes, with the key kept outside the database.
  • Step screenshots are masked before storage and before a model sees them; a screenshot whose mask can't be verified is dropped.
  • Our checker identifies itself, follows robots.txt, makes at most one request per second, never logs in and never gets around CAPTCHAs or firewalls.
  • Secrets live in environment configuration, never in code. Payment and model keys are used only on our servers.
  • Raw evidence is deleted after 90 days, and a workspace is purged 12 months after its plan ends.

Measures for hosting, such as encryption at rest, backups and restore tests, are added here when the hosting provider is chosen, before paid accounts open.

Annex 3: Sub-processors

The list as of the date at the top. Our Sub-processors page always has the current one.

ProviderWhat we use it forData it receivesWhereStatus
VercelHosts this website and runs its forms. Will also host the dashboard.Request details such as IP address, user agent, time and page. Demo requests pass through on their way to Telegram. Anonymous page analytics only when analytics are on.United States, with pages served from Vercel's global networkIn use
TelegramDelivers demo requests to our team's private channel.Name, work email, store website, optional note, the page you came from and the time.Telegram's data centersIn use
MicrosoftMicrosoft Clarity: visit replays and heatmaps of this website, only for visitors who accept analytics cookies.Clicks, scrolling, mouse movement and page content with form fields masked, page address, IP address, browser and device details.United StatesIn use
GoogleGoogle Analytics: counts visits to this website, where they come from and demo requests, only for visitors who accept analytics cookies.Pages visited with query strings removed except campaign tags, the referring page, browser, device and approximate location, a random cookie ID, and button clicks with fixed labels. Google uses the IP address for location and doesn't store it.United States and other countries where Google operatesIn use
StripePayments, invoices, tax calculation and the billing portal (Manage billing).Billing email, name and address, payment method (held by Stripe, never by us), subscription and invoice data, and your acceptance of the Terms.United States and other countries where Stripe operatesPlanned
CloudflareTurnstile bot protection on the free check and the form before checkout.IP address, user agent and the browser signals the challenge needs.Cloudflare's global networkPlanned
OpenAIAI agent runs with GPT-6 Luna, Ask Aiscovery, and the AI check of task results.Task instructions, public page text from your store, masked step screenshots, page addresses, and your Ask Aiscovery questions with the results needed to answer them.United StatesPlanned
GoogleAI agent runs with Gemini and the AI check of task results, through the Gemini API.Task instructions, public page text from your store, masked step screenshots and page addresses.United States and other countries where Google operatesPlanned
AnthropicClaude agents and checkout rehearsal.Task instructions, what the agent sees on the page, masked step screenshots and page addresses.United StatesComing later
DataForSEOAI visibility add-on: answers from ChatGPT search, Google AI Overviews and Gemini.The prompts you choose to monitor, which can name your brand and competitors, plus a market and language.Confirmed before the add-on opensComing later
Bright DataAI visibility add-on: Perplexity answers.The prompts you choose to monitor and a country.Confirmed before the add-on opensComing later

Not chosen yet, and named before they receive customer data: hosting for the api, workers and database, screenshot storage, transactional email, support inbox, status page.