Fideria uses the providers below to deliver the AI Investment Overview platform. Contractual protections differ by provider. Fideria's current Pro plan with Lovable is governed by Lovable's Terms of Service and Privacy Policy; no data processing agreement is in force between Fideria and Lovable. Lovable states that its own provider agreements include transfer and use restrictions. Its current upstream sub-processor record is published at trust.lovable.dev/subprocessors.
Where data is stored and where it is processed
Stored. The application database and its backups are currently set to Stockholm, Sweden. The account owner's per-project Cloud setting is the authoritative record. This is the current configuration, not a vendor commitment that the region will remain unchanged. The platform does not publish separate locations for server-side compute or file storage.
Processed. Some data leaves that database to be processed. Application traffic passes through Cloudflare's global network. The Lovable AI gateway entrypoint is hosted in the EU, but prompt content, including text extracted from invoice emails, is sent to model-provider endpoints and processed in the United States. Lovable states that transfers outside the EEA, UK, Switzerland or Brazil rely on the mechanisms in section 12 of its Privacy Policy, including clauses it has entered with its service providers that give customers directly enforceable rights. Those mechanisms apply on the current plan, but there is no data processing agreement between Fideria and Lovable. Lovable does not publish how long prompts or outputs are retained at the gateway or model providers, so Fideria cannot state a retention period.
Used for every customer
| Sub-processor | Purpose | Data categories | Region |
|---|---|---|---|
| Supabase (via Lovable Cloud) | Application database and authentication, provided through Lovable Cloud. | Account and profile data, audit log, customer content and integration credentials (stored encrypted). | The database and its backups are currently set to Stockholm, Sweden. This is a per-project setting visible to the account owner, not a vendor commitment that the region will remain unchanged. |
| Cloudflare | Serves the published application and custom domain as a global CDN and reverse proxy, with DDoS protection. | IP address, request metadata, application traffic in transit. | Global network. Requests are handled at the Cloudflare location nearest the user and are not limited to the EU. |
| Lovable | Operates the application platform, AI gateway, connected-mailbox relay and application email service. The gateway entrypoint is hosted in the EU and sends inference requests to model-provider endpoints in the United States. | Prompt content, including text extracted from invoice emails, passing through the AI gateway. Mailbox access tokens and mailbox API traffic. Recipient address and content of emails sent by Fideria. | Global processing applies. AI prompt content is processed in the United States. The platform does not publish separate locations for server-side compute or file storage, retention periods for gateway or model-provider content, terms governing mailbox access, or which provider delivers a given application's email. |
| Google (Gemini models, via the Lovable AI gateway) | Google-model requests through the Lovable AI gateway for the in-product assistant (Morgan), board report drafting, recommendations and invoice parsing. Also summarises public vendor news and industry articles, which contain no customer data. The platform does not identify the provider endpoint used for a given request. | Prompt content: the customer's portfolio, spend and governance figures, questions typed into the assistant, titles and descriptions of uploaded documents, and invoice email text from a connected mailbox. | United States for model inference. The platform states that its agreements restrict model providers to using content to deliver the service, including no training on it. It does not publish how long prompts or outputs are retained, so Fideria cannot state a retention period. |
| OpenAI (via the Lovable AI gateway) | OpenAI-model requests through the Lovable AI gateway for revising board reports, and speech-to-text and text-to-speech for the voice assistant. The platform does not identify the provider endpoint used for a given request. | Board report text and revision instructions. Recorded voice audio and the text read aloud. | United States for model inference. The platform states that its agreements restrict model providers to using content to deliver the service, including no training on it. It does not publish how long prompts or outputs are retained, so Fideria cannot state a retention period. |
| Google (sign-in) | Sign in with Google, for users who choose it. | Email address, name, Google account identifier. | Google's service regions apply. |
Used only when a customer connects them
The services below are used only for a customer who connects them. They are the customer's own providers. Fideria reads from them with the customer's authorisation. Data written to the application database is stored according to the current per-project setting described above.
| Sub-processor | Purpose | Data categories | Region |
|---|---|---|---|
| Google (Gmail invoice mailbox) | Applies only when the customer connects a Gmail mailbox for invoice scanning. A nightly job reads recent email to find invoices from AI vendors. The text of each likely invoice is sent to an AI model (Google Gemini, via the Lovable AI gateway) to read out vendor, amount, currency, date and invoice number. | Email message content from the connected mailbox: sender, subject, date and body text of messages from the last 90 days that come from a known AI vendor or mention an invoice or receipt. Attachments are not read. | Google's service regions apply to mailbox access. Invoice text is sent through the Lovable AI gateway and processed in the United States. The platform does not publish terms governing mailbox access or whether content is retained in transit. |
| Microsoft (Outlook invoice mailbox) | Applies only when the customer connects an Outlook mailbox for invoice scanning. A nightly job reads recent email to find invoices from AI vendors. The text of each likely invoice is sent to an AI model (Google Gemini, via the Lovable AI gateway) to read out vendor, amount, currency, date and invoice number. | Email message content from the connected mailbox: sender, subject, date and body text of the most recent messages from the last 90 days. Only messages matching a known AI vendor are sent for parsing. Attachments are not read. | Microsoft's service regions apply to mailbox access. Invoice text is sent through the Lovable AI gateway and processed in the United States. The platform does not publish terms governing mailbox access or whether content is retained in transit. |
| Microsoft (Entra ID, Microsoft 365, Graph) | Applies only when the customer connects its Microsoft tenant or configures Entra ID for SAML single sign-on. Reads the app inventory, licence assignments, Copilot seat usage and audit events. | Names, email addresses and directory metadata of users, licence and seat assignments, per-user activity dates, audit event metadata. | Microsoft's service regions apply. Data written to the application database is currently stored in Stockholm, Sweden. |
| Google Workspace | Applies only when the customer connects its Google Workspace. Reads the user directory and sign-in audit events to find AI apps in use. | Names, email addresses, directory metadata, third-party app authorisation and audit metadata. | Google's service regions apply. Data written to the application database is currently stored in Stockholm, Sweden. |
| Okta | Applies only when the customer connects Okta or configures it for SAML single sign-on. Reads the list of active applications and the users assigned to them. | Application names, assigned users, email addresses, directory metadata. | Okta's service regions apply. Data written to the application database is currently stored in Stockholm, Sweden. |
| GitHub | Applies only when the customer connects its GitHub organisation. Reads Copilot seat billing and organisation membership. | Member usernames, Copilot seat assignments and last activity dates. | GitHub's service regions apply. Data written to the application database is currently stored in Stockholm, Sweden. |
| OpenAI (customer's ChatGPT Enterprise or API account) | Applies only when the customer connects its own OpenAI account. Reads seat, usage and cost data. | Workspace member names and email addresses, seat status, usage and cost figures. No conversation content. | OpenAI's service regions apply. Data written to the application database is currently stored in Stockholm, Sweden. |
| Anthropic (customer's Claude for Work or API account) | Applies only when the customer connects its own Anthropic account. Reads seat, usage and cost data. | Workspace member names and email addresses, seat status, usage and cost figures. No conversation content. | Anthropic's service regions apply. Data written to the application database is currently stored in Stockholm, Sweden. |
| Slack | Applies only when the customer connects its Slack workspace. Reads the list of installed apps and bots to find AI tools. | Workspace name, bot and app user names. No messages or channel content. | Slack's service regions apply. Data written to the application database is currently stored in Stockholm, Sweden. |
| Notion | Applies only when the customer connects its Notion workspace. Reads the list of workspace users and integrations to find AI tools. | User and integration names. No page content. | Notion's service regions apply. Data written to the application database is currently stored in Stockholm, Sweden. |
Change notifications
Fideria notifies customers without undue delay after it has itself been notified of a sub-processor addition or replacement. The customer's objection period starts with Fideria's notification and is never shorter than the objection period available to Fideria from its upstream provider. For upstream changes, notice is given as soon as Fideria knows, not a fixed number of days in advance. Customers may object on reasonable data-protection grounds. If an objection cannot be resolved, the customer may terminate the affected part of the Service in accordance with the master agreement.
To subscribe to Fideria's change notifications, email privacy@fideria.ai with the subject line "Sub-processor updates".
Deletion and backups
Fideria deletes the customer's records from the live database. Backup copies age out according to a retention period that Lovable does not publish. Selective deletion of a customer's records from backups is not possible.
Lovable's platform-level deletion operates per project or account: data first becomes inaccessible, then is permanently removed, including from backups, after a retention period Lovable does not publish. This is not the same as Fideria deleting one customer's records in a shared live database.