Avenlo Avenlo
Strona główna
Panel Profil
Wyloguj się
Zaloguj się Zarejestruj się

Polityka prywatności

Last Updated: 15 November 2026

Data Controller (Verantwortlicher)

The controller responsible for the processing of your personal data under the EU General Data Protection Regulation (GDPR / DSGVO) is:

Ekin Eser Akcay

Avenlo Media

Helgoländer Str. 32

26316 Varel

Germany

📧 E-Mail: [email protected]

Data-protection and privacy requests can be sent to [email protected], a routed alias that reaches the controller.

1. Who We Are

Avenlo is an AI-powered social media automation platform that helps you create, schedule, and publish content to TikTok, YouTube, and Instagram. This policy explains what data we collect, how we use it, and with whom we share it.

2. What Data We Collect

  • Account data: Your name and email address when you register.
  • Continue with Google (optional): If you choose Continue with Google, we receive your Google account ID, your email address, whether Google has verified it, and your display name. We do not receive your Google password and we do not store a Google access token.
  • Connected accounts: Access tokens for your TikTok, Instagram, and YouTube accounts, so we can publish on your behalf; and the profile details, account statistics (such as follower and subscriber counts), and video performance data (such as views, likes, comments, and shares) those platforms make available for your account, so we can show them to you on the Insights page.
  • Content: Videos, captions, and scheduling details you create or upload.
  • TikTok statistics and videos (only if you connect TikTok and allow it): your account's follower, following, total-like and video counts, saved once a day so Insights can show how they change; the view, like, comment and share counts of videos you published through Avenlo; and, when you open Insights, a live list of your public TikTok videos (title, cover image, link, date and the same counts), which is shown only to you and not stored. This data is deleted when you disconnect the TikTok account or delete your Avenlo account.
  • Payment data: Subscription payment records, processed through Stripe. We never see or store your card details.
  • Usage data: basic logs of actions taken on the platform for billing and support, and, to improve Avenlo, which days you open the signed-in site and when and how often you play, preview or download your own videos (stored with your account only as dates and counts, no cookies, kept for up to 13 months and deleted with your account; legal basis: our legitimate interest in improving the product, Art. 6(1)(f) GDPR, you can object at [email protected]).
  • Tips, offers and news by e-mail (optional): If you tick the box “Email me tips, offers and news from Avenlo”, we first send you one e-mail asking you to confirm (double opt-in). Only after you confirm do we send you tips on using Avenlo (for example, the day after your first video), offers and news about Avenlo. To be able to prove your consent, we store with your account when and where you ticked the box, the wording you agreed to, when we asked you to confirm and when you confirmed. Legal basis: your consent (Art. 6(1)(a) GDPR; § 7(2) no. 2 UWG). You can withdraw it at any time with the unsubscribe link in every such e-mail or under Notification preferences; the record of your consent and its withdrawal is deleted with your account.
  • Sign-up source and checkouts: When you sign up, we record with your account where your first visit in the 24 hours before came from (for example an ad campaign's tags in the address, the website that linked to us, and the first page you opened), and when you start a payment, what you chose, its price and whether the payment was completed. We match the sign-up to that visit on our server with a keyed hash of your IP address (for IPv6, its network part) and browser identifier that changes every day; nothing is stored on or read from your device. We use this only to see which channels bring us customers. Checkout records are kept for up to 13 months; both are deleted with your account. Legal basis: our legitimate interest in measuring our marketing (Art. 6(1)(f) GDPR); you can object at [email protected].
  • Audience data (comments and messages): When you use the Engage features, we retrieve and store the comments on your Instagram and YouTube posts, the comments on your own TikTok videos if you turned on TikTok comments for that account, and the direct messages sent to your connected Instagram accounts — including the sender's platform user ID, username, profile picture URL, the text, and timestamps — and a sentiment label we assign. See section 2a.
  • Voice samples (optional): If you create a voice clone, the audio samples you upload and the resulting synthetic voice. We treat voice samples as biometric data and process them only with your explicit consent (Art. 9(2)(a) GDPR), which you can withdraw by deleting the voice clone.
  • AI inputs and outputs: The prompts, topics, scripts, transcripts, and video frames sent to our AI providers, and the text, audio, images, and videos they return.
  • Assistant conversations: When you write to the Avenlo Assistant (the chat button in the app), we store your messages, the assistant's answers, the page you were on, and what the assistant showed you (for example template suggestions or a filled-in Studio form), linked to your account. We keep them for up to 90 days to answer support requests and to improve Avenlo (for example to see which questions it cannot yet answer); only our team can see them. We do not use them to train AI models, and they are deleted with your account. Legal basis: our legitimate interest in supporting you and improving the product (Art. 6(1)(f) GDPR); you can object at any time by writing to [email protected].
  • Simulation ideas: When you describe an idea for a Simulation video (in the "Describe your idea" box, to the Avenlo Assistant, or in "Describe your own simulation"), we store what you wrote, its language, the Simulation mode or building blocks it was turned into, and what Simulation could not show, linked to your account. We keep them for up to 90 days to see which ideas Simulation cannot show yet, so we know what to add next; our team looks at them as weekly summaries. We do not use them to train AI models, and they are deleted with your account. Legal basis: our legitimate interest in improving the product (Art. 6(1)(f) GDPR); you can object at any time by writing to [email protected].
  • Creator or invite code (optional): If you enter a creator's code or another user's personal invite code, we store the code with your account, when and where you entered it, and, once you pay, the amounts of your paid invoices (also as metadata in Stripe). We use this to give you the code's perk and to attribute your signup to that creator, for example to pay them a commission. A creator, or the user whose invite code you used, only sees totals (how many people signed up with their code), never who you are. If you used another user's invite code, we also check whether your e-mail address is verified and whether you have made a first video, so that we can credit that user's invite coins; they are then told that a friend made their first video and see the number of such friends, but not your name or e-mail address. We do not use cookies or device storage for this. Legal basis: performing our contract with you (your perk) and our legitimate interest in knowing which creators bring us customers (Art. 6(1)(f) GDPR).
  • Abuse checks for codes: To stop people from collecting code bonuses with many accounts, our server calculates a pseudonymised device signal when you sign up or sign in, when you open your own invite code, and when a code is used: a keyed hash of your IP address and browser identifier (user agent) that changes every day. Nothing is stored on or read from your device for this (no cookie, no local storage). We compare it only between the account that used a code and the account the code belongs to. A match never blocks you automatically; it only holds the bonus coins until a member of our team has reviewed it. We also do not accept sign-ups from temporary (throwaway) e-mail services. We keep the device signals for at most 6 months and delete them with your account. Legal basis: our legitimate interest in preventing fraud (Art. 6(1)(f) GDPR). You can object at any time by writing to [email protected]; we then stop collecting the signal for your account and delete the signals we have.
  • Character photos (optional): If you upload a photo for a character, we process it to create the character's pictures and videos at your request (Art. 6(1)(b) GDPR). We remove the file's metadata and store it privately on our server in the European Union; it is visible only to your account. To draw the character it is sent to our AI providers, Replicate (USA) and, for an automatic safety check, Anthropic (USA), as processors under standard contractual clauses. We do not create or store biometric templates for identifying anyone. You can delete a photo at any time by deleting the character; it is also deleted with your account. Copies of the drawn character inside a video are deleted with that video. If you upload a photo of another person, you confirm that you have their permission and that you have told them how it will be used.
  • Pictures you upload for videos (optional): If you upload a picture to use in a video (for example on the balls or as the background of a Simulation), we use it only to make your videos (Art. 6(1)(b) GDPR). We remove the file's metadata and store it privately on our server in the European Union; it is visible only to your account. We record when you uploaded it, as your confirmation under our Terms that you may use it. Before it is used, it is checked once by an automated image model of our AI provider Anthropic (USA), as a processor under standard contractual clauses, to refuse pictures of children and sexual content. A picture is kept while a video uses it. It is deleted when you delete it, when the last of your videos that uses it is deleted or expires, or when you delete your account. An uploaded file that no video uses is removed after 7 days.
  • Technical data: IP address, browser/user-agent, and request metadata in security and audit logs (see section 10).

2a. Information for people who interact with our customers' accounts

If you have commented on a YouTube, Instagram or TikTok post, or sent a direct message to an Instagram account, that is managed with Avenlo, the owner of that account may have chosen to manage their comments and messages through Avenlo. In that case Avenlo stores, on the account owner's behalf, your public platform user ID and username, your profile picture URL, the text of your comment or message, its time, and a sentiment label (positive / neutral / negative) that helps the account owner sort their inbox. Replies you receive may be written by the account owner or sent automatically under rules they configured; automatic replies are marked as such.

  • Who is responsible: the account owner is the controller of this data; Avenlo acts as their processor under a Data Processing Agreement. The legal basis the account owner relies on is their legitimate interest in managing messages sent to their own account (Art. 6(1)(f) GDPR).
  • What we do not do: we do not use your comments or messages for advertising, profiling, or AI training, we do not sell them, and we do not send them to our AI providers.
  • How long: comments are kept for up to 30 days after they were last retrieved from YouTube, and up to 180 days for Instagram and TikTok; message conversations are kept for up to 90 days after the last message. Everything is deleted when the account owner disconnects the account or deletes their Avenlo account.
  • Your rights: you can ask for access to, or deletion of, your comment or message data by e-mailing [email protected] — we will forward your request to the account owner where necessary and answer within 30 days. You can also object to the processing (Art. 21 GDPR) and complain to a supervisory authority (see section 8).
  • Because we cannot contact every commenter individually, we provide this information publicly under Art. 14(5)(b) GDPR.

3. How We Use Your Data

  • To run your account and provide our services.
  • To publish content to your connected social media accounts.
  • To manage your coin balance and process payments.
  • To send you important notifications about your account.
  • To respond to your support requests, including by looking at your recent conversations with the Avenlo Assistant.
  • To improve Avenlo, for example by seeing what people ask the Avenlo Assistant.
  • To detect and prevent fraud or abuse.

Legal bases (Art. 6 GDPR): running your account, publishing on your behalf, processing payments, and sending account notifications are necessary to perform our contract with you (Art. 6(1)(b)). Security logging, fraud prevention, and defending legal claims are based on our legitimate interests (Art. 6(1)(f)). Keeping payment records is a legal obligation (Art. 6(1)(c), §147 AO / §257 HGB). Voice cloning and any optional feature we mark as consent-based rely on your explicit consent (Art. 6(1)(a), Art. 9(2)(a)), which you can withdraw at any time with effect for the future. Providing your name, e-mail, and a password is required to open an account; everything else is optional.

Automated decision-making: we do not make decisions about you based solely on automated processing that produce legal or similarly significant effects (Art. 22 GDPR). Automatic rate limits may temporarily slow requests; account suspensions are reviewed by a person.

We do not sell your data or use it for advertising.

4. Google User Data

Avenlo's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Avenlo uses YouTube API Services. When you connect your YouTube account, Avenlo receives access to your Google account data via OAuth 2.0. Google's own handling of that data is governed by the Google Privacy Policy. Specifically:

  • We access your YouTube channel information (name, avatar, subscriber count) to display inside your Avenlo dashboard.
  • We upload videos to your YouTube channel on your behalf when you trigger or schedule a publish action — or, if you have enabled Auto‑Pilot, automatically on the schedule and settings you configured. You can pause or disable Auto‑Pilot at any time.
  • If you use the Engage feature, we read the comments on your videos and post replies that you write or that you have explicitly configured as automatic reply rules.
  • We do not sell, rent, transfer, or share your Google user data with any third parties.
  • We do not use Google user data for advertising purposes.
  • We do not use Google user data to train AI or machine learning models.
  • Google user data is used solely to provide the YouTube publishing and analytics features of Avenlo and, if you choose Continue with Google, to sign you in and to create and secure your account.
  • You can revoke Avenlo's access to your Google account at any time via the Google security settings page at security.google.com/settings/security/permissions, or by disconnecting the account inside Avenlo. Disconnecting or revoking deletes the YouTube data Avenlo holds; it does not delete anything on YouTube itself.

5. Third-Party Services

We use the following third-party services to operate Avenlo:

  • Stripe — for payment processing.
  • Google (YouTube Data API v3) — for YouTube content publishing and channel analytics.
  • Google (Sign in with Google) — to sign you in, if you choose it.
  • TikTok — for TikTok content publishing via their official API; if you allow it, reading your account statistics and video list for Insights; and, for accounts where you turned on TikTok comments, reading and managing the comments on your own videos (TikTok API for Business).
  • Meta (Instagram Graph API) — for Instagram content publishing via their official API.
  • Wikidata (Wikimedia Foundation, USA) — when a Transit Map video names a place we can't find in our own map data, we send that place name to Wikidata to find where it is. Only the place name is sent, not your account details.
  • netcup GmbH (Karlsruhe, Germany) — hosting of the server that runs Avenlo and stores the data described in this policy, in a data centre in the European Union.
  • Cloudflare, Inc. (USA) — CDN, DDoS protection, and bot management; processes request metadata (such as IP address and request headers) as it proxies traffic to our servers.
  • Cloudflare, Inc. (USA) — R2 object storage — off-site backup storage. Stores backup copies of our database, which contains the personal data described in this policy (including audience data), and of user files, including support-ticket attachments and the voice samples you upload for voice cloning. The backups are stored in Cloudflare's Western Europe region; they are not held under Cloudflare's EU data-jurisdiction setting, and Cloudflare, Inc. is a US company (see section 11).
  • Anthropic PBC — Claude API (USA) — AI text generation for video scripts, captions, and post copy, and the answers of the Avenlo Assistant, and the automatic safety check of photos and pictures you upload; receives the prompts, topics, and text you provide for generation, the messages you write to the assistant, and the photos and pictures to be checked.
  • ElevenLabs, Inc. (USA) — AI voice generation; receives the script and dialogue text you provide (and, for voice cloning, the audio samples you upload) to synthesise speech, and transcribes the audio of videos for captions.
  • Replicate, Inc. and OpenAI, L.L.C. (USA) — AI image generation; receive the image prompts you provide.
  • Resend, Inc. — transactional email service (EU region) — sends transactional emails (verification, password reset, account notifications) on our behalf; receives your email address and the message content. This account is configured to operate from Resend's EU region (EU data residency).
  • Pixabay — royalty-free background-music search; receives only non-personal mood and search queries.

Each of these services has its own privacy policy that applies to the data they handle. We do not share your personal data with any of these services beyond what is strictly necessary to provide our features.

Discord. If you connect your Discord account, we store your Discord user ID, username and avatar reference with your Avenlo account. We use them to give you server roles matching your plan and to recognise you in our Discord server. You can disconnect at any time in your profile.

Support on Discord. Only tickets you open yourself in our Discord server are stored on Discord. Such a ticket is kept in your Avenlo account and in a private Discord thread visible to you and our support staff, and our replies appear in both places. Files you add in the thread are copied to our servers. Tickets you open on our website stay on our website and are not sent to Discord.

Moderation on Discord. To keep the server safe, an automated, rule-based system checks messages sent in the server for spam, mass mentions, invite links and join floods, and may remove messages or temporarily restrict accounts. We keep a record of moderation actions, linked to your Discord user ID, for 12 months.

Discord as a recipient. Discord Inc., USA, processes this data as an independent provider under its own privacy policy. Discord states that it relies on the EU–US Data Privacy Framework and the European Commission's Standard Contractual Clauses for transfers from the EEA. Our legal bases are Art. 6(1)(b) GDPR for handling a support request you open on Discord and Art. 6(1)(f) GDPR for moderation (our legitimate interest in a safe community). When you delete your Avenlo account, your connection, your tickets and their Discord threads are deleted. Messages you post in public channels remain under your control on Discord.

6. Data Sharing & Disclosure

We do not sell, rent, or trade your personal data. We only share data in the following limited circumstances:

  • With social media platforms: We share your content and account tokens with TikTok, YouTube, and Instagram solely to publish on your behalf.
  • With Stripe: We share transaction identifiers with Stripe to process payments. Stripe does not receive your social media data.
  • Legal requirements: We may disclose data if required by law or to protect the rights and safety of our users.

No other sharing, transfer, or disclosure of your data takes place.

7. How Long We Keep Your Data

  • Your account and content are kept until you delete your account.
  • Your Google account ID is deleted together with your account.
  • When you delete your account we keep, for 12 months, a keyed hash of your email address and, if you used Continue with Google, of your Google account ID. We cannot read your address from it. It is used only to stop the free welcome coins being claimed again (Art. 6(1)(f) GDPR).
  • Payment records (purchase and subscription records, amounts, Stripe identifiers) are kept for up to 10 years as required by German tax and commercial law (§147 AO, §257 HGB), even after you delete your account; we keep only what the law requires.
  • Videos generated by Avenlo are kept in your library for up to 7 days unless you save them to your storage; unused uploads are removed after 24 hours; thumbnails after 7 days.
  • Audience data (comments and messages): see section 2a.
  • Conversations with the Avenlo Assistant are deleted automatically 90 days after they start, or earlier when you delete your account.
  • Simulation ideas are deleted automatically 90 days after you wrote them, or earlier when you delete your account.
  • Voice samples and voice clones are kept until you delete the voice clone or your account, and are then deleted from our systems and from ElevenLabs.
  • Security and audit logs: see section 10.
  • Deletion requests relayed to us by Meta are recorded (platform ID and status only) for 90 days so that you can check their status.
  • When you disconnect a social media account, we immediately and permanently delete both the access tokens and the data we derived from that account — including analytics snapshots, video performance metrics, cached comments, and publish/upload records. This deletion is irreversible.

8. Your Rights

Under the GDPR you have the right to access your personal data (Art. 15), to have it corrected (Art. 16) or deleted (Art. 17), to restrict processing (Art. 18), to receive the data you provided in a machine-readable format (data portability, Art. 20), and to withdraw consent at any time (Art. 7(3)) without affecting the lawfulness of processing before withdrawal.

Right to object (Art. 21 GDPR): you may object at any time, on grounds relating to your particular situation, to processing that is based on our legitimate interests (such as security logging). We will then stop unless we can demonstrate compelling legitimate grounds that override your interests, or the processing serves to establish, exercise, or defend legal claims.

How to exercise your rights: you can correct your profile and delete your account yourself in Profile, disconnect social accounts in Social Accounts, export your analytics as a PDF report from the Insights page, and follow the Data Deletion page for platform-initiated deletion requests. For everything else, including a full copy of your data in a machine-readable format, email us at [email protected] and we will respond within 30 days.

Right to complain: you have the right to lodge a complaint with a data-protection supervisory authority, in particular in the EU member state of your habitual residence, place of work, or of the alleged infringement. The authority responsible for us is Die Landesbeauftragte für den Datenschutz Niedersachsen, Prinzenstraße 5, 30159 Hannover, Germany, lfd.niedersachsen.de. UK users may contact the Information Commissioner's Office.

9. Security

We implement appropriate technical and organisational measures to protect your personal data against unauthorised access, loss, or misuse.

10. Security and Audit Logging

To keep the platform secure and to investigate abuse, we record two kinds of operational logs:

  • Security events — such as failed login attempts, rate-limit hits, and suspicious request patterns. These are stored with the originating IP address and a country derived from it, and are kept for 30 days before automatic deletion.
  • Audit logs — a record of actions taken on your account (for example sign-ins, account connections, and security-relevant changes). These are kept for 10 days before automatic deletion.

The legal basis for this processing is our legitimate interest in the security and integrity of our service (Art. 6(1)(f) GDPR / DSGVO).

11. International Transfers

Our main server is in the European Union. The server that runs Avenlo and stores the personal data described in this policy — account data, content, connected-account data, audience data, and logs — is hosted by netcup GmbH, Germany, in a data centre in the European Union. Storing your data on this server is not a transfer to a third country.

Some of our service providers — including Stripe, Cloudflare, Anthropic, ElevenLabs, Replicate, OpenAI, and Google — are located in the United States. For transfers to these providers, we rely on appropriate safeguards under Art. 44 ff. GDPR / DSGVO, namely the providers' certification under the EU–US Data Privacy Framework and/or the European Commission's Standard Contractual Clauses (SCCs).

12. Cookies and Third-Party Content

We use only cookies that are strictly necessary to operate the service and keep it secure. We do not set advertising, analytics, or tracking cookies, so no cookie-consent banner is required. The cookies we use are:

  • token — your authentication session (a JWT). HttpOnly, Secure, SameSite=Lax.
  • csrfToken — a CSRF-protection token (synchronizer pattern). Secure, SameSite=Lax, readable by the page's JavaScript.
  • oauth_state_* — short-lived (15-minute) signed cookies set only during a social-account connection flow to secure the OAuth handshake.
  • google_signin_flow, google_signin_pending, google_reauth_proof — short-lived signed cookies (15, 30 and 5 minutes) set only if you use Continue with Google, to secure the sign-in.
  • __cf_bm — set by Cloudflare for bot management when traffic passes through their network.

Fonts and scripts. All web fonts and JavaScript libraries our pages use are served from our own servers (through Cloudflare, our reverse proxy — see section 5). Your browser does not contact Google Fonts or any other third-party font or script CDN when you use Avenlo.

13. Children

Avenlo is not intended for, and may not be used by, anyone under 16. You must be 18 to buy a subscription. We ask you to confirm your age when you register and do not knowingly collect data from children; we do not direct our service at children. If you believe a minor has created an account, contact us at [email protected] and we will remove it.

14. Changes

If we make significant changes to this policy, we will notify you by email at least 14 days before they take effect.


Related Policies

Data Processing Agreement for business customers · AI Disclosure · Acceptable Use Policy · Data Deletion · Report Content

Contact

For any privacy-related questions or data requests:

📧 [email protected]

Legal Pages

Terms of Service · Privacy Policy · Impressum · Refunds & Cancellation · Right of Withdrawal · Cancel Contract · Acceptable Use · AI Disclosure · Report Content · Data Processing Agreement · Data Deletion