Privacy Policy
Last updated 20 November 2026
Welcome to ERPoida (“we,” “us,” or “our”). We are committed to protecting your privacy and personal information. This Privacy Policy outlines how we collect, use, disclose, and safeguard your information when you use our website and services.
This page covers this website (the marketing site at erpoida.com) and the ERPoida application when we host it for you, including the AI connectors described below. If you run ERPoida on your own servers, the handling of the data inside it is governed by the agreement covering that installation, not by this page.
1. Company Information
Company Name: ERPoida
Contact Information: [email protected]or our contact page
2. Services Provided
ERPoida is an AI-native ERP for the whole business: CRM, projects and tasks, HR and timesheets, invoicing and accounting, documents and Drive in one workspace, with optional AI connectors for assistants such as Claude and ChatGPT.
3. Analytics, and your choice about it
We use Google Analytics 4 to see which parts of this page people read. It isoff until you allow it. Nothing from Google is loaded, and no analytics cookie is set, unless you press “Allow” on the banner. If you press “No thanks”, or simply never answer, no analytics code runs at all — we do not load it in a disabled state, we do not load it.
If you do allow it, Google Analytics sets cookies named _ga and_ga_<id> to tell one visit from another, and sends your page views, approximate location, device and browser to Google, which may process it outside the EU. Your IP address is truncated before storage. We have advertising features switched off, so this is measurement only and your visit is not added to any advertising audience. The legal basis is your consent, Article 6(1)(a) GDPR.
You can change your mind at any time and it takes one click: “Cookie settings” at the bottom of any page. Withdrawing deletes the analytics cookies and reloads the page without the tracking code. Withdrawing is as easy as allowing, by design.
In the ERPoida application we ask the same question separately, with the same banner, the same two equal buttons and the same rules. If you allow it there, we use Google Analytics to learn which screens are used, how fast pages load, and how often errors occur, so we can fix problems and improve the product. We deliberately send far less than Google Analytics normally collects: only the type of screen (for example “invoice detail”, never which invoice), with every ID, search term, link token and page title removed before anything leaves your browser; for errors only their category and status code, never the message; and your interface language. We send no user ID, name, email address, workspace or business data. Pages opened by your own customers, such as payment and share links, never show the banner and are never measured. You can change your choice at any time under “Cookie settings” in your user menu or below the sign-in form.
To remember your answer we store one cookie of our own,erpoida_consent, holding the single word granted ordenied for six months. It is what stops us asking again on every page, it is needed for that purpose alone, and it is set whichever way you answer.
If you switch the site’s language, a second cookie of our own,erp_lang, stores en or de for one year so we keep showing the language you picked. Without it, your first visit is shown in German if your browser’s preferred language is German or you are visiting from Germany (country taken from the request by our CDN, Cloudflare), and in English otherwise. Your IP address is not stored for this.
Counting where visitors come from (no cookies)
When you arrive on erpoida.com from another site, your browser sends one request to our application server with only the name of the referring website (for examplegoogle.com or chatgpt.com), any campaign tags in the link (utm_source, utm_medium, utm_campaign) and the section of our site you landed on. We add one to a daily counter for that combination. We do not store your IP address, browser details or any identifier, and nothing is saved on your device, so this needs no consent and cannot be traced back to you. Legal basis: our legitimate interest in knowing which channels bring visitors (Art. 6(1)(f) GDPR).
The same values are added to our links into the ERPoida application. If you then create an account, they are stored with your account as its sign-up source. Only if you accepted analytics above do we keep them in your browser’s session storage for the rest of the visit, so a sign-up a few pages later is still attributed; this ends when you close the tab.
4. When you request a demo, or write to us through the contact page
Both forms post what you typed to our own server, where it is stored so we can reply to you.
We store your name, your email address, your company if you gave one, whatever you wrote in the message box, which language the site was in, the path of the page you sent it from, and your browser’s user-agent string. The contact form also stores which topic you chose (support, sales or a demo). The user agent is kept only because it is the most useful signal when sorting real enquiries from automated spam.
We deliberately do not store your IP address with the submission. We use what you send to reply to you and to follow up about erpoida, and for nothing else. We do not sell it and we do not pass it to anyone outside ERPoida. The legal basis is Article 6(1)(b) GDPR — taking steps at your request prior to a contract — and our legitimate interest in answering business enquiries, Article 6(1)(f).
We keep it while the conversation is live and for up to two years afterwards, so we can pick up a thread you started. Ask us to delete it sooner and we will, without asking why.
5. Using the ERPoida application
When we host your ERPoida workspace, we store what you put into it so the application can work: your account (name, email, password hash), the people you invite and their roles, and the business records you create — contacts and companies, projects and tasks, HR and timesheet entries, invoices and accounting entries, and the documents and files you upload to Drive, along with any comments and attachments on these records.
We use this to run the application for you, to let your team collaborate inside a workspace, and to answer support requests. The legal basis is Article 6(1)(b) GDPR (performance of the contract covering your workspace) and, where applicable, Article 6(1)(c) (statutory retention of accounting records, see below).
Gmail and Google Workspace integration
A user can connect their own Gmail or Google Workspace mailbox, and an administrator can connect a shared inbox (for example support@). This only happens after the mailbox owner signs in with Google and approves access on Google’s consent screen. Depending on the mode chosen, ERPoida requests read-only access (gmail.readonly), or read and send access (gmail.modify andgmail.send), plus your basic Google profile (name, email address) to identify the connected account.
What we access and store. Email headers (sender, recipients, subject, date), message text and attachment metadata (file name, type, size) of the connected mailbox. Spam and newsletters are not stored. Attachments are not copied: they are fetched from Google only when you open one or when a flow you enabled needs it (for example to turn a supplier invoice into a draft bill). The OAuth tokens Google issues are stored encrypted (AES-256-GCM).
How we use it. Only to provide the features you use in ERPoida: show your email in the application, group it into conversations, link it to your contacts, companies, deals, tickets and other records, let your team answer and assign it, send the replies you or your flows write, and run the email automations you turn on. If your workspace enables AI classification or extraction, the text of the email is processed by the built-in assistant through AWS Bedrock in the EU as described in section 6, only to produce that result.
What we never do. We do not sell Google user data, use it for advertising, or use it to train or improve general-purpose AI or machine-learning models. We do not transfer it to third parties except as needed to provide the features above, to comply with law, or as part of a merger or acquisition with notice to you. Our staff do not read your email unless you ask us to (for example in a support request), it is needed for security or abuse investigation, or the law requires it.
ERPoida’s use and transfer of information received from Google APIs to any other app will adhere to theGoogle API Services User Data Policy, including the Limited Use requirements.
Retention and deletion. Email linked to a business record is kept for the period your workspace sets (24 months by default); the text of other email is removed after 30 days. Disconnecting a mailbox in ERPoida deletes its email, except email that is linked to a record or also held by another connected mailbox of your workspace; “Delete all” removes that too. Blocking a sender removes their email already synced. You can also revoke ERPoida’s access at any time atmyaccount.google.com/permissions, or ask us at [email protected] to delete your data. The legal basis is Article 6(1)(b) GDPR (providing the integration you connected).
6. AI connectors — Claude, ChatGPT and the Model Context Protocol (MCP)
ERPoida can be connected to AI assistants such as Anthropic’s Claude and OpenAI’s ChatGPT through the Model Context Protocol (MCP). This only happens after a user signs in and explicitly approves access for one workspace through an OAuth consent screen — nothing is shared with an AI assistant before that approval.
Once approved, the AI assistant can call a limited set of tools against your workspace — for example, listing or creating records, reading documents, or starting a timer — and whatever those tools return (business records, document contents, comments) is sent to the assistant for that conversation. Access is limited by the signed-in user’s role permissions: an AI assistant can never see or do more than that user could through the application itself.
ERPoida does not send this data to Anthropic or OpenAI itself. Your AI assistant requests it from ERPoida, on your behalf, through the connection you approved. Which provider then processes it, and where, is determined by the assistant account you connected and your own agreement with that provider (for users in the EEA: Anthropic Ireland, Limited or OpenAI Ireland Ltd). Both providers may process and store data in the United States; EU data residency is only offered on some of their business plans and has to be set up on your side. SeeAnthropic’s privacy policyandOpenAI’s privacy policy.
You can revoke a connector’s access at any time, and it takes effect immediately: from Settings → Access Tokens in the application, or by removing the connector in Claude or ChatGPT’s own settings. See ourMCP setup guide for details.
The assistant built into ERPoida
The AI assistant inside the application is a different thing. When you use it, ERPoida sends your request and the workspace data needed to answer it to Anthropic’s Claude models through Amazon Web Services (AWS Bedrock) in the European Union(Frankfurt region, with processing kept within AWS’s EU regions). AWS acts as our processor under its data processing addendum; AWS does not use this data to train models and does not share it with Anthropic. Amazon Web Services EMEA SARL is established in Luxembourg; because its parent company is in the United States, access by US authorities cannot be ruled out entirely, which is covered by the EU-US Data Privacy Framework and the EU Standard Contractual Clauses. The legal basis is Article 6(1)(b) GDPR (providing the feature you asked for).
Feedback you send us from the application
If you use the Feedback button in the application, we store your message together with your name, email address, workspace and the page type you were on, and email it to our team so we can read and answer it. We use it only to improve ERPoida and to reply to you. The legal basis is our legitimate interest in improving the product and your request to be answered, Article 6(1)(f) GDPR. Ask us at any time and we will delete it.
7. What we log
We keep an action log for your workspace recording who did what: for API and AI connector activity, this is the tool or endpoint called, the arguments passed (with secrets redacted), the outcome, and the time. Inline file contents and binary file bytes are excluded from this log, and large results are reduced to a summary (size, number of rows, record IDs). Entries are deleted automatically after 30 days; entries for changes to financial records (invoices, bookings, payments, purchasing, payroll, stock) are kept for 8 years, the statutory retention period under German tax and commercial law. The legal basis is our legitimate interest in security, troubleshooting and abuse prevention, Article 6(1)(f) GDPR, and — for financial records specifically — our obligation to keep an audit trail under German accounting law.
8. Hosting and sub-processors
When we host your workspace, the application and its database run on infrastructure in the European Union. Processing your business data also involves the sub-processors named on this page for the specific purpose described — our payment provider Stripe (see below) and, for the built-in AI assistant, Amazon Web Services in the EU (see section 6). AI connectors such as Claude or ChatGPT are not our sub-processors: you connect them yourself, under your own agreement with that provider. We do not use any other sub-processor to read or write your workspace data.
9. Fonts
The page loads the Inter Tight typeface from Google Fonts, which means Google receives the request for the font files, including your IP address, as it would for any web font served from their network. This happens regardless of your analytics choice because it is part of rendering the page. If that matters for your organisation, tell us and we will self-host the font instead.
10. What else the server sees
Our web server and the reverse proxy in front of it write ordinary access logs when you request a page — the request, the time, the response status and your IP address. These exist to keep the site running and secure, are not used to build any profile of you, and are not combined with anything above. The legal basis is Article 6(1)(f).
11. Online payments and recurring subscription payments
If you pay for an ERPoida subscription, this section also covers the application. Subscriptions and invoices are kept in ERPoida only; our payment provider Stripe only collects payment against our invoices.
You enter card details only on pages hosted by Stripe. ERPoida never receives the full card number or the security code (CVC). We store only the Stripe references to your customer account and payment method, the card brand, the last four digits, the expiry month and year, and your consent to recurring payments (the time and the version of the terms). We use these to show you the card on file, warn you before it expires, and trigger the charge for ERPoida invoices.
The legal basis is Article 6(1)(b) GDPR (performance of a contract) and, for tax and accounting records, Article 6(1)(c) GDPR.
The recipient and processor is Stripe Payments Europe, Ltd., Dublin, Ireland. Data may be transferred to Stripe, Inc. in the USA under the EU-US Data Privacy Framework or the EU Standard Contractual Clauses. SeeStripe’s privacy policy.
We delete the card details we hold when you remove the card or the subscription ends. Payment and invoice records are kept for the statutory retention periods (§ 147 AO, § 257 HGB, up to ten years). Your rights below are unchanged.
12. Your rights
You can ask what we hold about you, ask for a copy in a portable form, ask for corrections, ask us to erase it, ask us to restrict how we use it, and object to our using it. Where we rely on consent, you can withdraw it without affecting what was lawful beforehand. Write to[email protected] and we will answer within 30 days. You also have the right to complain to a data protection supervisory authority.
13. International Data Transfer
Hosted workspaces run on infrastructure in the European Union. Where we use providers based outside the EU (Google, Stripe, and AWS’s US parent company, as described above), your information may be processed in other countries, including the United States, under the safeguards named in each section. Data your own AI assistant retrieves through a connector is governed by your agreement with that provider (section 6).
14. Children’s Privacy
Our services are intended for businesses, including small and medium enterprises. We do not knowingly collect personal information from individuals under the age of 16.
15. Complaints and Dispute Resolution
If you have any complaints regarding our handling of your personal information, please contact us at [email protected]. We will work with you to resolve any issues promptly.
16. Legal Jurisdiction
This Privacy Policy is governed by the laws of the European Union (GDPR) and applicable local laws.
17. Changes to This Privacy Policy
If this changes, the date at the top of the page changes with it. There is no mailing list to notify, because we do not run one from this site.

