Skip to content

Privacy Notice

1. Controller

The controller responsible for data processing on this website is:
Marcel Herczog
c/o POSTFLEX PFX-837-041
Emsdettener Straße 10
48268 Greven
Germany
Email: kontakt@aionity.app (Aiory and Aionity are offerings of Marcel Herczog, sole proprietor)

2. Collection and Storage of Personal Data

a) When visiting the website
When you access our website, the browser used on your device automatically sends information to our website server. This information is temporarily stored in a log file.

The following information is collected without any action on your part and stored until automatic deletion:

  • IP address of the requesting device
  • Date and time of access
  • Name and URL of the requested file
  • Website from which access occurs (referrer URL)
  • Browser used, operating system where applicable and name of the access provider

We process this data for the following purposes:

  • Ensuring a smooth connection to the website
  • Ensuring comfortable use of our website
  • Evaluating system security and stability
  • Other administrative purposes

Minors:
Our service is not directed at children under the age of 13. Users under the age of 18 may only use the service with the consent of a parent or legal guardian. Where processing is based on consent, such consent is only valid for users under the age of 16 if it is given or authorised by a parent or legal guardian (Art. 8 GDPR). If we become aware that we are processing data of a child under 13 without these conditions being met, we delete it.

Legal basis: Art. 6(1)(f) GDPR

3. Contact

For questions of any kind, you can contact us using the email address provided on the website or our contact form. A valid email address is required so that we know who sent the request and can respond to it. Additional information may be provided voluntarily.

Legal basis: Art. 6(1)(a) GDPR

4. Cookies and Local Storage

We use cookies on our website. Cookies are small files created automatically by your browser and stored on your device when you visit our website. Cookies do not harm your device and do not contain viruses, trojans or other malware.

Information connected with the specific device used is stored in the cookie. This does not mean that we directly become aware of your identity.

The following technically necessary storage is used:

  • Login storage in the browser — keeps you logged in while using the service
  • Language setting — remembers your selected language
  • Temporary security value during login — protects login via external providers against misuse

Local storage:
We use your browser's local storage to store login state, language settings and user settings such as layout preferences, drafts and notification status. You can delete locally stored data through browser functions or within the relevant feature.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in technical functionality)

5. Authentication via Third-Party Providers

We offer authentication for our service via the following third-party providers:

a) Google OAuth
When logging in with Google, Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) transmits the following data to us: email address, name and profile picture. We use this data exclusively to create and manage your user account.

b) Discord OAuth
When logging in with Discord, Discord Inc. (444 De Haro Street, Suite 200, San Francisco, CA 94107, USA) transmits the following data to us: email address, username, avatar and Discord user ID. We use this data exclusively to create and manage your user account and to assign subscription permissions.

c) Apple
When logging in with Apple, Apple Inc. (One Apple Park Way, Cupertino, CA 95014, USA) transmits the following data to us: Apple ID, email address (on request a forwarding address generated by Apple) and, if you agree, your name. We use this data exclusively to create and manage your user account.

Registration with an email address
Alternatively, you can create an account with an email address and password. We store your email address, your password only in protected form (not in plain text) and the time at which your email address was confirmed, which we check with a confirmation email.

During the OAuth authorization process, you decide whether to continue login via the relevant third-party provider. The data then transmitted to us is processed to create, manage and secure your user account.

Legal basis: Art. 6(1)(b) GDPR and Art. 6(1)(f) GDPR

6. Payment Processing

We use Stripe Inc. (354 Oyster Point Blvd, South San Francisco, CA 94080, USA) to process payments. When you subscribe to a paid plan, your payment data, such as card number and expiry date, is transmitted directly to Stripe and processed there. We do not store complete payment data ourselves.

Stripe processes your data, among other places, in the USA. Data transfer is based on the EU Standard Contractual Clauses (SCCs). Further information is available in Stripe's privacy policy: stripe.com/privacy

Subscriptions via the apps: If you subscribe in the iOS app, Apple (App Store) processes the payment; in the Android app, Google Play does (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). Apple or Google then processes your payment data under their own privacy terms; we only receive and store the details we need for the subscription (plan, term, status, price and a transaction or purchase ID).

Legal basis: Art. 6(1)(b) GDPR

7. Integrated Third-Party Services

a) Google Fonts
This website uses locally hosted Google Fonts files for consistent font display. The font files are loaded from our own server; no connection to Google servers is established when loading the fonts.

b) Favicons and Website Icons
To display website icons, for example next to sources of search results, favicons are loaded through the provider's own proxy. The user's browser does not establish a direct connection to external favicon services; our server may process the respective source domain to retrieve the icon.

c) hCaptcha
We use hCaptcha to protect our contact form against automated submissions. Technical connection data, IP address, browser information, interaction data with the captcha and the result of the human verification may be transmitted to the provider.

d) Media, Map and Content Services
When corresponding content is displayed or opened, YouTube videos and OpenStreetMap maps may be loaded. Discord and Google profile pictures are delivered through the provider's own proxy endpoints where technically possible, so the browser does not need to connect directly to the original avatar providers.

e) CDN and Icon Services
Country flags, symbol graphics and individual fallback icons are delivered through the provider's own proxy endpoints or locally hosted files. Where our server queries external icon sources such as flagcdn.com or jsDelivr, this happens server-side and not directly through the user's browser.

f) OpenAI and AI Services
For the AI chat, document analysis, AI image generation, translations, automatic titles and speech transcriptions, we use services from OpenAI as a processor within the meaning of Art. 28 GDPR. Your entered prompts, uploaded files and documents, audio files for transcription, chat excerpts, selected entries from your memory (see section 9) and technical context data may be transmitted to OpenAI where this is required to provide the respective function. Processing may also take place in the USA (see section 10). We have a data processing agreement with OpenAI under Art. 28 GDPR that includes standard contractual clauses for transfers to third countries. OpenAI may retain data submitted through its programming interface (API) for up to 30 days to detect abuse and does not use it to train its models.

f-2) Voice conversation with Aiory
When you start the free voice conversation, your device opens a direct connection (WebRTC) to OpenAI’s Realtime interface. In this case your voice and the reply voice do not travel through our servers but directly between your device and OpenAI; our server only issues a short-lived access key and receives information about duration and volume of use in order to bill your allowance. The transcript of the conversation is stored in your chat history. The voice conversation only starts on your explicit action.

f-3) Own language model
We run part of the AI tasks on a language model operated by us (a freely available open-weights model) on rented servers within the European Union, for example short replies such as greetings, weather reports, titles, summaries, spelling correction, the preparation of search queries and the checking of product offers. The data does not leave our infrastructure in this case. The model does not make decisions about people.

g) Web Search and Weather Services
For the live web search and everyday widgets (for example weather, product search, travel), request content such as search terms or place names may be transmitted server-side to external search or weather services. These requests are made through our servers; the user's browser does not establish a direct connection to these services.

h) Hosting, Servers and Backups
Aiory is operated on rented servers in data centres within the European Union. The providers involved are netcup GmbH (Karlsruhe; servers), centron GmbH (Hallstadt; server on which our own language model runs) and Hetzner Online GmbH (Gunzenhausen; encrypted backups, Falkenstein data centre). We have a data processing agreement under Art. 28 GDPR with all three providers. Deleted content is removed from our live systems immediately; it disappears from the encrypted backups after at most twelve months.

i) Partner offers in product search
In product search we show offers from merchants that we obtain through partner networks (currently Yadore and AWIN). These offers are marked “Anzeige” (advertisement). For the search, our servers transmit search terms or product identifiers (for example EAN) to the partner; we do not transmit your account data. If you click an offer, you are redirected to the merchant via the partner. The partner and the merchant may then process your IP address and browser details and set cookies in order to attribute the click to a commission; if you buy, we may receive a commission. The partner and the merchant are themselves responsible for their processing.

Legal basis: Art. 6(1)(b) GDPR (provision of booked or requested functions) and Art. 6(1)(f) GDPR (technical operation, security, abuse prevention and improvement of the functions); Art. 28 GDPR (processing on behalf)

8. Real-Time Data Connections (WebSocket)

Our service uses WebSocket connections to our own servers to provide chat responses, status messages, notifications and other Aiory functions in real time. For logged-in users, technically necessary session, user or permission information may be processed so that content can be assigned correctly and delivered securely.

Legal basis: Art. 6(1)(b) GDPR, Art. 6(1)(f) GDPR

9. Aiory Chat, AI Functions, Location and Notifications

Aiory chat:
When you use Aiory, we process your inputs, uploaded or linked content, chat history, generated answers, images and documents, usage and cost information and technical session data. This processing is used to provide answers, history, export functions and subscription limits.

E-mails sent from your own mailbox:
In the settings you can connect your own e-mail mailbox (e.g. iCloud, Gmail, GMX, web.de or another one via IMAP/SMTP). When you then ask Aiory to send an e-mail, Aiory first creates only a draft that you see in the chat; it is sent solely after your explicit confirmation (tapping “Send” or agreeing in a voice conversation) and always from your own address through your provider’s server – never from an Aiory address. Aiory stores a copy in the “Sent” folder of your mailbox. We store the access data (address, servers, app password) encrypted on our servers and use it only for this sending; you can disconnect at any time, after which it is deleted. In addition we store recipients, subject, text, time and delivery status of the e-mails you confirmed in your account (Settings › Mailboxes › “Sent via Aiory”); the text is deleted after 90 days, unconfirmed drafts expire after 24 hours at the latest. Aiory does not read e-mails you receive. To prevent abuse, the number of e-mails per account is limited.

Gmail connection via Google:
Instead of an app password you can also connect a Gmail mailbox by signing in with Google. Aiory then receives only the permission to “send e-mail on your behalf” (Google scope gmail.send) plus your e-mail address and name; Aiory gets no read access to your mailbox. We store the access tokens issued by Google encrypted and use them only to send the e-mails you have confirmed through the Gmail API; Gmail itself files them in your “Sent” folder. If you disconnect the mailbox in Aiory, we delete the tokens and revoke the access at Google; you can also revoke it at any time under myaccount.google.com › Security › Third-party apps. Aiory's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. This data is not shared with third parties and is not used for advertising or to train AI models.

Our access to your chats:
We do not read your chats routinely. We access them only in individual cases and only where necessary: on your report or request (support), for troubleshooting, to investigate security incidents or abuse, and where required by law (Art. 6(1)(b), (c) and (f) GDPR). Access is limited to authorised persons and is logged.

AI processing:
For answer generation, document analysis, image generation, summarisation, translation, automatic chat titles and speech transcription, inputs, uploaded files, audio data and required context data may be transmitted through our servers to OpenAI as a processor; in the free voice conversation this happens directly between your device and OpenAI (see section 7 f-2). Before any data is sent to OpenAI for the first time, we obtain your consent inside the application. Please do not enter particularly sensitive personal data in Aiory unless it is required for your request.

Memory:
Aiory can remember short single details about you beyond individual chats so that answers fit you better (for example “Is vegetarian.” or “Daughter is called Lea.”). Only such single details are stored, no conversation log: details you explicitly ask Aiory to remember (for example “Remember that …”), details you enter yourself under Account › Memory and – as long as the “Learn from chats” switch is on – details Aiory learns from your own chat messages. These may include details about people or pets in your life that you mention yourself. Aiory learns only from the text you write yourself, and every learned detail must be backed by a literal quote from one of your messages. Nothing is learned from pasted texts, from the transcript of the free voice conversation, from Aiory’s answers or from attachments, files, e-mails and web pages; Aiory does not follow requests to remember something that appear in pasted texts, attachments, files, e-mails or web pages. For each entry we also store whom it is about (you or, for example, “daughter”), its area, its origin (from you or learned), whether it is sensitive (see below) or should always be taken into account, the time, the chat it comes from, when and how often it was used, and an expiry date where one was mentioned. So that Aiory also finds an entry for questions that do not name it literally, Aiory has two to three short example questions generated, after an entry that is not sensitive is stored or changed, in which the entry helps (for example “What shall I cook tonight?” for “Is vegetarian.”). For the text and the example questions we calculate numerical representations (embeddings) on our own servers, which Aiory uses to find the entries that fit a question. We store text, example questions and numerical representations encrypted and bound to your account. Each account can hold at most 300 entries.

Memory – sensitive details:
Aiory does not learn details about health, religious or philosophical beliefs, political opinions, sex life or sexual orientation, ethnic origin, trade union membership, or genetic or biometric data (special categories under Art. 9 GDPR) on its own: learned details are checked automatically before they are stored and discarded if they fall into one of these categories. Aiory only takes up such a detail if you explicitly ask for it or enter it yourself (including by changing an entry accordingly). It is then only held as a proposal that Aiory does not use, and it is only added to your memory when you tap “Remember” on the “Sensitive detail” in the chat or under Account › Memory. With this tap you explicitly consent to the storage and use of exactly this one detail, including its transfer to OpenAI in the cases described below (above all when it fits one of your questions). Because persons under 16 cannot give such consent on their own (cf. Art. 8 GDPR), Aiory asks once, before your first consent, whether you are at least 16 years old and stores only the time of your confirmation, not a date of birth; if you answer no, the proposal is deleted at once. Aiory checks automatically whether a detail is sensitive; if the check cannot be carried out, Aiory treats the detail as sensitive and asks. Proposals you do not confirm are deleted after 24 hours, or at once when you tap “Don't remember” or “Discard”. Sensitive details never go along with every question, only when they fit a question particularly closely; Aiory does not generate example questions for them. You can withdraw your consent at any time by deleting the detail; this does not affect the lawfulness of the processing carried out until then.

Memory – interest suggestions:
As long as the “Learn from chats” switch is on, Aiory also recognises while learning (in the same call of the language model, see below) which topics you ask about – for example a team, a sport, an artist or a hobby. No detail is stored from this at first: per topic, Aiory only counts how often and on which days you asked about it and stores the name of the topic for this, encrypted and bound to your account; it does not store the questions themselves for this. Aiory does not count topics about health, religious or philosophical beliefs, politics, sex life or sexual orientation and ethnic origin: they are checked automatically before they are stored and discarded, and if the check cannot be carried out, the topic is not counted either. If you ask about the same topic at least four times on at least two different days within 30 days and it is not yet in your memory, Aiory shows a suggestion under Account › Memory (for example “You often ask about THW Kiel. Remember it?”). Only when you tap “Remember” there does it become an entry (for example “Is interested in THW Kiel.”), which is treated like any other learned entry; without your tap no entry is stored, and suggestions left unanswered are deleted after 14 days. Counters to which no question is added for 30 days are deleted. So that the same topic is not suggested again, Aiory keeps the name (encrypted) of topics for which you tapped “Remember” or “No”, for which a suggestion has already been made or which are already in your memory, for 90 days; it is deleted afterwards. If you switch off “Learn from chats” or pause the memory with the “Use memory” switch, we delete the running counters and open interest suggestions at once; “Forget everything” and the deletion of your account also delete the remembered decisions.

Memory – what is transmitted to OpenAI:
For each question, Aiory selects on our servers only the entries that fit this question and transmits them together with the question to OpenAI as a processor (see section 7 f and section 10). Entries you have set to “Always take into account” go along with every question. If you ask Aiory what it knows about you, or ask it in the chat to forget something, the entries needed for this are transmitted (at most 60 when listing). For learning, we transmit your new own chat messages – each with the beginning of Aiory’s preceding answer as context – together with the list of your already stored entries (without sensitive details) to an OpenAI language model, which turns them into new single details and recognises what is already known; in the same call it also determines the topics of your questions for the interest suggestions and, for this, additionally receives the names of the topics already counted for you. For the example questions (see above), we transmit entries that are not sensitive to an OpenAI language model after they are stored or changed. If your question refers to something of your own that it does not name itself (for example “When does my club play?”), Aiory puts only the name or place needed for the web search from the matching entry into the search query; this search query goes to the web search and weather services like any other (section 7 g) and is stored with the chat like other search queries. Sensitive details never go into a search query. Beyond that, we do not pass entries from your memory on to any other recipients.

Memory – your settings and storage period:
Under Account › Memory you see your valid entries and open proposals. There you can change or delete any entry, add entries, export your entries and open proposals as a JSON file, pause the memory (“Use memory” switch: Aiory then uses none of it and remembers nothing new, stored entries are kept), switch off learning from chats (“Learn from chats” switch) or delete all entries with “Forget everything”. In the chat you can ask Aiory to forget something at any time. If a new message contradicts a detail you stated or entered yourself, Aiory does not change it on its own but places a proposal to change or remove it under Account › Memory, which you accept or discard; proposals not accepted are deleted after seven days. If you have switched off reading completely under “Aiory and your files” (“Do not read at all”), the memory is paused as well. We store the entries until you delete them or your account is deleted; with the account we delete all entries, proposals, counters for interest suggestions and settings of the memory. Entries deleted individually can be restored for 15 minutes and are then deleted for good; “Forget everything” deletes immediately and without restore. Deleting a chat does not delete the details Aiory remembered from it – you delete those under Account › Memory. Aiory no longer uses or shows entries with an expiry date (for example about a planned trip) after that date and deletes them automatically afterwards. Deleted entries may remain in our encrypted backups for up to twelve months until the respective backup is deleted automatically.
The legal basis for the memory is Art. 6(1)(b) GDPR (provision of the function; learning from chats can be switched off with its own switch), and for sensitive details your explicit consent per detail under Art. 9(2)(a) GDPR.

Cloud storage and online office:
Files you store in the cloud storage or open in the online office editor are stored and processed on our servers to provide storage, editing, document creation and export.

Appointments, reminders and AI automations:
For appointments, reminders and AI automations, we store the content, times and recurrence rules you set up in order to provide and execute the respective function.

Location and maps:
Location data is processed only if you grant the relevant browser permission or actively use a location-based feature (for example weather). The data is used to display maps, local information and location-based Aiory responses. For geocoding, reverse lookup or IP-based location proximity, services such as OpenStreetMap/Nominatim or ipwho.is may be queried.

Notifications:
For in-app notifications, we store notification text, type, time and read or hidden status per user account. Short-lived notifications and related status data are regularly cleaned up automatically; technically necessary states may also be stored locally in the browser. If you allow push notifications, they are delivered through push services: in the apps through Firebase Cloud Messaging (Google, and on iOS devices additionally Apple), in the browser through the push service of your browser provider. For this we store a device token or a browser subscription, and the text of the message (for example an appointment reminder) passes through these services. You can switch push notifications off at any time in your device or browser settings.

Legal basis: Art. 6(1)(b) GDPR and Art. 6(1)(f) GDPR; for sensitive details in the memory Art. 9(2)(a) GDPR (explicit consent)

10. Data Transfers to Third Countries

Use of the services named above, in particular Google, Apple, Discord, Stripe, hCaptcha, YouTube, OpenAI, OpenStreetMap, ipwho.is, jsDelivr and flagcdn, as well as integrated search and weather services, may result in personal data being transferred to the USA or other third countries. Transfers are based on:

  • EU-US Data Privacy Framework, where the recipient is certified
  • EU Standard Contractual Clauses pursuant to Art. 46(2)(c) GDPR

Legal basis: Art. 49(1)(a) GDPR, Art. 46(2)(c) GDPR

11. Retention Periods

We store your personal data only for as long as necessary for the respective processing purposes or as required by statutory retention obligations:

  • User account data: until the account is deleted or until a justified deletion request, unless statutory retention obligations apply
  • Payment data (Stripe): according to tax and commercial retention obligations, up to 10 years
  • Server log files: maximum 14 days
  • Aiory chats, uploaded files and cloud content: as long as they are needed for history, storage, support or subscription features, or until deleted by you or upon justified request; deleted chats are removed from our live systems immediately and disappear from the encrypted backups after at most twelve months
  • Appointments, reminders and AI automations: until deleted by you or until the account is deleted
  • Memory (Account › Memory): until deleted by you or until the account is deleted; entries deleted individually after 15 minutes (restorable until then), unconfirmed sensitive proposals after 24 hours, change proposals not accepted after seven days, counters for interest suggestions 30 days after the last question on the topic, interest suggestions left unanswered after 14 days, remembered decisions on interest suggestions after 90 days; in backups up to twelve months
  • Notifications: short-lived in-app notifications and related status data are regularly cleaned up automatically
  • Contact requests: until the request is completed, then deletion unless statutory retention duties apply

Legal basis: Art. 17(3) GDPR, Section 147 AO, Section 257 HGB

12. Data Subject Rights

You have the right to:

  • request information about your personal data processed by us pursuant to Art. 15 GDPR
  • request rectification of inaccurate or completion of incomplete personal data pursuant to Art. 16 GDPR
  • request deletion of personal data stored by us pursuant to Art. 17 GDPR
  • request restriction of processing pursuant to Art. 18 GDPR
  • receive your personal data in a structured, commonly used and machine-readable format pursuant to Art. 20 GDPR
  • withdraw consent at any time pursuant to Art. 7(3) GDPR
  • lodge a complaint with a supervisory authority pursuant to Art. 77 GDPR

Decision-making based solely on automated processing, including profiling, within the meaning of Art. 22 GDPR that produces legal effects concerning you or similarly significantly affects you does not take place.

13. Right to Object

Where your personal data is processed on the basis of legitimate interests pursuant to Art. 6(1)(f) GDPR, you have the right to object to processing pursuant to Art. 21 GDPR where grounds arise from your particular situation.

To exercise your right to object, an email to kontakt@aionity.app is sufficient.

14. Data Security

During website visits, we use the widely used SSL procedure together with the highest encryption level supported by your browser.

We also use appropriate technical and organizational security measures to protect your data against accidental or intentional manipulation, partial or complete loss, destruction or unauthorized third-party access.

15. Current Version and Changes

This privacy notice is currently valid and dated 12 October 2026.

Due to further development of our service and offerings, or due to changed legal or regulatory requirements, it may become necessary to amend this privacy notice. The current privacy notice can be accessed and printed at any time on the website at www.aiory.app/privacy.