Privacy policy

Last updated: October 21, 2026

1. Who is responsible for your data

The controller within the meaning of the General Data Protection Regulation (GDPR) is:

No data protection officer has been appointed. You can send privacy requests directly to info@animodo.app.

2. The key points first

• To create an account, you only need an email address and a password. You confirm the email address with a link we send you. No invite code is needed.
• We don’t ask for your real name, your date of birth or your location. You can choose any username; it doesn’t have to be your real name. We store your device’s time zone so that your day starts at the right time (see 3.3).
• What you post or share is only seen by your friends, unless you explicitly choose “Everyone” when posting. Then all signed-in users see the post. All signed-in users can find your username and your profile picture so that they can send you a friend request. Your friends also see how many habits you have and when you last checked something off (see 3.3).
• Chats are not end-to-end encrypted. Users other than the recipient cannot see them. We can technically read them and review reported messages (see 3.13 and 3.19).
• We don’t send advertising or newsletters. We only use your email address to sign you in, for necessary messages about your account, and for the link to reset your password if you request it.
• We don’t use analytics or advertising services. No Google Analytics, no Facebook Pixel, no crash reporting, no advertising IDs, no tracking across apps or websites.
• Animodo is free to use. For the optional Animodo Plus subscription, our reseller Paddle handles the payment (see 3.16). You enter your payment details, such as your card number, only with Paddle; we don’t receive them.
• We don’t sell data and don’t pass it on for advertising purposes.
• Your data is stored on servers in Germany. Exceptions: If you turn on push notifications, delivery runs in encrypted form through your browser’s push service (see 3.12). If you join the waitlist, your email address is stored with the email service Brevo in France (see 3.15); we also send our emails to you through Brevo (see 3.13, 3.17 and 3.18). If you look at the Plus prices or get Animodo Plus, Paddle processes data internationally (see 3.16). Brevo may also use subprocessors outside the EU (see section 4).

3. What data we process

3.1 Access

To create an account, you need an email address and a password. If you have an invite code from another user, you can enter it at that point (see 3.10). Anonymous use without an account is not possible.

After you sign up, we send you an email with a confirmation link so we know the address is yours. The link is valid for 24 hours; you can request a new one in the app. Until you confirm, you can use Animodo, but you won’t receive emails from us, can’t subscribe and can’t address content to people you aren’t friends with. If you don’t confirm the address within 7 days, we delete the account with all its data.

3.2 When you create an account

Legal basis: Art. 6(1)(b) GDPR (performance of the user agreement, see Terms of use).

Obligation to provide: Your email address and password are required for the user agreement. There is no legal obligation to provide them, but without them we can’t create an account for you and you can’t use Animodo.

Use of your email address: We do not show it to other users or use it for advertising. We use it for sign-in, password resets, support, moderation and contract messages, particularly cancellations. Brevo receives the address and the relevant message content to send emails. Paddle also receives your email address when you purchase Plus (see 3.13 and 3.15 to 3.18).

Legal basis for these messages: Art. 6(1)(b) GDPR, and for decisions on reported content additionally Art. 6(1)(c) GDPR in conjunction with Articles 16 and 17 of the Digital Services Act.

3.3 Your content in the app

Time zone: When you create your account, we take the time zone your device reports. It roughly indicates which region of the world you are in, but not exactly where. If your device’s time zone later differs, the app asks you whether it should take over the new time zone; we don’t change it without your confirmation. Other users don’t see your time zone.

Language: When you create your account, we take the language you selected in the app, otherwise that of your browser. We send you emails and push notifications in this language. You can change it in Settings.

At first, this data is visible only to you. Your friends additionally see how many habits you have and on which day you last checked something off (“last active”). All your habits count for this, including those you haven’t shared; your friends don’t see their names or history. Others only see anything more if you post it (3.8) or share it (3.9).

Legal basis: Art. 6(1)(b) GDPR, also for showing this to your friends as part of the friends feature.

3.4 Special categories of personal data

Free text and photos may contain information about health, religion, political views or other specially protected matters. This can affect habits, photos, posts, comments, chats and descriptions in reports and cancellations. Even storing such information is processing under Art. 9 GDPR.

Animodo does not specifically request this information or analyze it to assess your health or other sensitive matters. The features are not intended to collect such data. Please use neutral names and avoid such details and photos, including about other people. In particular, we do not need diagnoses or medical records to process a cancellation.

Processing special categories requires an exception under Art. 9(2) GDPR in addition to a legal basis under Art. 6 GDPR. Entering, posting or sharing information, or agreeing to the terms of use, does not replace explicit consent to this processing. If you entered such information by mistake, you can delete the content or ask for help at info@animodo.app. We cannot fully retrieve copies already sent to other people.

3.5 The ideas board (“Ideas & bugs”)

With the “Ideas & bugs” button, you can send us suggestions and bug reports, give other entries a thumbs-up and reply to them.

Other users see the text of your entry, the time, the page of the app and how many thumbs-up it has, and for replies the text and the time. They don’t see your username, your email address or your ID number; no name is displayed, but your text may still identify you. Internally, entries, replies and thumbs-up are linked to your account so that we can delete them and nobody votes twice.

We store the text, the time, the page of the app you were on, your replies and who gave which entry a thumbs-up.

Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is improving the app in exchange with its users.

Retention period: Your own entries, until you delete them or your account. Replies and thumbs-up on other people’s entries remain until the entry in question is deleted, even if you delete your account; nobody is shown who they came from.

3.6 Profile picture

You can upload a profile picture voluntarily. It is stored on our server. Signed-in users see it together with your username, for example in the friend search, in friend suggestions, in friend requests, next to your posts and comments and on shared habits. If you share an invite link, it is also visible on the invitation page, there even without signing in for anyone who has the link. So don’t upload a picture you don’t want to show. You can remove your profile picture at any time.

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

3.7 Friendships, search and suggestions

In Animodo, you can become friends with other users. For this, we process:

• Friendships and requests: who sent whom a request, whether it is open, accepted or declined, and since when. If you accept an invitation, you automatically become friends (see 3.10). You can withdraw requests and end friendships at any time.
• Search: Signed-in users can search for usernames. The results show the username and profile picture, but never your email address.
• Suggestions: We suggest people with whom you have friends in common, and name up to two of these mutual friends and how many there are. If there are too few such people, we add other users to the list, if necessary also people whose request was declined. The selection changes regularly. In the same way, you can be suggested to others.

As soon as you have set a username, all other users can find you: you can appear in their search and in their friend suggestions. There is currently no setting that lets you hide yourself once you have set a username.

Legal basis: Art. 6(1)(b) GDPR (the friends features are part of the user agreement).

3.8 The feed: posts, photos, hearts and comments

After checking off a date, you can voluntarily post in the feed, either a win or a miss. A post contains your username, the name of the habit, your streak, the time of day and schedule of the habit, and the time of posting. You can optionally attach a photo.

Who sees your post: When posting, you choose the visibility. The default is “Friends”: then only you and the people you are friends with see the post. If you choose “Everyone”, the post is a public post: all signed-in users of Animodo can see it, including those you are not friends with. It then appears for everyone who has set their feed to “Everyone”, together with your username and your profile picture. Posts can’t be accessed outside the app, for example by search engines or without signing in. You can change the visibility of your own post at any time; people who are no longer allowed to see it no longer see it from then on.

Feed selection: Whether your feed shows only posts from you and your friends or all public posts as well is stored in your account so that the selection applies on all your devices.

Photos: The app shrinks the photo before uploading and saves it as a new image file. In the process, embedded metadata such as the location or camera model is lost. If you upload a photo but don’t post it, we delete it after about 24 hours.

Hearts and comments: Everyone who is allowed to see a post can give it a heart, comment on it and report it: for friends posts, the author’s friends; for public posts, all signed-in users. We store who gave a heart, and the text, username and time of a comment. A comment is visible to everyone who sees the post. This can include people you are not friends with yourself, namely other friends of the person who posted, and for public posts all signed-in users. If the author later switches a public post to “Friends”, hearts and comments remain stored but are only visible to the people who are still allowed to see the post. The author of the post learns through a notification who gave a heart or commented.

Legal basis: Art. 6(1)(a) GDPR for voluntarily posting and attaching a photo with the chosen visibility; Art. 6(1)(b) GDPR for hearts and comments. Section 3.4 also applies to special categories. You can withdraw consent by deleting the post; you can remove hearts and delete your own comments.

3.9 Sharing habits with friends

You can share a habit with specific friends. Friends can also ask you to do so, for example through one of your posts; you decide yourself whether you share.

Anyone allowed to see one of your habits sees, permanently and continuously updated: the name, the icon (emoji or photo), the schedule and the time of day, your current streak, your record, your success rate, since when you have been sharing, and for each individual date, whether you completed it, didn’t do it or had paused.

Legal basis: Art. 6(1)(a) GDPR (consent by sharing). Section 3.4 also applies to special categories. You can withdraw consent at any time by stopping sharing. Sharing also ends if you delete the habit or the friendship ends.

3.10 Invitations

You can invite other people to Animodo with an invite link. For this, we store a randomly generated invite code, the link between you and the invited person and, if you enter one, a short note about the invitation.

Anyone who opens your invite link sees your username and your profile picture (if you have one), so that it is clear who the invitation is from. This is visible even without signing in. So only share the link with people you really want to invite.

If the invited person creates an account, you automatically become friends. As soon as they have set their username, you get a notification.

Legal basis: Art. 6(1)(b) GDPR (inviting and becoming friends are features of the app).

3.11 Notifications in the app

Under “Notifications” (bell), in the “Notifications” tab, we let you know when someone sends you a friend request or a friendship has been confirmed, someone has accepted your invitation, a friend has posted something, someone shares a habit with you, asks you to share one or agrees to your request, or when someone has given your post or comment a heart, commented on your post or replied to your comment. A notification contains the type of event, the username of the person who triggered it, where applicable the name of the habit, the time, and whether you have read it. While the app is open, the feed, notifications and chats update live through a persistent connection to our server; no additional data is collected in the process.

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

3.12 Push notifications

If you turn this on in the notification settings or through the prompt in the app, and allow it in your browser, we also send you the notifications from 3.11 as push notifications to your device when the app is closed. The text of a push notification contains the username of the person who triggered it and, where applicable, the name of the habit. For a new message in a chat (see 3.19), it contains the sender’s username and the beginning of the message (up to 120 characters).

Selection: In the notification settings, you choose for which types of notifications and for which chats (from friends, from others) you get push notifications. We store this selection in your account. Types you turn off still appear under “Notifications”, just without a push notification.

Reminders: You can turn on a reminder for individual habits. If a date is due and still open, we send you a push notification with the name of the habit, such as “Today: Reading”. So that you are reminded of a date only once, we store for which habit and which date we sent a reminder, and delete this record after 30 days. Reminders require push notifications to be turned on.

For this, we store your device’s push address and the associated keys in your account. Technically, delivery runs through the push service specified by your browser’s vendor, for example Google (Chrome, Android), Apple (Safari, iOS), Mozilla (Firefox) or Microsoft (Edge). We can’t choose the provider.

• The content is encrypted between our server and your device. The intermediary push service cannot read the text or the names or habits it contains. Our server creates the message and knows its content.
• The push service receives your device’s push address, the time, the size of the message and the IP address of our server. It also knows your device’s IP address from the connection your browser itself maintains to receive push notifications; this connection exists independently of Animodo.
• Depending on the push service, connection data may be processed in the USA or other third countries. An adequacy decision, such as the EU-US Data Privacy Framework, supports a transfer only where the specific recipient and service are covered. Otherwise, appropriate safeguards under Art. 46 GDPR are required. Browser permission alone is not explicit consent to a transfer without safeguards under Art. 49 GDPR. You can ask us for information about the specific service and applicable safeguards.

Legal basis: Art. 6(1)(a) GDPR (consent). You can withdraw it at any time in the notification settings or in your browser. If you turn off push notifications, we delete the push address; if it has expired at the push service, we remove it as well. You turn off reminders for a habit on the habit itself.

3.13 Reports of content

If you report content to us (see Terms of use, section 7), we process the report in order to review it and to inform you and the person concerned of our decision.

• Report in the app (posts, comments and messages in chats): We store your account’s internal ID number, your email address, the reason you selected, your description for “Other reason” and the time. We then hide reported posts and comments for you.
• Report by email: your message with your details, such as your name and email address.
• Copy of the reported content: So that we can review and document a report even if the content has since been deleted, we keep a record of it: the username and ID number of the person who wrote it, the name of the habit, for a comment or message its text, and for a post with a photo a copy of the photo. This also applies to you if someone reports one of your contents.

We confirm receipt of your report by email; our support also receives the report by email. Neither email contains the reported content (text, photo, name of the habit) or the person who wrote it, only ID numbers and your reason and description; our support looks at the content in our own database. To send these emails, we use Brevo (see 3.15) as a processor. We only disclose your identity to the person concerned if this is essential for the review or we are legally required to do so.

Legal basis: Art. 6(1)(c) GDPR in conjunction with Articles 16 and 17 of the Digital Services Act; for the copy of the reported content additionally Art. 6(1)(f) GDPR (our legitimate interest in reviewing reports carefully and being able to document decisions). Retention period: We automatically delete reports, including the copy, 183 days after receipt, even if the reported content or an account involved is deleted earlier. If we need records longer to defend against legal claims, we keep them separately.

3.14 Server logs

When you use the app, our server automatically records:

• IP address
• date and time of access
• address requested
• amount of data transferred and status code
• browser type and operating system

These logs serve secure operation, troubleshooting and defense against attacks. They are automatically deleted after 14 days and are not combined with other data.

To protect against overload and attacks, we also briefly count requests per IP address in the server’s memory, for example for sign-in, sign-up and cancellation. These counters expire after two hours at most.

Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is technically flawless and secure operation.

3.15 Waitlist for the launch of Animodo

You can voluntarily join the waitlist. For this, we process your email address in order to notify you by email when Animodo launches. The legal basis is your consent (Art. 6(1)(a) GDPR). This does not create an app account.

For the waitlist, we use the email service Brevo (Sendinblue SAS, 106 boulevard Haussmann, 75008 Paris, France) as a processor under Art. 28 GDPR. We don’t store your email address in our own database but transfer it directly to Brevo. Brevo sends you a confirmation email (double opt-in). Only when you click the link in it are you added to the waitlist. Brevo stores when you signed up and confirmed so that we can prove your consent. When you click the confirmation link, you open an address at Brevo; for technical reasons, Brevo processes your IP address in the process.

You can withdraw your consent at any time with effect for the future, by email to info@animodo.app. We delete your entry after you withdraw consent or after the launch notification has been sent.

Signing up doesn’t require cookies. To protect against automated sign-ups, we temporarily limit the number of requests per IP address. We don’t transfer your IP address to Brevo in the process; section 3.14 applies to server logs.

3.16 Animodo Plus and payment processing by Paddle

For Animodo Plus, we use Paddle as reseller and seller (merchant of record). The entity responsible for your purchase is identified on your receipt: Paddle.com Market Limited, 30 Old Bailey, London EC4M 7AU, United Kingdom, outside the USA and Canada; Paddle.com Inc. in the USA; and Paddle.com (Canada) Ltd. in Canada. Paddle processes data for purchases, payments, invoicing, taxes, refunds and fraud prevention as a separate controller. Details and other Paddle entities involved are listed in the Paddle privacy policy.

• Price display: When you open the Animodo Plus page in the app, your browser loads Paddle’s payment library (Paddle.js) from Paddle’s servers and requests the prices for your country there. For technical reasons, Paddle receives your IP address and information about your browser in the process. Loading is triggered only on the Plus page; afterwards, the library may remain loaded when you change pages until you close or reload the app.
• Purchase: When you tap “Get Plus”, we send Paddle your email address and your account’s internal ID number so that Paddle can assign the purchase to your account. In Paddle’s checkout window, you enter your payment details and your country and, where applicable, your postal code; only Paddle receives this information.
• What we store: From Paddle, we receive and store in your account an identifier of your subscription, its status, the start date, the billing interval, the time of the last change, the end of the current billing period and, if you have canceled, the end date. We don’t store payment details, invoices or addresses.
• Plus badge: While your subscription is active, we show a Plus badge after your username. It is seen by everyone who sees your posts or comments, and by your friends in the friends list and in your profile.
• Manage subscription: With “Manage subscription”, we forward you to Paddle’s customer portal. For this, we request a personal access link to your subscription from Paddle.
• Emails from Paddle: As the seller, Paddle sends you the necessary emails, such as the receipt with invoice and notices about renewal, failed payment and cancellation.

Legal basis: Art. 6(1)(b) GDPR for entering into and performing the subscription and for the price display you request as a pre-contractual measure. International processing: Paddle also processes data outside the United Kingdom, for example in the USA and Canada, and uses other service providers. Its privacy policy describes adequacy decisions and, for transfers not covered by them, standard contractual clauses and additional safeguards. Information and copies of the safeguards referenced there can be requested at privacy@paddle.com.

Our retention period: Subscription and cancellation details (3.17) are kept for as long as your account exists. After account deletion, they are deleted once the subscription has ended and three years have passed since Paddle’s last reported update to the ended subscription. This allows us to clarify and document payment, cancellation and refunds and to defend claims (Art. 6(1)(f) GDPR). Records needed for a specific legal dispute or statutory retention obligations may be kept separately for longer. Paddle retains its own invoice and payment data under the rules applicable to Paddle.

3.17 Cancellations

If you cancel via Cancel contracts here, we store your declaration with your subscription: cancellation number, type of cancellation, for an extraordinary cancellation the reason, the time of receipt, the end of the contract, your email address and the processing status. If you delete your account, we cancel an active subscription the same way. You immediately receive a confirmation of receipt by email; for extraordinary cancellations (for the refund) and for cancellations we can’t carry out automatically, we also notify our support. To send these emails, we use the email service Brevo (see 3.15) as a processor. Cancellation reasons are not visible to other users. We process them to handle the cancellation; if they are included in an email, Brevo also processes them for delivery.

Legal basis: Art. 6(1)(c) GDPR in conjunction with § 312k BGB (German Civil Code) for the confirmation, Art. 6(1)(b) GDPR for handling the contract and Art. 6(1)(f) GDPR for keeping it as evidence. Retention period: the same as the subscription details (3.16), so after an account deletion up to three years after the last status update to the ended subscription (3.16). If you withdraw a cancellation, we delete the details of that cancellation.

3.18 Resetting your password

If you’ve forgotten your password, you can request a reset link via “Forgot password?”. If there is an account for the email address you entered, we send the link there. To send it, we use Brevo (see 3.15) as a processor.

• The link contains a random code. We only store an irreversible hash of it and the expiry time. The link is valid for one hour and only once; a new link invalidates the old one.
• To limit misuse, we store the times of your most recent requests (at most three per hour) and limit the number of requests per IP address. For this, we keep the IP address only in memory, for no more than two hours after the last request.

Legal basis: Art. 6(1)(b) GDPR (access to your account), and for limiting requests Art. 6(1)(f) GDPR (protection against misuse). Retention period: the hash and expiry time until you have set a new password or a new link is requested; the times of requests until they are older than one hour at a later request. At the latest, we delete everything together with your account.

3.19 Chats

You can send messages to other signed-in users, including those you are not friends with. Under “Notifications” → Settings, you choose whether everyone can message you or only your friends; the default is “Everyone”. You can block a person; then neither of you can send the other any more messages. The blocked person doesn’t learn that you blocked them; they only see that they can’t message you right now.

For this, we store:

• for each message, the internal ID numbers of the sender and the recipient, the text and the time it was sent; if you edit one of your own messages (possible within the first 15 minutes), we store the new text and the time of the edit, not the previous text; if you delete one of your own messages, we delete it completely, for you and for the other person,
• for each chat, up to what time you have read the messages (read status), so that we can show you unread chats; the other person doesn’t see your read status,
• whom you have blocked,
• your setting for who can message you.

To prevent mass sending, we limit the number of messages per IP address. For this, we keep the IP address only in memory, for no more than two minutes after the last message.

Messages are only seen by you and the person you’re chatting with. Chats are not end-to-end encrypted. The transmission between your device and our server is encrypted (TLS); on the server, the messages are stored in a way that we could technically read them. We only look at them if a message is reported (see 3.13) or we are legally required to do so. If you have turned on push notifications, you also receive new messages as a push notification with the sender’s username and the beginning of the message; delivery runs through the push service of your browser vendor (see 3.12).

If you report a message, we store a copy of its text together with the report, as with reported comments (see 3.13). This copy remains even if an account involved is deleted, and is deleted together with the report.

Legal basis: Art. 6(1)(b) GDPR (providing the chat feature), and for limiting messages Art. 6(1)(f) GDPR (protection against misuse). Retention period: We store messages until the sender deletes them or you or the other person deletes their account; read statuses and blocks until one of the two accounts is deleted, and a block also until you lift it. If either of you deletes their account, the whole chat disappears, including the messages the other person wrote.

4. Where your data is stored

We run Animodo at Hetzner Online GmbH, Industriestraße 25, 91710 Gunzenhausen, Germany. The servers are located in Germany. We have a data processing agreement with Hetzner under Art. 28 GDPR.

For the waitlist and email delivery, we use Brevo, based in France (3.13 and 3.15 to 3.18). Processing by Brevo and its subprocessors is not limited to its registered location. The Brevo terms, including its data processing agreement and subprocessors, describe recipients and transfer safeguards. Further international processing may take place at push services (3.12) and Paddle (3.16). You can request information about the recipients and safeguards applicable to our processing at info@animodo.app.

5. Storage on your device

Animodo stores some information locally on your device so that the app works and loads quickly:

This storage serves solely the operation and functioning of the app. Under Section 25(2) no. 2 TDDDG (German Telecommunications Digital Services Data Protection Act), it takes place without separate consent because it is necessary for the service you use, and it involves no tracking. When you sign out, the sign-in token and the account data are deleted.

Animodo itself uses local storage instead of cookies for sign-in. We do not use analytics or advertising cookies. The local storage described here is not cross-site tracking. Paddle may use its own cookies or similar storage technologies for price display and checkout; its information and any required consents apply (3.16).

6. Fonts

Animodo uses the fonts Nunito and Kalam. These files are part of the app and are served by our own server. There is no connection to third-party servers and, in particular, no transfer of your IP address to Google.

7. Who receives your data

• Our hosting provider Hetzner as a processor (see section 4).
• The email service Brevo as a processor for necessary account, contract and support messages, and if you join the waitlist (see 3.15), report content (see 3.13), cancel something (see 3.17) or reset your password (see 3.18).
• Paddle as a separate controller, only if you open the Plus page or get Animodo Plus (see 3.16).
• Your browser’s push service, only when push notifications are enabled: encrypted message content and the connection data described in 3.12.
• Other users, to the extent you cause this yourself by using the app: username and profile picture (3.6, 3.7), to your friends the number of your habits and when you last checked something off (3.3), the Plus badge while you have Plus (3.16), posts, hearts and comments to your friends or the friends of the post’s author, and for public posts to all signed-in users (3.8), shared habits to the friends you share them with (3.9), invitations (3.10), notifications (3.11), messages to the person you write to (3.19), and entries on the ideas board (3.5).

Beyond that, we only pass on your data if we are legally required to do so, for example to law enforcement authorities on the basis of a court order.

8. How long we store data

9. Your rights

You have the following rights with respect to us:

• Access (Art. 15 GDPR): We tell you what data we have stored about you.
• Rectification (Art. 16 GDPR): We correct inaccurate data. You can change most information directly in the app.
• Erasure (Art. 17 GDPR): You can delete your account at any time directly in the app, under Settings → “Delete account”. In doing so, we delete your email address, password, username and settings from the active account record, all habits including icons, flows and triggers, your profile picture, your invitations, your friendships and shared habits, your push subscriptions, all your posts in the feed including photos, your hearts and comments, including those on other people’s posts, your notifications, including the notifications you triggered for others, your chats (all messages you have written or received, also on the other person’s side), read statuses and blocks, and your own entries on the ideas board (for replies and thumbs-up on other people’s entries, see 3.5). The account record retains its randomly generated internal ID number marked “deleted”. The exceptions below may still contain personal data, such as your contact address in a cancellation record. Records that we sent a reminder for a date (3.12) expire after 30 days. Subscription details, including cancellation, remain for the period stated in 3.16, and reports you submitted or that concern your content for the period stated in 3.13. Data that Paddle has stored as the seller is deleted by Paddle according to its own rules; you request deletion at Paddle directly from Paddle.
• Restriction of processing (Art. 18 GDPR)
• Data portability (Art. 20 GDPR): We provide your data to you in a common, machine-readable format.
• Objection (Art. 21 GDPR): You may object, for reasons relating to your particular situation, to any processing we base on Art. 6(1)(f) GDPR, such as the ideas board, abuse prevention, server logs and retention of evidence. We will stop processing unless we can demonstrate compelling legitimate grounds overriding your interests or need the data for legal claims.
• Withdrawal of consent (Art. 7(3) GDPR), with effect for the future, for example by deleting a post, stopping sharing, removing your profile picture, or turning off reminders or push notifications.

You can send requests informally to info@animodo.app. We respond without undue delay, normally within one month. If a legally permitted extension is needed because of the number or complexity of requests, we will explain the reasons within that month. Withdrawing consent does not affect the lawfulness of earlier processing.

Note on identity verification: So that we don’t disclose anyone’s data to someone else, we must be sure that an access or erasure request comes from the account holder. The easiest way is therefore to delete your account directly in the app. For a request by email, we may ask you for additional information.

Right to lodge a complaint: You may complain to a data protection authority, particularly where you habitually live or work, or where the suspected infringement occurred. Our competent authority is the Bavarian State Office for Data Protection Supervision (BayLDA).

10. Security

We protect your data by measures including:

• encrypted transmission via HTTPS
• storing passwords only as a hash
• server-side authentication and permission checks for protected account and content data; public website pages and invitation information are accessible without signing in
• end-to-end encrypted push notifications
• keeping secret credentials separate from program code
• limiting the frequency of requests (rate limiting), especially for signing in, to make automated attacks harder

11. Children and young people

Animodo is intended for people aged 16 and over. We don’t knowingly collect data from children under 16. If you find that a child has sent us data, write to us at info@animodo.app; we will then delete it.

12. Changes to this privacy policy

If the app or the legal situation changes, we update this policy. You can always find the current version at animodo.app/en/datenschutz.