Orion Hosted data processing agreement
Version: 2026-11-16. Effective date: the date the Customer accepts it in the dashboard. Corrected on 18 November 2026: blanks left in the published text are filled in (daily rollups are now deleted 90 days after the day they cover, section 9.2), the data protection officer row says that none is appointed, and Amazon CloudFront, in use since launch, is named in section 8.2 and Annex 3. Nothing else changed.
1. Parties and scope
This data processing agreement (the "DPA") is between:
- the organisation, or the person, that accepts this DPA in the Orion Hosted dashboard, under the name it gives there when it accepts (the "Customer"), as controller; and
- Paradigm Machines, Inc., a Delaware corporation (file number 10576277) of 1160 Battery St, San Francisco, run from London, United Kingdom ("Paradigm Machines"), as processor.
It forms part of the agreement under which the Customer uses Orion Hosted, the Orion Hosted terms, version 2026-11-16 (the "Agreement"). Where the two conflict on data protection, this DPA wins.
| Customer | Paradigm Machines | |
|---|---|---|
| Data protection contact | The workspace owner who accepted this DPA, at the email address they sign in with, or another contact the Customer names to Paradigm Machines in writing | Ryan Lin, ryan@paradigmmachines.ai |
| Data protection officer | The Customer's, if it has one and names them to Paradigm Machines in writing | None appointed (not required); data protection questions go to Ryan Lin, ryan@paradigmmachines.ai |
| Representative (UK GDPR Art 27) | n/a | Ryan Lin, London, ryan@paradigmmachines.ai |
| Representative (EU GDPR Art 27) | n/a | None appointed |
2. Definitions
- Data Protection Law: the EU GDPR (Regulation (EU) 2016/679), the UK GDPR, the UK Data Protection Act 2018, and the rules on cookies and similar technologies (the ePrivacy Directive as implemented in each EU country, and the UK Privacy and Electronic Communications Regulations, "PECR"), as each applies to the processing. "GDPR" means the EU GDPR or the UK GDPR, whichever applies.
- Customer Personal Data: personal data that Paradigm Machines processes for the Customer through Orion Hosted, as described in Annex 1. It does not include data about people who sign in to the Orion dashboard. Paradigm Machines is the controller of that data, and its privacy notice covers it.
- Connected Tool: a PostHog project, a Mixpanel project, a Datadog organisation or a Sentry organisation that the Customer connects to Orion Hosted on the dashboard's Import page.
- Imported Recordings: recordings and analytics data of visits, made by another tool, that the Customer brings into Orion Hosted by connecting a Connected Tool, by having a Connected Tool's browser SDK send through Orion Hosted, by importing an export on the dashboard's Import page, or by uploading them through an AI agent it has connected.
- Recommendations: an optional part of Orion Hosted that the Customer turns on for a Site in the dashboard, and can turn off there at any time. While it is on, AI models review each visit to that Site for the problems the visitor ran into, two of them check each problem, and the dashboard lists the ones both confirm. It is off for every Site until the Customer turns it on.
- Site: a website on which the Customer installs the Orion script tag (the "Tag"), or a website or other product whose Imported Recordings the Customer brings into Orion Hosted.
- Sub-processor: another processor that Paradigm Machines engages to process Customer Personal Data.
- Temporary Account: an account made when someone connects a PostHog project without signing in with Google. It holds one Site and has no email address.
- Personal Data Breach, controller, processor, data subject and processing have the meanings given in GDPR.
3. Subject matter, duration, nature and purpose
- Subject matter. Paradigm Machines records how visitors use the Customer's Sites, receives recordings of those visits that the Customer brings in, stores the recordings and analyses them, so the Customer can see where visitors have trouble.
- Duration. From the effective date until Paradigm Machines has deleted all Customer Personal Data under section 9.
- Nature. Collection by the Tag in the visitor's browser, receiving and masking Imported Recordings, transmission, storage, rebuilding the screens from the session replay, predicting where on the screen the visitor probably looked, scoring, for Sites with Recommendations on reviewing visits with AI models (section 6.5), showing the results in the dashboard, and deletion.
- Purpose. Only to provide Orion Hosted to the Customer. Paradigm Machines does not sell Customer Personal Data, does not use it for advertising or for profiling for advertising, and does not use it for its own purposes, except that it may use anonymised, aggregated statistics that cannot identify any Site, visitor, session or account, to improve Orion Hosted and to describe it publicly.
- Decisions about visitors. The friction score rates how a visit went, so it may count as profiling under GDPR Art 4(4). Orion makes no automated decisions with legal or similarly significant effects on visitors (GDPR Art 22).
- Data and data subjects. Annex 1 lists the categories of personal data and of data subjects.
4. The Customer's duties
4.1 Lawful basis and consent. The Customer decides why and how Customer Personal Data is processed. It is responsible for having a lawful basis under GDPR, and any consent the cookie rules require, for every visit the Tag records and every Imported Recording it brings in.
4.2 The Tag records whenever it runs. The Tag does not ask visitors for consent. The Customer must load it only where it has a lawful basis and any consent needed, for example only after the visitor accepts analytics in the Customer's own consent banner. The Tag keeps a random device id in the visitor's browser storage, which in most cases needs consent under ePrivacy Directive Art 5(3) and PECR regulation 6.
4.3 Stopping mid-visit. If a visitor withdraws consent during a visit, the Customer's consent tool can call orion.stop() to stop recording. The Customer is responsible for connecting its consent tool to it. To remove what was recorded before, the Customer can ask for the session to be deleted (section 9.3).
4.4 What the Customer's pages show. The session replay records page text as it appears on screen, except inputs and masked or blocked areas. Click descriptions record element text (up to 255 characters) and data-* attributes, and page events record URLs and page titles. The Customer will:
- mask page areas that show personal data it does not need with
[data-orion-mask], or leave them out with[data-orion-block]or.ph-no-capture; - not record special category data (GDPR Art 9) without a valid condition; masking or blocking those areas is the simple fix;
- keep personal data out of URLs, page titles and data-* attributes where it can;
- pass a pseudonymous id to
orion.identify(id), not an email address or name.
4.5 Telling visitors. The Customer will tell visitors about Orion in its own privacy notice. Part 3 of the Orion privacy policy has a suggested paragraph.
4.6 Impact assessment. The Customer decides whether it needs a data protection impact assessment. Session replay with gaze prediction is systematic monitoring of behaviour, so it may. Paradigm Machines will help (section 5.6).
4.7 Lawful instructions. The Customer's instructions must comply with Data Protection Law.
4.8 Imported Recordings. The Customer chooses the tool that made each Imported Recording and has its own contract with that tool's provider, which is not a Sub-processor. The Customer is responsible for having the right to bring each recording into Orion Hosted. [data-orion-mask] and [data-orion-block] work only in the Tag, so for an Imported Recording the Customer will mask or leave out what it does not need in the tool that made it, or set the Site to mask all text. Deleting a session in Orion Hosted does not delete it from that tool, so the Customer also deletes it there: otherwise a later check or import can bring it back.
5. Paradigm Machines' duties
These follow GDPR Art 28(3). Paradigm Machines will:
5.1 Instructions (Art 28(3)(a)). Process Customer Personal Data only on the Customer's documented instructions, including about transfers to other countries, unless EU, EU member state or UK law requires otherwise. In that case it will tell the Customer before processing, unless that law forbids it. The Agreement, this DPA, and the Customer's settings and actions in Orion Hosted (installing the Tag, connecting a Connected Tool or sending its browser SDK's traffic through Orion Hosted, importing or uploading recordings, connecting an AI agent, turning Recommendations on or off, choosing what to mask, asking for deletion) are the Customer's instructions. Paradigm Machines will tell the Customer straight away if it thinks an instruction breaks Data Protection Law.
5.2 Confidentiality (Art 28(3)(b)). Give access to Customer Personal Data only to people who need it to run, support or secure Orion Hosted, and make sure they are bound by a duty of confidentiality.
5.3 Security (Art 28(3)(c) and Art 32). Keep the measures in Annex 2 in place, and not reduce the overall protection they give.
5.4 Sub-processors (Art 28(3)(d)). Follow section 6.
5.5 Rights requests (Art 28(3)(e)). Help the Customer answer visitors' requests to use their GDPR rights, through the deletion options in section 9.3 and otherwise as far as the nature of the processing allows. If a visitor writes to Paradigm Machines directly, it will pass the request to the Customer without undue delay, and will not answer it except to say it has been passed on.
5.6 Other help (Art 28(3)(f)). Help the Customer meet its duties under GDPR Arts 32 to 36 (security, breach notification, impact assessments and prior consultation with a regulator), taking into account the nature of the processing and the information Paradigm Machines has.
5.7 Deletion at the end (Art 28(3)(g)). Follow section 9.4.
5.8 Information and audits (Art 28(3)(h)). Follow section 10.
5.9 Records. Keep a record of the processing it does for the Customer (GDPR Art 30(2)), and cooperate with supervisory authorities.
6. Sub-processors
6.1 The Customer gives Paradigm Machines general written authorisation to use Sub-processors. Annex 3 lists them at the effective date. The current list is at https://app.paradigmmachines.ai/subprocessors.
6.2 Paradigm Machines will tell the Customer at least 30 days before it adds or replaces a Sub-processor, by email to the Customer's contact in section 1 and by updating the list.
6.3 The Customer may object on reasonable data protection grounds before that notice period ends. The parties will then discuss it in good faith. If they cannot resolve it, the Customer may end the Agreement, and Paradigm Machines will refund any fees prepaid for the period after it ends.
6.4 Paradigm Machines will have a written contract with each Sub-processor that gives Customer Personal Data at least the same level of protection as this DPA. It stays fully liable to the Customer for each Sub-processor's performance of those duties (GDPR Art 28(4)).
6.5 Recommendations. The Sub-processors that Annex 3 lists for Recommendations receive Customer Personal Data only from a Site on which the Customer has turned Recommendations on, and only for visits reviewed while it is on. Turning it on is the Customer's instruction to send them each visit's session replay, rendered as a video with the predicted gaze, its page events, screen pictures and the names of elements on its pages, as section 8.6 describes. Paradigm Machines records who turned it on, when, and the version of the words shown to them. Turning it off stops new reviews at once; the Customer chooses whether the problems found so far are kept or deleted.
7. Personal data breaches
7.1 Paradigm Machines will tell the Customer about a Personal Data Breach affecting Customer Personal Data without undue delay after becoming aware of it, and in any case within 48 hours, by email to the Customer's contact in section 1.
7.2 The notice will say, as far as Paradigm Machines then knows: what happened; the categories and approximate number of visitors and records affected; the likely consequences; what has been done or is proposed; and who to contact. Anything it does not yet know will follow as soon as it knows it.
7.3 Paradigm Machines will take reasonable steps to contain and investigate the breach, and will help the Customer notify regulators and visitors where the Customer decides to.
7.4 A Temporary Account has no email address. Until the Customer signs in with Google, Paradigm Machines will give the notices in sections 6.2 and 7.1 in its dashboard, where the Customer sees them when it next opens it.
8. International transfers
8.1 No transfers of Customer Personal Data outside the EU are planned, except for Sites with Recommendations on (section 8.6). It is stored in the EU, in Cloudflare's EU jurisdiction (Durable Objects, R2 storage and D1 database), and processed on AWS servers in eu-west-1 (Ireland). If the Customer connects an AI agent, data reaches that agent wherever its provider runs it, on the Customer's instruction (section 5.1), and the Customer is responsible for that transfer.
8.2 Cloudflare Workers handle each request at the Cloudflare location nearest the visitor, and Amazon CloudFront, which receives the requests to app.paradigmmachines.ai and t.paradigmmachines.ai and passes them on to Cloudflare, at the AWS edge location nearest the visitor; CloudFront stores nothing and keeps no logs of them. For a visitor outside the EU either may be outside the EU, but the data is stored only in the EU. This handling is covered by Cloudflare's data processing agreement, which includes the EU Standard Contractual Clauses and the UK Addendum. Cloudflare, Inc. is also certified under the EU-US Data Privacy Framework and its UK Extension (checked 11 October 2026).
8.3 Data about UK visitors, or for UK customers, may be stored in the EU because the UK treats the EU and EEA as adequate. Under UK GDPR this is not a restricted transfer.
8.4 Paradigm Machines works from London, and the EU treats the UK as adequate. Cloudflare, Inc. is a US company; its transfers are covered by the EU Standard Contractual Clauses and the UK Addendum in its data processing agreement, as Annex 3 states. Any other transfer outside the UK and EEA will be covered by those clauses before it starts.
8.5 Paradigm Machines will make no other transfer without the Customer's instruction and a safeguard that meets GDPR Chapter V.
8.6 For a Site with Recommendations on, each visit reviewed is processed by Paradigm Machines' review server (Ireland, eu-west-1), by Google LLC through Gemini on Vertex AI's global endpoint, which may process it in any region where Google runs Vertex AI, including outside the EU and the UK, and by Amazon Web Services through Amazon Bedrock, called from eu-west-1 (Ireland): Anthropic Claude Opus 5.5 runs in EU regions only (Bedrock's EU profile), and OpenAI GPT-6.1 Sol runs through Bedrock's global routing, which may process it outside the EU and the UK. Each processes it under its data processing addendum named in Annex 3. Transfers to Google LLC are covered by the EU Standard Contractual Clauses in Google's Cloud Data Processing Addendum, and any transfer by Amazon Web Services outside the EU by those in the AWS GDPR Data Processing Addendum, each with its provisions for the UK. What the models find is stored with the session in the EU, and deleted with it (section 9).
9. Retention and deletion
9.1 90 days. Paradigm Machines deletes everything tied to a session (events, replay, input timing, context, identifiers, gaze predictions, friction scores and, with Recommendations on, the problems found in it) 90 days after the session. A storage lifecycle rule and a daily deletion job enforce this. For an Imported Recording, the 90 days count from the visit, not from when it was brought in. A record of what was brought in (the other tool's session id or the file's name, but no recording) can stay for up to 90 days after it was brought in.
9.2 Daily rollups. Paradigm Machines keeps daily aggregate rollups for trend charts. They hold only counts and averages, and no session or visitor data: no session, tab, device or identify ids. The daily deletion job deletes them 90 days after the day they cover, and they are deleted sooner if the Site is deleted or the Agreement ends.
9.3 Deletion on request. The Customer can ask Paradigm Machines to delete:
- one session;
- everything recorded under one id the Customer passed with
orion.identify(id); or - a whole Site.
Paradigm Machines will do so within one month. Site owners delete data themselves in the dashboard (Settings). Anyone else can ask by email to ryan@paradigmmachines.ai. Data can be found for deletion only by session, identify id, upload or Site.
9.4 End of the Agreement. Within 30 days after the Agreement ends, Paradigm Machines will delete all Customer Personal Data and the Customer's rollups. If the Customer asks before the end, it will first return the data as a machine-readable export (JSON) sent by email. This does not apply to data that EU, EU member state or UK law requires it to keep.
9.5 Cloudflare keeps a restorable history of each D1 database ("Time Travel") for up to 30 days. Data deleted under this section can remain in that history for up to 30 days, after which it is gone.
9.6 Temporary Accounts. A Temporary Account's Site and everything in it are deleted one day after it is made if the Agreement has not been accepted, and otherwise about 90 days after its dashboard was last used, unless the Customer signs in with Google first. A Temporary Account can delete its whole Site in Settings. To delete one session, the Customer signs in with Google or asks by email (section 9.3).
10. Information and audits
10.1 On request, Paradigm Machines will give the Customer the information it reasonably needs to show compliance with GDPR Art 28 and this DPA, for example answers to a security questionnaire and its Sub-processors' audit reports where they can be shared.
10.2 If that is not enough, or a supervisory authority asks, the Customer, or an independent auditor bound by confidentiality, may audit Paradigm Machines. The Customer will give 30 days' written notice. Audits happen at most once in 12 months, unless there has been a Personal Data Breach or a regulator requires one. Each party pays its own costs. An audit must not give access to other customers' data or weaken security.
11. Liability
Each party's liability under this DPA is subject to the limit and exclusions in the Agreement. Nothing limits visitors' own rights under GDPR Art 82.
12. Governing law and courts
This DPA is governed by the laws of England and Wales, and the courts of England and Wales decide any dispute about it, unless Data Protection Law requires otherwise.
Signatures
| Customer | Paradigm Machines, Inc. | |
|---|---|---|
| Name | Ryan Lin | |
| Title | CEO | |
| Signature | ||
| Date |
Annex 1: processing details
- Controller: the Customer.
- Processor: Paradigm Machines.
Data subjects
- Visitors to the Customer's Sites while the Tag runs, or whose visits are in Imported Recordings. These may include the Customer's own customers, prospects and staff.
- People whose personal data is shown as text on a recorded page or in a screen picture, unless the Customer masks or blocks it.
Personal data the Tag records
- Page activity: page views and page leaves, with the URL, page title, referrer and UTM tags; how far the visitor scrolled.
- Interactions: clicks, form submits and form field changes (never the field's value), each with a description of the element: tag, id, classes, text (up to 255 characters), href, data-* attributes and position. Rage clicks and dead clicks.
- Technical events: JavaScript errors; web vitals (LCP, CLS, INP, FCP).
- Session replay (rrweb): how the page looked and changed during the visit. Every input is masked by default. Text inside
[data-orion-mask]is masked. Elements marked[data-orion-block]or.ph-no-captureare left out entirely. Other page text is recorded as it appears on screen. - Input timing: pointer positions and timing; the timing of key presses, but never which key.
- Device context: browser, operating system, device class, screen and viewport size, language and time zone.
- Location: country and region, derived from the request. The raw IP address is never stored.
- Identifiers: a random anonymous device id in first-party browser storage, a session id, a tab id, and optionally an id the Customer passes with
orion.identify(id).
Personal data in Imported Recordings
Orion Hosted keeps only the following, as far as a recording holds them:
- Session replay (rrweb): how the page looked and changed during the visit, with pointer positions and the timing of field changes. Typed field values are masked. Tick boxes, radio buttons and the option chosen in a list stay as the other tool recorded them. For recordings brought in since 6 November 2026, page text that looks like an email address, a phone number or other number of 9 digits or more, or a long id is masked on every Site. Links and most other attributes are not, such as a
mailto:link. All text is masked if the Site was set to mask it when the recording was brought in. Anything else the other tool put in the replay stays in it, such as canvas content. - Activity: page views, clicks, rage and dead clicks, and when the visitor wasn't using the page, with the URL, referrer, UTM tags and the element's text. Query parameters in URLs with names like token, key, password or email are masked.
- Technical events: JavaScript errors.
- Device context and location: browser, operating system, device class, viewport size and country.
- Identifiers: the other tool's session id, or the file's name if it has none, and a tab id.
- Screen recordings: if the Customer uploads a screen recorder's output, pictures of the screen, with the pointer, scrolling and key-press timing that go with them. Pictures are kept as sent: Orion Hosted does not mask them.
Person profiles and IP addresses are not kept. Orion Hosted does not ask a connected PostHog project for them. Mixpanel's, Datadog's and Sentry's APIs answer with whole events and replay details: Orion Hosted takes from them only what is listed above and discards the rest as it reads it. A Connected Tool's browser SDK that sends through Orion Hosted has each request passed on to that tool unchanged, with the visitor's IP address for the tool's own location lookup, and Orion Hosted keeps only what is listed above. Console logs, network logs and the other tool's own settings and custom events are dropped.
Data Paradigm Machines derives
- Gaze prediction: where on the screen the visitor probably looked. It is predicted from pointer movement, scrolling and the screen. It does not come from an eye tracker or a camera.
- Friction score: a score for each time window and for each session.
- Recommendations: for Sites with them on, the problems AI models found in each visit, each with the two checks' verdicts, and the recommendations they are grouped into.
Not recorded by the Tag
Form field values; which key was pressed; the raw IP address; canvas content; cross-origin iframes; console logs; network request and response bodies and headers; anything inside [data-orion-block] or .ph-no-capture.
Special category data
None intended. The replay could capture it if a page shows it as text, and a screen picture could show it, so the Customer must mask or block those areas, or leave those screens out (sections 4.4 and 4.8).
Processing operations
- The Tag collects the data in the visitor's browser and sends it over HTTPS to Cloudflare Workers, which reject bot traffic and derive country and region from the request.
- Imported Recordings reach Cloudflare from a Connected Tool (through its API, or as its browser SDK's traffic sent through Orion Hosted), from the dashboard's Import page, or through an upload. An import is masked in the Customer's browser. Anything else is masked as it is read, and the unmasked copy is then deleted (in any case within 90 days).
- Cloudflare stores the data in its EU jurisdiction (Durable Objects, R2 storage, D1 database).
- A GPU server at AWS in eu-west-1 (Ireland) fetches a session through short-lived signed URLs, rebuilds the screens from the replay, runs the gaze model and the scoring engine, and holds the data only while it processes it.
- For a Site with Recommendations on, once a visit is scored, Paradigm Machines' review server fetches it through short-lived signed URLs, renders its replay as a video with the predicted gaze, and sends that video, its page events, screen pictures and element names to Gemini on Vertex AI (Google) and to Amazon Bedrock models (Amazon Web Services), which list and check the problems the visitor ran into (section 8.6). The problems found are stored with the session.
- The dashboard shows visits, replays, gaze predictions, friction scores and Recommendations to the Customer's signed-in users, and to any AI agent the Customer connects.
- Data is deleted as set out in section 9.
| Item | Details |
|---|---|
| Purpose | To provide Orion Hosted to the Customer (section 3) |
| Frequency | Continuous, whenever the Tag runs; at regular checks for a Connected Tool, and as each visit ends for one whose browser SDK sends through Orion Hosted; when the Customer sends them for imports and uploads |
| Retention | 90 days after the session; daily aggregate rollups 90 days after the day they cover (section 9) |
| Locations | EU: Cloudflare EU jurisdiction; AWS eu-west-1 (Ireland). For Sites with Recommendations on, also: the review server (Ireland, eu-west-1); Google Vertex AI's global endpoint, which may be outside the EU; Amazon Bedrock, called from eu-west-1 (Ireland): Claude Opus 5.5 in EU regions only, GPT-6.1 Sol through global routing, which may be outside the EU |
| Sub-processors | Annex 3 |
Annex 2: technical and organisational measures
Encryption and location
- In transit: every connection uses HTTPS. The dashboard and tag address accept TLS 1.2 or newer only, plain HTTP is redirected to HTTPS, and browsers are told to use HTTPS only (HSTS).
- At rest: visitor data and dashboard records are stored in Cloudflare D1, R2 and Durable Objects, which Cloudflare encrypts at rest. The GPU servers' disks at AWS use EBS encryption (AES-256, keys managed by AWS KMS), and encryption is on by default for every new volume in eu-west-1. The bucket that holds GPU model artifacts uses AES-256 server-side encryption and blocks public access.
- Location: stored in the EU (Cloudflare EU jurisdiction) and processed in AWS eu-west-1 (Ireland).
Access control
- Dashboard access to Customer Personal Data is through Sign in with Google, with owner and viewer roles in each workspace, or through a Temporary Account.
- A Temporary Account is reached with the session cookie of the browser that signed in to PostHog, or by signing in to the same PostHog project again. The newest sign-in ends any other. Orion Hosted asks PostHog at each check whether the sign-in still works, and ends the session if PostHog refuses. A Temporary Account holds only recordings from that PostHog project, and has no team, Tag, AI agents or imports by hand.
- Tokens for a Connected Tool are stored encrypted, never reach the dashboard and are read-only. Orion Hosted uses them only for the project or organisation chosen, and only for the Site it was connected to.
- Operator access to production systems and stored data is limited to the founder, Ryan Lin. He has full access to inspect stored data, which is needed to run, debug and support the service. No other person has operator access. Operator access uses two-step verification.
- Two-step verification is enabled on the Cloudflare, AWS and Google accounts.
- Personal data breaches are handled under section 7.
- Site keys are public and can only write data. They cannot read it.
- GPU servers fetch data through short-lived signed URLs and hold it only while processing.
- GPU servers scale to zero when there is no work.
- Staging is separate from production.
Collecting less by default
The Tag:
- Every input is masked in the replay. Text inside
[data-orion-mask]is masked. Elements marked[data-orion-block]or.ph-no-captureare left out entirely. - Form field values are never recorded, and neither is which key was pressed.
- No canvas, cross-origin iframes, console logs, or network bodies or headers.
- The raw IP address is never stored; only country and region are kept.
- Bot traffic is rejected.
Imported Recordings:
- Masked as Annex 1 sets out. An import is masked in the Customer's browser; anything else is masked as it is read, and the unmasked copy is then deleted (in any case within 90 days).
- Console logs and network logs are dropped, and person profiles and IP addresses are not kept.
- Pictures from a screen recorder are kept as sent. Orion Hosted does not mask pictures.
Recommendations
- Off for every Site until the Customer turns it on; until then nothing about the Site's visits is sent to an AI model provider. Turning it off stops new reviews at once.
- Phone visits, and visits with no page replay to render, are not sent.
- At most 300 visits a Site are reviewed a day.
Retention and deletion
- Automatic deletion after 90 days, by a storage lifecycle rule plus a daily deletion job.
- Deletion on request by session, identify id, upload or Site.
Annex 3: sub-processors
Authorised at the effective date. Changes follow section 6.
| Sub-processor | Service | Purpose | Location |
|---|---|---|---|
| Cloudflare, Inc. | Workers, Durable Objects, R2 storage, D1 database | Receiving, storing and serving visitor data and the dashboard | Stored in Cloudflare's EU jurisdiction; each request handled at the nearest Cloudflare location |
| Amazon Web Services EMEA SARL | EC2 instances; CloudFront | Rebuilding screens from replays; running the gaze model and scoring; for Sites with Recommendations on, the review server; CloudFront: receiving the requests to the Tag and the dashboard and passing them on to Cloudflare, storing nothing | eu-west-1 (Ireland); the review server: Ireland, eu-west-1. The model weights are stored in eu-west-2 (London) and are not personal data. CloudFront: the AWS edge location nearest the visitor. |
| Google LLC | Gemini on Vertex AI | Recommendations, only for Sites with them on (section 6.5): reviewing each visit for problems | Vertex AI's global endpoint, which may be outside the EU |
| Amazon Web Services EMEA SARL | Amazon Bedrock: Anthropic Claude Opus 5.5 and OpenAI GPT-6.1 Sol | Recommendations, only for Sites with them on (section 6.5): listing, checking and grouping the problems found | Called from eu-west-1 (Ireland). Anthropic Claude Opus 5.5 runs in EU regions only (Bedrock's EU profile); OpenAI GPT-6.1 Sol runs through Bedrock's global routing and may be processed outside the EU. |
| Google LLC | Sign in with Google | Signing in dashboard users only. Sign-in receives no visitor data. | Google's own systems |
The gaze model and scoring engine run on Paradigm Machines' own servers at AWS. Paradigm Machines sends Customer Personal Data to an AI model provider only for a Site on which the Customer has turned Recommendations on (section 6.5). If the Customer connects its own AI agent to Orion Hosted, that agent can read and download the data of the Sites its user can reach, on the Customer's instruction (section 5.1). Its provider is the Customer's supplier, not a Sub-processor, and so is the provider of any tool that made an Imported Recording (section 4.8). Google's sign-in row is listed for openness: sign-in is for dashboard users, for which Paradigm Machines is the controller.