signafAIde sub-processors
Version: 1.1
Last updated: 14 November 2026
AIME TECH UK LIMITED uses the providers below to run the hosted signafAIde Service. "Customer Data" is the data in customers' records, for which we are a processor. "Our data" is account, billing and analytics data, for which we are the controller. A self-hosted witness uses none of these unless the customer configures it to.
We give at least 30 days' notice of a new sub-processor, as set out in the data processing agreement.
Sub-processors #
| Provider | Purpose | Data | Location | Transfer safeguard |
|---|---|---|---|---|
| Google Cloud (Google Cloud Platform) | Hosting the Service, database and backups | All Customer Data and our data | United Kingdom (London, europe-west2) | Not needed: the data stays in the UK |
| Brevo (Sendinblue SAS) | Sending sign-in links, invitations and alert emails, from [email protected] | Recipient email addresses; the email text, which for alerts holds project, agent and error details | European Union | Not needed beyond the UK's adequacy regulations for the EEA |
| Stripe Payments Europe, Ltd. and Stripe, Inc. | Payments, subscriptions, invoices, usage metering | Billing email, organisation id, payment details (collected by Stripe directly), monthly overage counts | Ireland, United States and others | UK Extension to the EU-US Data Privacy Framework; Standard Contractual Clauses with the UK Addendum |
| Cloudflare, Inc. | Edge network in front of the Service; staff access control for the operator admin (Cloudflare Access) | Request traffic passing through the edge, including IP addresses and request content; staff email addresses for admin access | Global network; United States | UK Extension to the EU-US Data Privacy Framework; Standard Contractual Clauses with the UK Addendum |
| GitHub, Inc. | Console sign-in with GitHub (OAuth), only for users who choose it | The user's GitHub identity; GitHub sees the sign-in request | United States | UK Extension to the EU-US Data Privacy Framework; Standard Contractual Clauses with the UK Addendum |
Notes:
- Cloudflare: the Service is served through Cloudflare, where encrypted traffic is terminated at the edge, so Cloudflare can process Customer Data in transit, including stored content when a customer sends it. Cloudflare is therefore listed as a sub-processor for Customer Data as well as for our data.
- GitHub: GitHub acts mainly as an independent identity provider chosen by the user. We list it for transparency.
- Support is by email to [email protected].
Public services that are not sub-processors #
The Service uses public, open services to give records independent timing evidence. They are run by third parties for anyone to use, under no contract with us. We do not treat them as sub-processors because they receive no personal data and no Customer Data in readable form.
| Service | What it does for signafAIde | What it receives from us |
|---|---|---|
drand, League of Entropy (api.drand.sh, api2.drand.sh, drand.cloudflare.com) | Public randomness rounds; each batch carries the newest round to show it was not written earlier ("not before") | Nothing. We only read published rounds |
OpenTimestamps calendars (a.pool.opentimestamps.org, b.pool.opentimestamps.org, a.pool.eternitywall.com; upgrades from alice.btc.calendar.opentimestamps.org, bob.btc.calendar.opentimestamps.org, finney.calendar.eternitywall.com, btc.calendar.catallaxy.com) | Public timestamps ("not after") | One SHA-256 hash per anchor, about once an hour, that combines the batch hashes of all customers created since the last anchor. It cannot be reversed to any record. Calendar operators also see our server's IP address |
Public timestamp explorers (mempool.space, blockstream.info) | Confirming a public timestamp against the real block header of the public ledger before an anchor is shown as confirmed | Requests for public block headers by block height. Nothing about customers |
The hash submitted to the timestamp calendars is recorded permanently in their proofs and, through them, in the public ledger behind the timestamps. It cannot be deleted.
The open-source verifier, when run by a customer or auditor, may contact a block explorer (by default mempool.space) from their own machine. That is outside the Service.