Legal
Privacy
Every kind of data Postia holds about you, in the order it arrives, with the reason it is held next to it.
Last updated 15 September 2026.
The short of it. Postia stores your email, what you write, and the tokens that let it publish on your behalf. It does not sell any of that, does not use it for advertising, and does not use your posts to train anything. Payment details never reach us: Paddle handles them.
Who is responsible
The controller of the personal data described here is KVLK Studio — Danylo Kovalenko, an individual entrepreneur (ФОП) registered in Ukraine under tax number 3620110199, of 15A Arkhitektora Nikolaieva St., Kyiv 02226, Ukraine.
What Postia stores, and why
- Your email address
- It is the account. Sign-in codes go to it, and so do notifications you have left switched on. Kept for as long as the account exists.
- Sign-in codes
- A six-digit code, good for ten minutes. The record of it is deleted once it has been used or has expired.
- Your preferences
- The name you asked to be called, your timezone, your language, whether the app is painted light or dark, and which notifications you want. The timezone is not a convenience: it is what decides the hour a scheduled post goes out.
- Your connected accounts
- For each channel: the network, the account's identifier and display name on that network, its avatar, and the access token the network issued. Tokens are stored encrypted, never leave the server, and are never sent to the app.
- Your posts
- The text, the images you attached, the destinations you chose, the time you scheduled, and what each destination answered when the post was sent. Kept until you delete the post or the account.
- Analytics
- Counts of what Postia published, failed to publish or skipped, and the audience figures the networks report once a day. These are figures about your channels, not about the people who read them.
- Support messages
- What you write to support, with your account attached so we know whose problem it is.
- Billing records
- Which plan you are on, when it renews, and the identifiers Paddle uses for your subscription. Card numbers are not among them and never reach us.
- Server logs
- Ordinary records of requests, kept briefly for diagnosing faults and abuse.
What Postia does not do
- It does not sell personal data, and there is nobody to sell it to: there are no advertising or analytics trackers in the product.
- It does not use your posts, images or drafts to train a model, ours or anyone else's.
- It does not read the audience of your channels. Postia sees the numbers a network publishes about a channel, not the people behind them.
- It does not post, suggest or send anything you did not schedule.
Why we are allowed to hold it
Most of it is held because it is necessary to provide the service you asked for, which is the performance of our contract with you. Billing records are kept because the law requires them to be. Logs and abuse prevention rest on our legitimate interest in keeping the service running and safe.
Who else sees it
- The networks you connected. A post you send to Telegram goes to Telegram, with whatever you attached to it. Each network then handles it under its own privacy policy. Data Postia receives from Google is covered by its own section below: it goes back to Google and to nobody else.
- Paddle. Payments, invoices, tax and refunds. They receive what a payment needs, including your email and billing country, and act as merchant of record.
- Google Fonts, on this marketing site only. The typefaces on this page are fetched from Google's servers, which means your browser's request reaches Google, including your IP address. The app itself does not do this.
- Google Analytics, on this marketing site only, and only if you allow it. Google receives which pages you open and which buttons you press here, with your approximate location and the kind of device you use. The app itself does not use it.
No email provider is on that list, because there is not one: sign-in codes and notifications are sent by our own mail server, so the addresses they are going to are not handed to anybody along the way.
Beyond these, personal data is disclosed only where the law requires it.
Data from Google: YouTube and Blogger
You can connect a YouTube channel or a Blogger account to Postia. Each is a separate Google sign-in that asks for one permission only, and only when you connect that service.
- YouTube — permission to manage your YouTube account
- When you connect, Postia reads your channel's identifier, name and picture, to show which channel is connected. When you schedule a video, Postia uploads it with the title, description, tags, thumbnail and settings you chose, and adds it to the playlist you picked; to let you pick one, it reads the list of your playlists. When you ask Postia to take down a video it published, it deletes that video. It does nothing else with your channel.
- Blogger — permission to manage your Blogger account
- When you connect, Postia reads your Blogger profile's identifier and display name and the list of your blogs, so you can choose which to post to. When you schedule a post, Postia publishes it to the blog you chose. When you ask Postia to take a post down, it deletes that post. It does nothing else with your blogs.
- Google's access and refresh tokens
- What lets Postia do the above on your behalf. They are stored encrypted, as described under How it is protected, and are deleted the moment you remove the channel from Postia.
Who Google user data is shared with. Nobody. Postia does not sell, share, transfer or disclose Google user data to any third party. It is not passed to advertisers, data brokers or analytics services, and it is not used for advertising or to train any model. The only place it goes is back to Google: the video or post you scheduled is sent to YouTube or Blogger, because that is what you asked for. It is disclosed otherwise only if the law requires it.
Who reads it. No person at Postia reads your Google data, except with your explicit permission (when you ask support to look into a problem with a video or post), to deal with security or abuse, or where the law requires it.
Postia's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Postia uses the YouTube API Services. By connecting a YouTube channel you also agree to the YouTube Terms of Service, and Google handles your data under the Google Privacy Policy. You can take back Postia's access at any time from your Google account's third-party connections page; removing the channel in Postia deletes its tokens as well.
How it is protected
- In transit. Everything between the app, our server and the networks goes over HTTPS, encrypted with TLS.
- Access tokens at rest. The tokens networks issue for your channels — Google's access and refresh tokens among them — are encrypted with AES-256-GCM, each with a fresh nonce, before they are written to the database. The key is kept in the server's configuration, not in the database, so a copy of the database on its own does not reveal them.
- Never sent to the app. Tokens are only ever used on the server. The app, the browser and the phone never receive them.
- Separated by account. Every request is checked against the account that makes it, so one account cannot see or change another's posts, channels or tokens.
- Kept only as long as needed. Removing a channel deletes its tokens straight away; deleting your account deletes your posts, channels and settings with it.
Where it lives
Postia runs on a single server, with its database on the same machine, hosted in Germany. Images you upload are stored alongside it. The mail server that sends you sign-in codes is ours as well, and runs on its own machine. Nothing is copied to a third-party analytics service.
How long it is kept
Account data lives as long as the account. Deleting a connected channel removes its tokens straight away. Deleting your account removes your posts, your channels and your settings with it; billing records are kept for as long as tax law requires, and backups roll off on their own schedule.
There is no self-service delete button in the app yet. Ask through support and we will do it, and confirm when it is done.
Your rights
You can ask us for a copy of the personal data we hold about you, to correct it, to delete it, to restrict what we do with it, to object to processing that rests on legitimate interest, and to receive it in a portable form. Ask through support in the app.
If you think we have handled your data badly, you can complain to the data protection authority where you live, whatever we say about it.
Children
Postia is not for children. We do not knowingly hold data about anyone under 16, and we delete it if we learn we have.
Changes
If this policy changes in a way that matters, the date at the top moves and the change is announced in the app before it takes effect.