Privacy Policy

Data processed: email address, password (cryptographically hashed by the Media API), JWT authentication token, optional billing data. When signing in with Google, the email address, display name and profile picture provided by Google (no password is processed in that case). To verify the email address and reset the password, we send a single-use confirmation/reset link by email.

Storage: the JWT is held in the browser in an HttpOnly cookie (for the proxy) and in localStorage (for server actions). Any 401 response triggers immediate logout and deletion of the token.

Purpose: provision of the SaaS service and user identification.

Legal basis: performance of a contract (GDPR Art. 6(1)(b)).

Data processed: the App name, unique identifier and associated API key.

Purpose: isolation of App-level resources (platforms, videos, schedules, jobs, S3 storage). Requests are authenticated to the Media API using the x-api-key header.

Legal basis: performance of a contract (GDPR Art. 6(1)(b)).

Data processed: identifiers, profile pictures, display names, access and refresh tokens (and their expiry) for YouTube, Facebook, Instagram, TikTok, Threads, LinkedIn and Pinterest accounts, as well as analytics data related to post performance (e.g. views, likes, shares, reach, watch time, estimated revenue – where returned by the platform’s API).

Purpose: automated content publication on connected platforms on behalf of the User, and measurement of post results.

Legal basis: explicit consent of the data subject during the OAuth flow (GDPR Art. 6(1)(a)) and performance of a contract.

Note: we do not know or store external platform passwords; the connection is made exclusively through official OAuth tokens. The User can revoke access at any time in the platform account settings, which immediately invalidates the token stored with us.

Data processed: uploaded videos, thumbnails, text prompts provided for AI generation, generated videos and associated metadata (title, description, hashtags, size, duration). For the text-to-speech (TTS) feature, the text to be narrated.

Purpose: storage, AI-based video generation using S3-stored templates, voice-over generation, preparation for publication on social media platforms.

Legal basis: performance of a contract.

Note: the text to be narrated is sent to the Microsoft Edge TTS service to produce the voice-over (see Data processors). Uploaded or generated content may contain personal data (e.g. faces, voices); the uploading User is therefore responsible as an independent controller for such content and its lawful processing, with Uplonic acting as a processor in this respect.

Data processed: cron-based scheduling rules, the status of generation and upload jobs, error logs, the content of Media API webhook events (/api/webhooks/media) delivered to the User’s browser via SSE.

Purpose: task automation, real-time status reporting, error diagnostics.

Legal basis: performance of a contract; legitimate interest in fault detection.

Data processed: the name (optional), email address, subject and message provided in the contact form, together with the technical context of the submission (the page URL and interface language). To filter abuse we use a Cloudflare Turnstile bot check and a hidden “honeypot” field.

Purpose: answering requests, customer support and spam filtering.

Legal basis: legitimate interest in handling requests and preventing abuse (GDPR Art. 6(1)(f)), and consent given for contacting us (a).

Data processed: aggregated, cookieless usage events (e.g. page views, login, App creation, starting a video generation, pricing views, subscription steps). These do not create a cross-session identifier linkable to an individual.

Purpose: understanding and improving use of the Service.

Legal basis: legitimate interest in non-identifying, aggregated statistics (GDPR Art. 6(1)(f)).

Data processed: the hash of the session refresh token, the IP address, the user agent (browser/device identifier), the time the session was last used, as well as operational and security event logs (EventLog) and error messages.

Purpose: maintaining sign-in, managing active devices, preventing abuse, operation and debugging.

Legal basis: legitimate interest in account and service security (GDPR Art. 6(1)(f)).

Data processed: the Stripe customer ID, subscription status, the chosen plan, currency and billing period. Uplonic does not store card data; payments are processed by Stripe (PCI-DSS).

Purpose: handling fees and subscription management.

Legal basis: performance of a contract (GDPR Art. 6(1)(b)) and legal obligation to retain accounting records (c).

Data processed: in-app, email and webhook notifications (e.g. failed payment, expiring token, schedule outcome, product news) and notification settings.

Purpose: service-related transactional notifications and – with consent – marketing/product-news notifications.

Legal basis: performance of a contract for transactional notifications (GDPR Art. 6(1)(b)); consent for marketing (a).

Data processed: for comments and replies that other people leave under content on the User's connected Facebook Page, Instagram professional account, Threads profile and YouTube channel, we store the commenter's display name or username, profile picture URL, the comment text, its time, like count and platform identifier, and the internal status set by the User (unanswered / replied / resolved). We also store the replies the User writes in Uplonic and publishes to the platform.

Source: the official APIs and webhooks of the platforms, only for the accounts the User explicitly connected. We do not collect comments from any other account.

Purpose: showing the comments in the User's Comments inbox so the User can read and answer them in one place. Replies are published only when the User writes and sends them; Uplonic does not post, like, hide or delete comments automatically.

Role and legal basis: with respect to commenters' data the User (the owner of the connected account) is the controller, and Uplonic acts as the User's processor. The processing is based on the User's legitimate interest in managing the communication with their own audience (GDPR Art. 6(1)(f)). Commenters' data is not used for profiling or advertising, is not combined across Users, and is not shared with third parties.

Retention: while the channel stays connected. When the channel is disconnected, or a deletion request is received (see 3.12), all stored comments of that channel are deleted immediately. A comment deleted on the platform is removed from Uplonic when the platform notifies us of the deletion.

You can have all data we received from Meta about you deleted in three ways: (1) by disconnecting the channel on the Platforms page in Uplonic; (2) by removing Uplonic in your Facebook settings (Apps and websites) or Threads settings and sending a deletion request — Meta then notifies us automatically, we delete every channel connected with that account, and you receive a confirmation code; or (3) by email to info@uplonic.com. The deleted data covers the access tokens, the account name and picture, post statistics, follower statistics, stored comments and the publishing history of the affected channels. Step-by-step instructions and the status of a request (by confirmation code) are available at uplonic.com/legal/data-deletion.

Removing Uplonic in the Meta settings without requesting deletion only revokes our access: the affected channels are deactivated, but their data is not deleted.

Data processed: the email address you enter in the newsletter box on the blog, guides or news pages, the interface language, the page you signed up from, and the time of your consent. A hidden “honeypot” field and an IP-based rate limit filter automated sign-ups; the IP address is not stored with the subscription.

Purpose: sending the Uplonic newsletter (new guides, creator data, platform changes). We do not send newsletters yet; before the first issue we email you once to confirm your address, and only confirmed addresses receive the newsletter. Every newsletter will contain an unsubscribe link.

Legal basis: your consent (GDPR Art. 6(1)(a)), which you can withdraw at any time by unsubscribing or by email to info@uplonic.com.

If you connect an external AI application (e.g. Claude, ChatGPT, Cursor) through our MCP server, we process: the client’s identifier and the name, logo address and redirect address it provides; the connection itself (which user, which workspaces and which permission in each — read only or read and write —, the workspaces’ short identifiers, and when it was approved, last used and revoked); the access and refresh tokens in hashed form only; and an audit log of the operations the AI invoked (the operation’s name, its masked and truncated parameters, the outcome, the error code, the duration and the time). We do not log the results of the operations, i.e. what we hand to the AI.

Purpose: to let the AI assistant you chose read the approved workspaces on your behalf (media library, channels, time slots, publishing status, analytics, unanswered comments) and, with write access, perform operations (scheduling, approval, retries, replying to comments). The log serves to detect abuse and to keep the connection secure: if a connection repeatedly tries to reach a workspace it was not granted, we notify you.

Legal basis: performance of the contract for operating the connection (GDPR Art. 6(1)(b)); legitimate interest in account and service security for the audit log (Art. 6(1)(f)).

Recipient: the operator of the AI application (e.g. Anthropic, OpenAI, Anysphere) is not Uplonic’s processor but an independent provider chosen by you. The results of the operations — including the comments and commenter names described in 3.11 — are passed to it and processed under its own terms. You decide about this transfer: a connection is created only with your explicit approval, covers only the workspaces you select (at most 25) with the permission you set for each, its workspace list can be changed at any time, and it can be revoked at any time on the “AI integration” tab of the Developers page — revocation immediately invalidates all of the connection’s tokens. As the controller under 3.11, you are responsible for passing on the data of third parties (e.g. commenters) contained in the results.

Retention: an active connection is kept until it is revoked or the account or workspace is deleted; expired tokens are deleted daily; data of revoked connections and the audit log are kept for a maximum of 12 months.

The AI assistant on the Analytics page (summary, “What works?”, video ideas) analyses the workspace’s published content. For this we send Google’s Gemini model: the content titles (at most 160 characters), platform, channel name, publishing time, video length, the content’s topic classification, and performance metrics (views, likes, comment and share counts, follower counts) together with the aggregates we calculate from them. For post-text suggestions and for the clip editor’s segment selection we send the video’s title, description or transcript.

We do not send the model email addresses, usernames, passwords, access tokens or API keys, and the AI assistant does not receive the text of comments or commenters’ names (only comment counts).

Results we store: the generated analyses (summary, findings and their underlying aggregates), video ideas and their status (saved / dismissed / used), the topic classification of the content, the 👍/👎 feedback on findings, and a usage log (which workspace, which user, which operation, the credits and tokens used) to account for the plan’s allowance.

Purpose: providing the analysis and content-planning feature that is part of the Service, accounting for the allowance, and improving the feature’s quality.

Legal basis: performance of the contract (GDPR Art. 6(1)(b)); for the feedback and the usage log, legitimate interest in improving the feature and preventing abuse (Art. 6(1)(f)). For the analysed content the workspace owner is the controller and Uplonic acts as processor.

Recipient: Google (Gemini API, paid service tier) as processor, including in the United States (see sections 5 and 6). On the paid tier Google does not use the data sent to train its own models. The model’s answer is shown as plain text; every number and piece of evidence is checked against our own data.

Switching off and retention: the AI assistant can be switched off in the workspace settings; no new analyses are then created and the weekly automatic analysis does not run. Stored results are kept until the workspace is deleted; earlier deletion can be requested at info@uplonic.com.