ScreenJournal

Subprocessors

Version 3.2 · Effective 28 October 2026

Cyberinfra Limited ("ScreenJournal", "we") uses the subprocessors below to provide the ScreenJournal service. This page lists only third parties that process customer personal data as our processors. Vendors we use for our own marketing website process visitor data on our behalf; we are the controller of that data and they are covered by the Privacy Policy and Cookie Policy.

This page is incorporated into any Data Processing Agreement we enter into as the list of authorised subprocessors. From this version onward we post a new or replaced subprocessor on the Legal page's change list at least thirty (30) days before it starts processing customer data, and organisations may object within that period. Organisations that want direct notice of changes can ask support@screenjournal.ai to be added to a notification list. An organisation may object to a change, on reasonable data-protection grounds, within thirty (30) days of a posted change, to support@screenjournal.ai.

Version 3.0 of this list records changes already made — our move to Hetzner, and the use of Google Cloud Storage and Vertex AI since August 2026 — for which advance notice was not given; those entries are listed on the Legal page's change list with the dates we can establish.

Version 3.1 records a further change already made: on 20 October 2026 the service, including its database, moved from the Hetzner server in Germany to Amazon Web Services in Mumbai, India, which already stored activity data. Advance notice was not given. The thirty (30) day objection period for this change runs from the date this version was posted.

Version 3.2 adds no subprocessor. It records, vendor by vendor, the written terms that bind each subprocessor (see Contracts with our subprocessors), confirms the locations that earlier versions marked "to be confirmed" for Sentry and Vercel, corrects two vendors' legal names, and moves Paddle, which acts as an independent controller rather than as our processor, to the list of parties that are not subprocessors.

AI processing

Screen and audio analysis runs on Google Gemini models through Google Vertex AI. Report and timesheet narratives, alert evaluation and the assistant use Google Gemini models through Google's Gemini API.

VendorPurposeData processedLocationTransfer safeguard
Google (Vertex AI and the Gemini API, Gemini models; our contracting entity is Google Cloud EMEA Limited, Ireland)Screen-content analysis and activity descriptions, audio transcription and activity-pattern checks (Vertex AI); report and timesheet narratives, alert evaluation and the assistant (the Gemini API)Screen recordings from allowed applications (sensitive applications are excluded before capture); audio where the organisation enables it; derived timelinesVertex AI global endpoint; Gemini API, Google-operated with no fixed regionGoogle Cloud's terms incorporate its Cloud Data Processing Addendum (Vertex AI); the Gemini API's paid-service terms incorporate Google's Data Processing Addendum for Products Where Google is a Data Processor. Both rely on Google's Data Privacy Framework certification with standard contractual clauses as the fallback. See the contracts section below
DeepInfra, Inc.Audio transcription fallbackAudio and transcripts, if enabledUnited StatesSet out in the change notice, if enabled
OpenAIModel fallback for the assistantAssistant prompts and the organisation data retrieved to answer them, if enabledUnited StatesSet out in the change notice, if enabled

Google's commitments on training are contractual. For Vertex AI, Google's Service Specific Terms state that Google will not use customer data to train or fine-tune any AI or machine-learning model without the customer's permission or instruction; see also Google's published data-governance commitments for Vertex AI. For the Gemini API, Google's Gemini API Additional Terms of Service (effective 23 March 2026) state that when a customer uses Paid Services "Google doesn't use your prompts (including associated system instructions, cached content, and files such as images, videos, or documents) or responses to improve our products", and processes them under the Data Processing Addendum named above. Access is a Paid Service when the API key belongs to a Google Cloud project with an active billing account; we are confirming that every key we use is issued from such a project. On both services Google keeps prompts and responses for a limited period for abuse monitoring (up to 90 days on Vertex AI, 55 days on the Gemini API); flagged items may be reviewed by Google staff for policy enforcement and are not used to train models.

DeepInfra and OpenAI are not used in normal operation; each is available as a fallback and would be enabled only with notice under the change process above.

Hosting and infrastructure

VendorPurposeData processedLocation
Amazon Web Services, Inc.Our servers and PostgreSQL database on Amazon RDS (application containers, including the endpoint for connected AI tools; accounts, monitoring metadata, report data, acceptance records, operational logs); object storage (Amazon S3) for activity timelines, transcripts and metrics, and read-only access to media stored before August 2026; Amazon CloudFront in front of the service (encryption in transit, protection against attacks)All account, monitoring-metadata and report data; activity time-series data and transcripts; older media; all traffic to and from the service, in transitIndia (Mumbai, ap-south-1) for servers, database, backups and storage, with some older server backups in Hyderabad (ap-south-2); CloudFront edge locations worldwide, including the United States, for traffic in transit
Cloudflare, Inc.Domain name service for our domains; encryption in transit (TLS termination) and protection against attacks for the hosts that remain on our Hetzner server: our staging environment and the website demo workflowTraffic to and from those hosts, in transitGlobal network, including the United States
Hetzner Online GmbHHosted the whole service until 20 October 2026. Now runs our staging environment and the demo workflow on our website; the production copy of the database and the earlier report cache that were on this server are to be removed (to be confirmed)The former production copy of the database and the earlier report cache until they are removed; website demo conversationsGermany (Falkenstein)
Google Cloud (Google Cloud EMEA Limited)Object storage (Google Cloud Storage) for screen video and audio: uploaded temporarily for analysis in the default capture mode, or stored where an organisation enables Record + Save or alert evidence (since August 2026); also the model's written answers for each analysed segment and the task-grouping model input and outputScreen video and audio; the model's answers and task groupings derived from themRegion to be confirmed
Vercel Inc.Hosting of the web application and our websiteRequests to the web application and websiteUnited States (Vercel's primary processing facilities; it runs on Amazon Web Services, Microsoft Azure and Google Cloud). Serverless functions run in the region we select, by default Vercel's Washington, D.C. region; requests enter at Vercel's global edge network, including locations in Europe, for routing in transit; Vercel's backups are replicated globally

Generated reports and timesheets are stored in the PostgreSQL database on Amazon Web Services. An earlier cache of generated reports and timesheets, a MongoDB database on the Hetzner server, has not been written to since mid-2026 and is no longer used; it will be removed with the rest of that server's production copy.

Operations

VendorPurposeData processedLocation
Plus Five Five, Inc. (Resend)Transactional email: sign-in links, invitations, reminders and alert emailsNames and email addresses, and the content of those emailsUnited States. Resend keeps the content and logs of sent email for 30 days
Google (Google Workspace, Gmail; Google Cloud EMEA Limited)Report emailsNames and email addresses, and the content of those emails, including weekly report figuresGoogle's data centres
Functional Software, Inc. (Sentry)Desktop application crash and error reports, and application log lines the desktop app forwardsDevice and application diagnostics, which may include window titles; the signed-in user's name and email address and their organisationEuropean Union (Frankfurt, Germany), on Google Cloud, as selected when our Sentry organisation was created; Sentry stores user accounts, organisation settings, audit logs and integration metadata in the United States for every region. Error events are kept for up to 90 days under Sentry's plan defaults
TelegramForwarding bug reports to our support teamReporter email address and report textNetherlands for accounts registered in the UK or EEA, per Telegram's privacy policy (section 4.1); Telegram does not publish the location for other accounts, and its group companies are in Dubai and the British Virgin Islands. Telegram offers no data-processing terms to bot operators, so this channel is not covered by a processor contract (see below)

Contracts with our subprocessors

Each subprocessor processes customer personal data under written terms. The table records, for each one, the document that binds it, how that document came to bind it, whether it contains the service-provider terms the California Consumer Privacy Act requires of a business's service providers (Civil Code section 1798.100(d) and section 1798.140(ag), and section 7051 of the regulations), and the mechanism it relies on for international transfers. "In place" means the document names the vendor a service provider and contains each of those terms; where a term is missing we say which. Dates are the vendors' own version dates. We checked each document on 28 October 2026 and keep dated copies.

VendorTerms that bind the vendorHow they bindCCPA service-provider termsTransfer mechanism
Amazon Web Services, Inc.AWS Customer Agreement and AWS Service Terms (22 October 2026), which incorporate the AWS Data Processing Addendum and the AWS CCPA TermsAutomatically, by incorporation into the service termsIn place. The CCPA Terms name AWS a service provider and prohibit selling or sharing, use outside the direct business relationship and combining with other data; they require AWS to tell us if it can no longer meet its CCPA obligations and give us the right to stop and remediate unauthorised use. AWS's duty to comply with the CCPA and our right to verify compliance rest on the Data Processing Addendum's general terms (compliance with applicable law; AWS's ISO 27001 and SOC reports) rather than CCPA-specific wordsEU standard contractual clauses (controller-to-processor and processor-to-processor), the UK Addendum and the Swiss Addendum in the Data Processing Addendum; Amazon.com, Inc.'s Data Privacy Framework certification covers Amazon Web Services, Inc. (active; next due 2 January 2027)
Google Cloud EMEA Limited (Vertex AI, Google Cloud Storage, Google Workspace)Google Cloud Terms of Service (12 October 2026) and Cloud Data Processing Addendum (8 June 2026), including its Appendix 3 "CCPA" termsAutomatically: the Addendum is a URL term of the Terms of Service and prevails over themIn place. Appendix 3 names Google a service provider and contains the prohibitions on selling or sharing, other use and combining, the duty to notify us if Google can no longer meet its obligations, our right to intervene and audit, and assistance with consumer requests. The "same level of privacy protection" promise is expressed as a general undertaking to comply with applicable privacy law rather than in those wordsGoogle LLC's Data Privacy Framework certification (EU, UK extension and Swiss) as Google's alternative transfer solution, with the EU standard contractual clauses as the fallback
Google (the Gemini API, paid services)Gemini API Additional Terms of Service (23 March 2026), which for Paid Services incorporate Google's Data Processing Addendum for Products Where Google is a Data Processor (version 10, 7 May 2026)Automatically, when the API key's Google Cloud project has an active billing account, as every project we issue keys from does (confirmed 28 October 2026)In place. Appendix 3B of that Addendum names Google a service provider and contains each required term, including the "same level of privacy protection" undertakingGoogle's Data Privacy Framework certification, with the EU standard contractual clauses as the fallback
Cloudflare, Inc.Self-Serve Subscription Agreement (12 September 2025), which incorporates the Cloudflare Data Processing Addendum version 6.4 (3 April 2026)Automatically, by incorporationIn place, except that the Addendum has no express prohibition on combining personal data with data from other sources and no express right for us to stop and remediate unauthorised use; it does prohibit selling, sharing and other use, requires notice if Cloudflare can no longer meet its obligations, and gives information and audit rightsCloudflare, Inc.'s Data Privacy Framework certification (active, re-certification under review; next due 15 September 2027); otherwise the EU standard contractual clauses, the UK Addendum and the Swiss variant
Hetzner Online GmbHData Processing Agreement in Accordance with Article 28 of the GDPR, version 1.1 (10 February 2025)Concluded by the customer in the Hetzner console; it is not automatic. Ours is concluded (confirmed 28 October 2026)Not in place. The agreement is written to the GDPR and contains no CCPA terms. Its instruction-only processing, confidentiality, deletion, audit, assistance and subcontractor clauses cover similar groundProcessing takes place only in the EU/EEA under the agreement; no transfer mechanism is needed for our use
Plus Five Five, Inc. (Resend)Terms of Service (27 August 2026), which incorporate Resend's Data Processing Addendum (31 December 2025), pre-signed by ResendAutomatically, on entering the TermsPartial. Section 2.5 names Resend a service provider, prohibits selling personal information and restricts its use to performing the services. It does not use the word "share", has no prohibition on combining, and no duty to tell us if Resend can no longer meet its CCPA obligations. It gives audit rights and assistance with consumer requestsEU standard contractual clauses, the UK Addendum and the Swiss variant; Resend states that it is certified under the Data Privacy Framework
Functional Software, Inc. (Sentry)Sentry Data Processing Addendum version 5.1.0 (29 May 2024), which we accepted in Sentry's console on 28 October 2026By acceptance in the console; it is not automaticIn place. Schedule 4, section 2 names Sentry a service provider and contains each required termSentry's Data Privacy Framework certification first; otherwise the EU standard contractual clauses, the UK Addendum and the Swiss variant
Vercel Inc.Terms of Service (19 October 2026), which incorporate Vercel's Data Processing Addendum (effective 31 March 2026). The Addendum applies to Vercel's Pro and Enterprise plansAutomatically, by incorporation, for those plans; we are on the Pro plan, with model training switched off (confirmed 28 October 2026)Partial. Schedule 4 names Vercel a service provider for customer data and prohibits selling or sharing it, using it for other purposes or outside the direct business relationship. It has no prohibition on combining, and its undertakings to comply with the CCPA, to notify us if it can no longer comply and to remediate unauthorised use are drafted under the heading for data Vercel controls rather than customer dataEU standard contractual clauses, the UK Addendum and the Swiss variant in the Addendum; Vercel states that it is certified under the Data Privacy Framework
TelegramBot Platform Developer Terms and Telegram's privacy policyBy connecting a botNot in place. Telegram offers no data-processing or service-provider terms to bot operatorsNone offered

The transfer mechanisms in these contracts are written for data governed by EU, UK or Swiss law; none of them names the Isle of Man, where we are established. The Isle of Man is recognised by the European Commission as providing adequate protection, which covers our transfers to Google Cloud EMEA Limited in Ireland and to Hetzner in Germany. For transfers to the United States we rely on the vendors' Data Privacy Framework certifications and standard contractual clauses as the contracts set out, and we are confirming the position under Isle of Man law (see section 9 of the Data Processing Agreement).

Not subprocessors

These parties are not our subprocessors, and we list them so the picture is complete:

  • Paddle (Paddle.com Market Limited and its group companies, including Paddle Payments Limited and Paddle.com Inc., depending on the buyer's country). Paddle is our merchant of record: it sells subscriptions to organisations in its own name and processes administrator billing data as an independent controller under its own terms and privacy notice, not as our processor. Paddle shares buyers' names, addresses, email addresses and purchase history with us. Earlier versions of this page listed Paddle as a subprocessor.
  • MaxMind GeoLite2. A local database on our servers that derives a country or region from an IP address at sign-in. No data is sent to MaxMind.
  • Google and Microsoft sign-in. If a member chooses to sign in with Google or Microsoft, those companies act as independent controllers of their own sign-in data.
  • AI tools an organisation connects through the integration feature. These receive data on the organisation's instruction. The organisation chooses them and is responsible for their terms.
  • Marketing-site analytics vendors. These run only with a visitor's consent and process website-visitor data, not customer personal data; see the Cookie Policy.

Changes

This list is versioned. The version and effective date are shown at the top of this page. When the list changes, we post the change on the Legal page's change list as described above and publish a new version of this page. Prior versions are kept in the Legal archive.

Changes and previous versions

  • 28 October 2026v3.2: no subprocessor added. Records the written terms that bind each subprocessor and whether they contain the California service-provider terms (new contracts section); Sentry's data region confirmed as the European Union (Frankfurt) and its data processing addendum accepted on 28 October 2026; Vercel's location confirmed as the United States; the Gemini API paid-services no-training statement quoted from Google's terms; Resend and Sentry listed under their legal names; Paddle moved to the parties that are not subprocessors, as it acts as an independent controller; Hetzner's data processing agreement confirmed as concluded, Vercel confirmed on its Pro plan with model training off, and every Gemini API key confirmed to come from a project with billing enabled; from the code check of 24 October 2026, the Sentry row widened to the application log lines the desktop forwards and the signed-in user's identity, and the Google Cloud row to the model's answers and task groupings it stores.
  • 22 October 2026v3.1: hosting moved to Amazon Web Services in Mumbai, India on 20 October 2026, recorded retrospectively (the objection period runs from this posting); Amazon CloudFront added; Cloudflare now covers domain name service and the hosts that remain on the Hetzner server; Hetzner kept as former hosting pending removal of the production copy and of the earlier report cache, which is no longer used; the endpoint for connected AI tools moved from the Hetzner server to Amazon Web Services on 22 October 2026.
  • 5 October 2026v3.0: list rebuilt for the current hosting (Hetzner, Cloudflare, AWS S3, Google Cloud, Vercel) and operational vendors; DeepInfra marked fallback-only.

Questions about this document: support@screenjournal.ai. Canonical URL: /legal/subprocessors.