
Arkon GroupTrust & Privacy
Your data, and what we never do.
Plain language, and every claim mapped to how the platform is built.
Last reviewed: 2026-11-04
01
GDPR compliance posture.
The platform and its database are in the EU, for European and US customers alike. Download your data yourself at any time; delete it yourself, or ask us and we remove it.
- Data residency
- The platform runs in the EU: its functions in Dublin, on Vercel, and its database in Ireland, on Supabase. Your free audit, your organisation’s data and the measurement of use are held in that database. Documents and decks the platform makes for an account are held in Vercel’s file storage. How the model provider is used is in Section 02; where each provider processes data is in Section 05.
- US customers
- The servers stay in the EU. A US company’s audit and engagement data is held on the same EU infrastructure under the same controls; we do not run a US region today and say so rather than imply one. US public-company evidence (SEC filings, Census, BLS, BEA) is read from its public sources, not stored as customer data.
- Processor obligations
- We act as processor for personal data submitted through the audit or the platform. A Data Processing Addendum is available on request; the same terms apply to free-audit usage.
- Right to deletion (Art. 17)
- An admin of your organisation deletes its data at once, in the platform: Delete your company’s data on the page Who can see your data (Your business, then Who can see it). It says there what is deleted and what is kept. You can also write to hello@arkonconsultinggroup.com from the address on your account.
- Right of access & portability (Art. 15, 20)
- Download all of your organisation’s data yourself, at any time, with Download my data on the same page: one machine-readable file. See Section 06 below.
- Lawful basis
- Free-audit processing relies on consent (you start it). Paid-plan processing relies on contract. Measuring visits and use relies on legitimate interest: counting, without cookies, what is used so we can run and improve the service, and keeping the platform healthy and free of abuse (Section 07). Never sold, never used to train models.
02
Model-training disclosure.
Your audit answers are not used to train any model.
The honest substance behind that line — not a marketing slogan:
- How prompts are processed
- When the platform needs synthesis, the relevant inputs go to Anthropic’s API as prompts and the output comes back. We persist input and output in our own database for product functionality.
- No model fine-tuning on customer data
- We run no fine-tuning, RLHF or distillation on customer audit data, and export no prompts to a training dataset. The same holds for Arkon’s reasoning inside the platform.
- Anthropic’s side of the boundary
- Anthropic processes prompts as an API provider under their commercial terms — they do not train their foundation models on API customer data by default. Anthropic Commercial Terms and the Anthropic data-use policy cover the upstream commitment we rely on.
- Data flow, end-to-end
- your input → our API → Anthropic API → model output → our database → your dashboard. No third destination. No training pipeline branch.
- Retention boundary
- Audit prompts & outputs persist as part of your engagement. They are deleted with your organisation’s data on request, or, for a free audit never claimed by an account, after the 30 days described in Section 03.
03
Audit data lifecycle.
A free audit that is not claimed by an account is permanently deleted after 30 days.
- An account keeps it
- Create an account and the free audit binds to it. From then on it is part of your organisation’s data and stays for as long as you keep your account, whether or not you activate a module. It is deleted with the rest on request (Section 01).
- Unclaimed audits are deleted
- A free audit never claimed by an account is deleted after 30 days: answers, figures, findings, the audit and plan written from them, answers given to activate a module before signing up, replies to its emails, and its session token. A daily sweep removes it, so it is gone by day 31. Aggregate, non-identifying quality metrics are retained.
- Deletion on request
- Before day 30, anyone can ask for a free audit to be deleted sooner by writing to hello@arkonconsultinggroup.com with the company name and the email address used for the audit.
- What is not subject to the 30-day clock
- Our audit log, the platform’s security record, keeps each audit’s start for 730 days: the company’s name, sector and country and when it began. For an audit no account claims it never holds the email address: a keyed one-way fingerprint stands in for it, which cannot be turned back into the address and only tells us that the same address came back. Billing records are kept as accounting law requires. Neither holds your answers.
04
Encryption & authentication.
What protects your data in transit, at rest and at sign-in: only what the platform does today.
- In transit
- Every page of this website and of the platform, and every call to the platform, is served over HTTPS only.
- At rest
- The database is encrypted at rest (AES-256) by Supabase, which runs it.
- Authentication
- Sign-in is handled by Clerk, a specialist sign-in service: your password is held by Clerk and never stored by us. In the platform’s Settings you change your sign-in details and see, and end, your active sessions.
- API authentication
- Every signed-in page and call is checked on our server for a valid session before any data is read; a signed-out call is refused. The free audit’s own calls are tied to the audit by a token of its own, and limited per connection.
- Separation between companies
- On every signed-in request the platform reads only the data of the organisation the person belongs to.
05
Sub-processor list.
The full list of third parties that may process customer data on our behalf. It is the one list the platform uses: when it changes, this page changes with it.
| Sub-processor | Policy |
|---|---|
Anthropic Language model: drafts the platform’s writing and reasoning (the free audit, module work, the consultant’s answers) | Policy → |
Clerk Sign-in: accounts, passwords and sessions | Policy → |
Supabase The platform’s database | Policy → |
Vercel Runs this website and the platform, and stores the files the platform makes for an account | Policy → |
Stripe Subscription billing + payment processing | Policy → |
Resend Sends and receives the platform’s email | Policy → |
Inven Company information: finds the company you name and reads its public record | Policy → |
Sentry Error reports from the platform | Policy → |
Railway Assembles Arkon’s own videos | Policy → |
Google Workspace Our own mailboxes | Policy → |
Upstash Limits how often one connection or person may call the free audit and the platform | Policy → |
Each provider works under its own published terms, linked in its row.
06
Data export commitments.
You own your engagement data. You can take it with you, at any time, in a format other tools can read.
- Download my data
- On the platform’s page Who can see your data, Download my data gives any member of your organisation everything we hold for it as one machine-readable file (JSON), whenever you want it.
- Audit-finding history
- Findings carry their full provenance: which audit question surfaced them, which engine produced them, the confidence flag, and the timestamp. Exports preserve this metadata so any downstream tool can reason about the same evidence we did.
- After cancellation
- Cancelling the retainer does not delete your data. It stays in your account and you can still download it; it is deleted when an admin of your organisation deletes it, or asks us to.
- No vendor lock-in mechanics
- We don’t add proprietary headers, watermark exports, or withhold artefacts behind upgrade gates. The methodology is the substance; the export is the substance verbatim.
07
What we measure.
We count visits without cookies, and never link a visit to a person.
- Why
- We count visits to this website and to the platform’s public pages (such as the free audit), and how each account uses the platform, so we can see what is used and what to improve. It is never sold, never shared and never used to train models.
- What a visit records
- The day of the visit, never its time; the page’s address, without anything a link adds after it except its campaign tags; the name of the site that sent you, never the page you came from; your country, as our hosting provider reads it from the connection; and whether your browser describes itself as a phone, a tablet or a computer.
- No cookies
- Counting a visit sends no cookie and reads nothing stored on your device, so there is no banner to accept.
- Not linked to you
- To count each visitor once a day, our server combines the connection’s address and the browser’s description with a random code that changes every day, a different code for this website and for the platform, and keeps only the result; the code is deleted two days later. We never link a visit to a person. We keep only the day of a visit, and in our reports a group of fewer than five visits is shown only as “other”, so no one can be singled out from them. Your IP address and your browser’s description are never stored.
- When you are signed in
- Signed-in use is recorded separately, by the hour, as part of running your account: which of the platform’s areas your team opens (the account, the area and the hour), sign-ins, messages to the consultant, documents made, files uploaded and credits used. Each person is noted under a coded reference, never by name, and this record is never joined to the counting of visits.
- Free audits
- We count how many audits start from each source, by the day, and never link that count to who started them. An audit’s own record notes only the day it started, never where its visitor came from.
- Where and how long
- Measurement is first-party: our own platform records it, on the same EU infrastructure as everything else, and no analytics company receives it. Visit records and these notes are deleted after about 13 months; daily totals that name no one and no company are kept. When your organisation’s data is deleted, its notes go with it; when a person’s sign-in is deleted, so are theirs. Our own staff and test companies are counted apart from customers.
- The rules it follows
- Counting visits is done by us alone and only for our own sites; it is never linked to a person, combined with other data, passed on or used to follow anyone from site to site; it is reported only in groups, and kept for a limited time. These are the conditions European data-protection regulators set for audience measurement without consent.