Subprocessor register
Invena Labs Limited (trading as invena)
167-169 Great Portland Street, 5th Floor, London W1W 5PF, United Kingdom
Company number 17237229
Registered in England and Wales
Version: 0.12.13 (beta)
Last updated: 2 November 2026
Last reviewed: 2 November 2026
Invena is in beta. Signup is not open yet for new customers. This register describes third-party providers we use today to operate the service. It includes beta-only tooling where that provider may process personal data on our instructions.
For how we handle personal data generally, see our Privacy Policy.
1. Purpose of this page
This page lists third-party providers that process personal data on our instructions to help us operate the Invena service.
We review this list periodically. Where required by law or contract, we will provide notice before material changes take effect. Material changes will also be reflected on this page.
2. What we mean by “subprocessor”
For the purposes of this page, a subprocessor is a third-party processor we engage to process personal data on our behalf in connection with the Invena service.
Some vendors we use for internal development, domain registration, or other operational support may not be subprocessors in the strict UK GDPR sense. Where that is the case, we list them separately under Other service providers.
We engage subprocessors under appropriate contractual terms, including data processing terms where required. Where personal data is transferred internationally, we use safeguards required by UK data protection law and, where applicable, EEA law.
3. Core subprocessors
These providers may process personal data on our instructions. The data categories align with our Privacy Policy (account data, Space metadata, uploaded documents, audit metadata, error monitoring, and transactional email).
| Subprocessor | Service | Personal data processed | Processing location | Notes |
|---|---|---|---|---|
| Supabase | Database, authentication, file storage | Account email; Space and entry metadata; uploaded documents; audit metadata | West Europe (London) | Core service processor |
| Railway | Hosts the Invena API in EU West (Amsterdam), one replica. This is processing, not the primary store | Request and application metadata; application logs; Help support-message text and related support metadata; customer-provided document and entry-field content that the API decrypts where required for the requested operation, or streams, to provide the Service | EU West (Amsterdam), one replica | Supabase in London remains the primary database and file store. Railway hosts the API. Depending on the operation, the API may process readable customer content in memory or in transit. Railway is not the primary customer-content store. Help conversations are also hosted on Chatwoot/UpCloud in the UK. See the Privacy Policy for the processing and transfer explanation. |
| Vercel | Website and product application hosting | HTTP request metadata; session cookies on product app; static and dynamic pages | United States / global edge network | www.invena.app (legal) and app.invena.app (Next.js product UI) |
| Cloudflare | Bot protection on product auth (Turnstile); DNS for invena.app | Challenge tokens; limited client/browser signals used for bot detection; DNS query data | Global edge network | Turnstile is live on app.invena.app login, signup, and related auth forms; Customer DPA on file for that bot protection. Separately, Cloudflare provides DNS for invena.app |
| Resend | Transactional email (invitations, privacy-request acknowledgements, completion notices) | Recipient email address; invitation and customer-request metadata | United States | Transactional email only |
| Stripe | Payment arrangement (Managed Payments) | Billing name and email; payment-method and transaction metadata. Card numbers are not stored in Invena | United Kingdom / EEA / United States | Payment arrangement. Invena Labs Limited provides the Invena service |
| Link, LLC (Onelink / Sold through Link) | Payment seller and invoicing under Stripe Managed Payments | Billing name and email; payment-method and transaction metadata | United States | Named on invoices/receipts as Sold through Link, LLC. Customer-facing brand Onelink; statement may show ONELINK* WWW.INVENA.AP |
| Slack | Internal alerts for new support and privacy requests | Masked reporter email; request reference; request type; response due date | United States | Minimised alerts only; no Space or document content |
| Sentry | Error monitoring and diagnostics | Error stack traces; correlation IDs; scrubbed request metadata | European Union | Error telemetry; we configure scrubbing to reduce personal data |
| UptimeRobot | Uptime and availability monitoring | Health-check metadata; service availability data | United States | Monitors our API health endpoint |
| Microsoft 365 (Exchange Online) | Hosts the company mailboxes we publish, including privacy@invena.app and complaints@invena.app | Email content and addresses of people who write to us, including support and privacy requests | The tenant is registered in the United Kingdom. The data location is shown as EU (Model Clause compliant datacentres) | Used for email we receive and send ourselves at those published addresses. This is separate from the planned Microsoft Graph inbox connect below. This row records mail we already receive. It is not advance notice of a new service |
| Chatwoot (self-hosted on UpCloud UK-LON1) | Support and privacy messaging | Conversation content; contact email addresses; helpdesk account metadata; email received at the published company addresses | United Kingdom (UpCloud UK-LON1) | Self-hosted helpdesk in the United Kingdom. UpCloud provides the hosting. This is not Chatwoot’s cloud service. A message to a published address, including privacy@invena.app, can also appear in the helpdesk |
| Plausible Insights OÜ | Cookieless website analytics (marketing site) | Aggregate page views, referrers, and limited technical traffic data | European Union | Enabled only when configured on invena.app / www.invena.app; not loaded on app.invena.app |
| Google Cloud (Vision API) | Optional Photo / document extraction (OCR preview) | Document bytes you choose to Extract; returned text preview | European Union (eu-vision endpoint for UK/EU beta) | User-directed Extract only; see AI Policy. |
| Google (Gmail API) | Optional inbox connect (read-only) | Connected Gmail address; encrypted OAuth tokens; selected labels/senders; transient scoped message metadata and attachments | United States / Google global infrastructure | gmail.readonly only; no send/delete; no full mailbox replica; tokens removed on Disconnect |
| Microsoft (Graph API) | Planned Outlook / Microsoft 365 inbox connect (read-only) | Connected Microsoft email address; encrypted OAuth tokens; selected folders/senders; transient scoped message metadata and attachments when enabled | United States / Microsoft global infrastructure | Not yet available; planned Mail.Read only, with no send/delete or full mailbox replica. This is separate from Microsoft 365 hosting of Invena’s own mailboxes, listed above |
| Managed map tiles + geocoding provider (planned) | Production Place map tiles and geocoding | Address search; tile/view area; place labels | UK/EU preference, to be confirmed on enable | Inactive until contracted and enabled in the product environment. Listed for advance notice before cutover. |
Microsoft Graph and the planned managed map provider do not receive customer data unless and until those features are enabled.
During closed beta, Place may call public OpenStreetMap / Nominatim endpoints for preview and geocoding (see §3a). We will update this register before enabling a managed tiles and geocoding provider for production.
Trust Centre breach check: the in-app card links to Have I Been Pwned’s free search. You enter your email on their site; Invena does not transmit your email to HIBP for that check. A paid HIBP API integration would be listed here before it goes live.
3a. Closed-beta map preview (community endpoints)
These providers are public / community endpoints, not commercial subprocessors with a negotiated customer DPA. We list them for transparency during closed beta.
| Provider | Service | Personal data processed | Processing location | Notes |
|---|---|---|---|---|
| OpenStreetMap / Nominatim (community endpoints) | Beta Place map preview and geocode / reverse geocode | Address search strings; tile/view coordinates; returned place labels | Global public endpoints | Closed beta only. No customer DPA. Replace before open signup / GA with the managed provider in §3. Not used for vault document storage. |
4. Internal processing components
These tools form part of our technical controls. They are not external subprocessors.
| Component | Purpose | Data processed | Location |
|---|---|---|---|
| Upload scanner (ClamAV) | Checks customer document, image, and inbox-file uploads before they are saved, on the terms in the statement below. Operated by Invena. Not a separate scanning company | File bytes during scan only, on an ephemeral basis | EU West (Amsterdam), same region as the Invena API |
When our scanner is switched on, document, image and inbox-file uploads are checked before they are saved. If a check detects a problem or cannot be completed, the upload is not saved. The scanner is switched on as of 30 October 2026. We do not send these files to a separate scanning company. This statement covers customer uploads only; it does not cover an inbox item later filed to an Entry, which copies the already-checked file without another scan, or files and copies generated by Invena, including account exports and Entry handovers. If the scanner is switched off, uploads may be saved without this check.
5. Other service providers
These providers support Invena operationally but do not normally process customer content on our behalf in the course of providing the Invena service to you.
| Provider | Purpose | Processes customer personal data? | Notes |
|---|---|---|---|
| GoDaddy | Domain registrar for invena.app | No, subject to ordinary registration records | Registrar only. GoDaddy does not provide DNS for invena.app. DNS for invena.app is provided by Cloudflare |
| GitHub | Source code hosting | No customer vault data | Development and source control only |
6. Data residency summary
Primary customer content — including Spaces, entries, and documents — is stored in Supabase in London (United Kingdom), as described in our Privacy Policy. The Invena API and the upload scanner run in Amsterdam (EU West). The API may process or stream readable document and entry-field content when a feature requires it. That is processing in Amsterdam, not storage of the primary copy there. Storage location and processing location are not necessarily the same.
Some subprocessors process data in other jurisdictions — for example the United States for transactional email, website and product edge hosting, payment, and certain monitoring services, the EEA for API hosting and error monitoring, and the United Kingdom for primary storage — where necessary to provide the service. A transfer from the United Kingdom to the EEA is still an international transfer. The transfer assessment for the Amsterdam API is not finished, and this register does not describe that deployment as an approved transfer safeguard.
7. Changes to this register
We may add, remove, or replace subprocessors as the service develops. Where required by law or contract, we will provide notice before a material change takes effect and before the new processing begins.
Notice approach: Our operational aim is to give reasonable advance notice (typically 14 days where practicable) before adding a subprocessor that materially changes how we process your personal data. This timing is an operational target, not a substitute for any legal or contractual notice requirement. We update this page and our Privacy Policy at the same time.
App Store privacy labels must reflect our actual data practices — separate from subprocessor notice timing.
Contact
Privacy questions: privacy@invena.app