Privacy policy of the service
This English version is a convenience translation. Only the German version is legally binding.
This privacy policy informs you about the processing of personal data when using Aimarage at app.aimarage.com (the "Service") pursuant to Articles 13 and 14 of the General Data Protection Regulation (GDPR) and the Austrian Data Protection Act (DSG).
1. Controller
Dr. Peter Mayer, Webservice Mayer (sole proprietorship)
Würzburgerweg 18, 4840 Vöcklabruck, Austria
Email: mail@aimarage.com
No data protection officer has been appointed because there is no legal obligation to do so. Please send data protection enquiries to the email address above.
2. Two roles: controller and processor
2.1 We are the controller for the data of customers as contracting parties and of users of the Service (account, login, subscription, billing, communication). This privacy policy applies to that data.
2.2 For the data that customers process in the Service for their own projects (e.g. content of websites and documents, incoming emails, comments, contacts, drafts), we act as the customer's processor under Article 28 GDPR. If a customer uses the Aimarage counter on its website, we process the page views of that website's visitors as the customer's processor. The customer is then the controller, and the data processing agreement (DPA) at app.aimarage.com/avv applies. In that case, data subjects should contact the respective customer.
3. What data we process, why and on what legal basis
3.1 Registration and account
Data: name, email address, name of the workspace, company name and business address (street, postal code, city, country), optionally the VAT identification number, confirmation that the contract is concluded for an already existing business (with time and version), time and version of acceptance of the Terms and DPA and of acknowledgement of this privacy policy, a hash of the IP address at that time, team role, settings.
Purpose: creating and maintaining the account, proof of acceptance of the contract and of business status, protection against misuse. If the information appears contradictory (e.g. a company name like a personal name without legal form and without VAT ID), we receive an internal review note; the account is not blocked automatically.
Legal basis: for anyone registering as a customer or acting for their company: performance of a contract and pre-contractual measures (Art. 6(1)(b) GDPR). For employees and agents of a customer who are not themselves a contracting party: our legitimate interest and that of the customer in providing them with the service booked by the customer (Art. 6(1)(f) GDPR). For proof of acceptance of the contract and protection against misuse: our legitimate interest (Art. 6(1)(f) GDPR). Acknowledging this privacy policy at registration is not consent; we merely document it.
Invited team members: If an owner or admin of a workspace invites you to the team, we receive your email address and the intended role from that person (usually your employer or client). We then send you an invitation email with the name of the workspace, the name of the inviting person and a link to this privacy policy. The invitation is valid for 7 days. Owners and admins can delete an invitation that has not been accepted at any time; at the latest it is deleted together with the workspace.
3.2 Login
Data: email address, one-time login codes (stored only as a cryptographic hash, valid for 10 minutes), passkeys (public key, device type, name, time of last use; the private key never leaves your device), sessions (hash of the session key, login method, browser identifier, time of last activity), counters for login attempts (with a hash of the IP address or email address).
Purpose: secure login without a password, protection against attacks, displaying and ending active sessions.
Legal basis: Art. 6(1)(b) GDPR or, for team members who are not themselves a contracting party, Art. 6(1)(f) GDPR (as in section 3.1); protection against misuse Art. 6(1)(f) GDPR (legitimate interest in a secure service).
3.3 Subscription and payment
Data: plan, billing period, trial and subscription status, customer ID at the payment provider, billing address, billing email, country, VAT identification number, invoices. The customer enters payment data (e.g. credit card number) directly with the payment provider Stripe; we do not receive it.
Purpose: handling the subscription, invoicing, VAT, dunning.
Legal basis: Art. 6(1)(b) GDPR; retention under commercial and tax law (Art. 6(1)(c) GDPR in conjunction with § 132 BAO and § 212 UGB).
3.4 Use of the Service and AI processing
Data: content that you and your team enter or connect (project details, goals, strategy, drafts, documents, website content, messages to the agent), logs of AI calls (type of task, model, token counts, cost, time), usage and storage consumption.
Purpose: providing the Service, creating drafts with AI, enforcing plan limits, cost control, troubleshooting.
Legal basis: Art. 6(1)(b) GDPR or, for team members who are not themselves a contracting party, Art. 6(1)(f) GDPR (as in section 3.1). Where personal data of third parties is processed, we act as the customer's processor (section 2.2).
AI notice: So that the Service can generate drafts, analyses and replies, your input and the project content required for it are transmitted to an AI provider (section 4) and processed there. We do not use this content to train our own models; what the AI provider may do with the data is stated in section 4. AI output consists of suggestions and may be incorrect. The Service makes clear that the agent is an AI; content generated by the AI is additionally marked in machine-readable form (Terms 4.3).
3.5 System emails
Data: email address, name, content of the message (e.g. login code, welcome email, team invitation, notices on trial, payment and limits).
Purpose and legal basis: communication for the performance of the contract (Art. 6(1)(b) GDPR); for invitations and emails to team members who are not themselves a contracting party, our legitimate interest in providing the Service (Art. 6(1)(f) GDPR). We do not send marketing newsletters without separate consent.
Daily email: The daily email in the morning summarises what is due for you in the Service. You can switch it off at any time under Settings > Profile or unsubscribe via the unsubscribe link at the end of each daily email, even without logging in; for this purpose the email contains the List-Unsubscribe and List-Unsubscribe-Post headers. After unsubscribing, the summary remains visible only in the dashboard.
Push notifications of the iPhone app: If you switch on notifications in the iPhone app, we store the device identifier for notifications (push token), the language and the time of the last notification with your session. If a draft is awaiting approval, we send a notification with the title of the task via the Apple Push Notification Service (section 4); if there are several drafts, only their number. We delete the device identifier when you switch off notifications, log out or Apple reports it as invalid; the list of notifications sent after 60 days. Legal basis: Art. 6(1)(b) GDPR or, for team members who are not themselves a contracting party, Art. 6(1)(f) GDPR (as in section 3.1).
3.6 Support and contact
If you write to us, we process your email address, your name and the content of your message to handle the enquiry (Art. 6(1)(b) GDPR, or Art. 6(1)(f) GDPR for general enquiries). Emails to mail@aimarage.com are forwarded by our domain provider prohost networks GmbH (brand w3w) to our mailbox at Proton AG in Switzerland (section 4). We keep the correspondence as long as needed to handle and follow up the enquiry and delete it afterwards unless a statutory retention obligation applies or it is needed to establish or defend legal claims. If you send us project content with a support request or ask us to look into your project, we process this content as a processor (section 2.2, DPA section 8.2).
3.7 Server logs
When the Service is accessed, the server processes technically necessary connection data (IP address, time, requested address, browser identifier). The web server does not keep access logs permanently. The logs of the services (application, background worker, web server, database) with error and operational messages are kept for no more than 14 days and then deleted automatically; older entries are removed daily. In addition, they are limited in size (no more than five files of 10 MB per service, older entries are overwritten) and deleted completely whenever a new version of the Service is deployed. Error messages that we collect separately in a list to fix faults are also kept for no more than 14 days and then deleted automatically. In individual cases, logs and error messages may contain IP addresses or email addresses. The purpose is to deliver the Service, detect errors and fend off attacks; the legal basis is our legitimate interest in the secure operation of the Service (Art. 6(1)(f) GDPR). In the event of a specific security incident, the necessary entries may be kept until the matter is resolved and, where applicable, to establish or defend legal claims.
3.8 Deleting and exporting
You can delete data yourself in the Service: individual content and projects (immediately, including files; we only record that and when a project was deleted, without content), your user account (immediately; workspaces in which you are the only member are deleted as described below) and, as owner, the entire workspace. A deleted workspace is blocked immediately, the subscription ends at the end of the current period, and after 30 days all data including files is permanently deleted; we send a reminder by email 7 days beforehand. Until then, the owner can export the data. The owner starts the export (ZIP with JSON files and the uploaded files, without credentials, keys and hashes) after re-confirmation; the download link is valid for 7 days, after which the file is deleted. Instructions for deleting your account, including without logging in, are at aimarage.com/en/delete-account.
4. Recipients and processors
We use the following service providers. Contracts under Article 28 GDPR are in place with processors.
- Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany - hosting of server, database and file storage (Object Storage) as well as backups; data centres in Germany. Concerns all data stored in the Service.
- AI provider Anthropic, Anthropic Ireland, Limited, 6th Floor, South Bank House, Barrow Street, Dublin 4, D04 TR29, Ireland, together with Anthropic, PBC, 548 Market St, PMB 90375, San Francisco, CA 94104, USA - generating drafts, analyses and replies with the language model Claude. The respective task, your input and the project content required for it (which may also contain personal data) are transmitted; the generated text comes back. Processing in the USA. Transfers to the USA based on standard contractual clauses (Art. 46 GDPR) under the provider's data processing agreement. Under its commercial terms, Anthropic may not use data submitted via the API to train its models; according to its own information, Anthropic deletes inputs and outputs within 30 days unless longer retention is required to enforce its usage policy or by law.
- Sendinblue SAS (Brevo), 106 boulevard Haussmann, 75008 Paris, France - sending system emails; storage in the EU, access by Brevo group companies and service providers in third countries (including the USA) possible, safeguarded by standard contractual clauses or the EU-US Data Privacy Framework.
- Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland, together with Stripe, Inc. (USA) - payment processing, invoices, customer portal, tax calculation. Company name, business address, billing email and, if provided, the VAT identification number are transmitted as customer data. From Stripe we receive in particular customer and subscription identifiers and the payment status; full card data is not stored in the Service, and Stripe does not receive project content. Depending on the purpose, Stripe processes data as a processor or as an independent controller, including for fraud prevention and legal obligations. Transfers to the USA based on the EU-US Data Privacy Framework or standard contractual clauses (Art. 45, 46 GDPR).
- Zernio Software SL, Carrer de Mallorca 2A, 17230 Palamós (Girona), Spain - connecting social media accounts and publishing approved posts. Post content, media, publication times and identifiers of connected accounts are transmitted; only if you connect accounts. Database and application are located in London, United Kingdom (adequacy decision, Art. 45 GDPR), media in Western Europe; some Zernio service providers process data in the USA based on the EU-US Data Privacy Framework or standard contractual clauses (Art. 45, 46 GDPR).
- Brave Software, Inc., San Francisco, USA - web search for the agent's research (Brave Search API). Search terms derived by the agent from the project (e.g. topics, industries) are transmitted, no account data. Transfers to the USA based on standard contractual clauses (Art. 46 GDPR).
- Google Search Console (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland) - only if you connect your Search Console: retrieval of search statistics for your website with your authorisation. Google's terms apply to processing in your Google account.
- Apple Inc., One Apple Park Way, Cupertino, CA 95014, USA (for users in the EEA: Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland) - Apple Push Notification Service, only if you switch on notifications in the iPhone app. The device identifier for notifications and the content of the notification (title of the task or number of waiting drafts) are transmitted. Transfers to the USA based on the EU-US Data Privacy Framework (adequacy decision, Art. 45 GDPR), under which Apple is certified.
- Bing Webmaster Tools (Microsoft) - only if you store your own Bing Webmaster key: retrieval of search statistics for your website, read-only. Microsoft's terms apply.
- Social media platforms and other services (e.g. Meta, X, TikTok, LinkedIn, YouTube, Pinterest, Reddit, your blog or your mailbox) - only if you connect them: publishing approved content, retrieving metrics, comments or messages. The transfer takes place on your behalf. Whether these providers process the data as independent controllers or as your processor depends on your contract with them and the actual processing; their terms and privacy policies apply. We are responsible for the secure transfer up to these providers.
- prohost networks GmbH (brand w3w), Wilhelm-Külz-Str. 69, 14532 Stahnsdorf, Germany - domain provider, forwards emails sent to mail@aimarage.com to our mailbox. Concerns your email address, your name and the content of your message.
- Proton AG, Route de la Galaise 32, 1228 Plan-les-Ouates, Switzerland - mailbox for mail@aimarage.com. An adequacy decision of the EU Commission exists for Switzerland (Art. 45 GDPR).
Authorities and courts receive data only where we are legally obliged to provide it. Tax and legal advisers receive data to the extent necessary; they are bound by professional secrecy.
If you connect your own programs via the interfaces (MCP, API) or share client links, retrieval by these programs or persons takes place at your instigation. For every call via MCP or API we log the time, key, person, program (client identifier), shortened IP address (IPv4 without the last block, IPv6 only the first 48 bits), the tool called, project, a summary of the arguments without contents (identifiers, lengths, for links only the host) and the size of the result. The purpose is the security of your account (detecting unknown or unexpected access); the legal basis is the performance of the contract and our legitimate interest (Art. 6(1)(b) and (f) GDPR). The log is visible to owners and admins of the workspace and to each person for their own keys. Keys are stored only as a hash; credentials for connected platforms are never handed out via the interfaces.
Own AI key: If you store your own key with an AI provider in the Service (e.g. Mistral, Scaleway, Phala, NEAR AI, OpenAI, Anthropic or OpenRouter), the data described above for AI processing is transmitted to that provider instead of our AI provider. The provider processes it on the basis of your own contract with it and is not our processor. For providers outside the EEA (e.g. USA), the lawfulness of the transfer is your responsibility. We store the key encrypted, never display it and do not write it to logs. If your own key with Mistral AI is stored, voice input is also available in the chat: the recording is then sent once to Mistral, converted into text and not stored by us.
5. Retention
- Account and project data: for the term of the contract. After the contract ends or the workspace is deleted, you can export your data for another 30 days; it is then deleted.
- Backups: one encrypted backup of the database and the files daily in Hetzner Object Storage in Falkenstein (Germany), separate from the server. We keep the backups of the last 7 days and one for each of the last 4 weeks; older ones are deleted automatically. In addition, a daily database backup is kept on our server at Hetzner for 14 days. Deleted data therefore also disappears from backups after about 5 weeks at the latest.
- Login codes: valid for 10 minutes, deleted one day after expiry. Browser sessions: until logout or expiry (30 days without renewal); iPhone app sessions: until logout, no more than 365 days. Expired sessions are deleted.
- Team invitations: valid for 7 days, deleted at the latest together with the workspace.
- Mailbox emails, contacts, logs of AI calls and consumption data in a project: until you delete them or the project, at the latest together with the workspace.
- Device identifier for push notifications: until notifications are switched off or you log out; list of notifications sent: 60 days.
- Invoice and accounting data: 7 years from the end of the relevant calendar year (§ 132 BAO); special statutory cases and pending proceedings may require longer periods.
- Proof of consent to the Terms, privacy policy and DPA: for the term of the contract and thereafter until limitation periods expire (generally 3 years).
- Server and application logs and the list of error messages: no more than 14 days, then deleted automatically. Logs are also limited in size (no more than 50 MB per service) and deleted when a new version of the Service is deployed.
- Log of MCP and API calls: 90 days, then deleted automatically. API and MCP keys: until they expire (default 90 days) or are revoked.
6. Cookies and end device
The Service uses no advertising or analytics cookies. Only the following technically necessary cookies are set:
- ma_session: keeps you logged in after login (HttpOnly, SameSite=Lax, Secure; lifetime 30 days or until logout).
- ma_project: remembers the last project you opened so you can continue there after logging in (SameSite=Lax; lifetime 30 days like the session).
- ma_chat and ma_chat_task: remember whether you have opened or closed the chat with the agent (value "open" or "closed", SameSite=Lax; lifetime 365 days).
The iPhone app stores the login key in the device's keychain and the chosen address of the Service, the last project and the language in the app settings; it uses no tracking.
These cookies are strictly necessary for the service explicitly requested by the user or only store an interface setting chosen by the user (§ 165(3) of the Austrian Telecommunications Act 2021); no consent is required. We use no analytics, tracking or advertising tools, no third-party captcha and load no fonts or scripts from third-party servers.
The Aimarage counter on our customers' websites sets no cookies and does not access storage on the visitors' end device.
7. Transfers to third countries
Some service providers (section 4) are based in the USA or may process data there. Transfers take place only if the requirements of Art. 44 et seq. GDPR are met, in particular on the basis of an adequacy decision (EU-US Data Privacy Framework, where the recipient is certified) or the European Commission's standard contractual clauses. Storage in the EU does not automatically rule out access from third countries. You can request information on the safeguards applicable to our processing and a copy of the relevant agreements via mail@aimarage.com.
8. Your rights
Subject to the statutory requirements, you have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20). Where processing is based on your consent, you can withdraw it at any time with effect for the future; this does not affect the lawfulness of processing carried out before the withdrawal.
Objection: Where processing is based on Art. 6(1)(f) GDPR, you can object on grounds relating to your particular situation (Art. 21 GDPR). We then continue to process the data concerned only if the statutory requirements for doing so are met. You can object to direct marketing at any time.
You can view, change, export and delete much of your data yourself in the Service. For all other requests, please write to mail@aimarage.com.
9. Complaints
If you believe that the processing of your data violates data protection law, you can lodge a complaint with a data protection supervisory authority, in particular in the place of your habitual residence, your place of work or the place of the alleged infringement. In Austria, this is the Österreichische Datenschutzbehörde (Austrian Data Protection Authority), Barichgasse 40-42, 1030 Vienna, dsb@dsb.gv.at, www.dsb.gv.at.
10. Obligation to provide data, no automated decision-making
The information requested at registration and for the subscription is required to conclude the contract; without it we cannot provide the Service. We do not make decisions about you based solely on automated processing that have legal or similarly significant effects within the meaning of Art. 22 GDPR. The AI features generate suggestions; you decide yourself whether to use them. You can also delegate the approval of posts to the Service in advance (AI reviewer, approval by a connected program or direct publication per channel, Terms clause 3.3); the AI reviewer (only in plans with the strong model) is switched on deliberately by owners or admins, is switched off for new workspaces and only takes effect once sending is switched on. We store in the workspace who switched it on or off and when. Such automatic publications concern your marketing content, are not decisions about individuals and can be switched off by owners and admins at any time.
11. Changes
We update this privacy policy when the Service, the service providers used or the legal situation change. The current version is available at app.aimarage.com/datenschutz.