Your accounts and your data.
Giving a publishing tool access to your social accounts takes trust. This page describes what we do in return: what we store, what we don't, and how control stays with you.
We never ask for your password
You connect accounts through each platform's own consent screen. Your social media password stays on that screen and never reaches us — which means we can't leak it either.
Permissions stored encrypted
Access and refresh tokens are held encrypted in the database. They're decrypted only at the moment a post is being published, for that one job.
Least-privilege by default
We request permission only to read the account name and to publish posts. We don't request follower, message or analytics access — and because we don't request it, we can't read it.
Control stays with you
Disconnect a channel whenever you want; delete your account whenever you want. Both happen in the dashboard, without asking us.
What data do we store?
This is the complete list. If it isn't here, we don't store it.
- Your account details
- Your email address and your name if you provided one — so you can sign in and so team invitations reach the right person.
- Connected channels
- Each channel's platform identifier, display name, avatar URL and encrypted access permissions.
- Your posts
- The text you wrote, the images and videos you uploaded, the scheduling information and the publishing result.
- Team information
- Your company name, team members and pending invitations.
- Technical logs
- Operational logs kept for debugging. Post content is not written to these logs.
What we do in practice
Security isn't a feature list; it's a set of decisions applied consistently.
Row-level access control on the data
The database itself enforces, on every query, that a user can only reach their own company's data. Even if a bug slips into application code, data doesn't leak.
Signed, short-lived media URLs
Some platforms download the image themselves, and they do it without signing in. That's why file URLs are signed and expire shortly after — someone who intercepts a URL can't reuse it.
Keys live only on the server
Access permissions and the encryption key exist only on the server side. They are never sent to the browser.
A single canonical address
The app is reachable only at postju.com. That's not a matter of tidiness: OAuth redirect URIs are derived from the request's host, and a second address would mean platforms redirecting to a URI that isn't registered.
How to delete your data
You don't need to email us for a deletion request; both of these are one click in the dashboard.
- To remove a single channel: remove it from the Channels screen. The access permission we stored is deleted at that moment.
- To delete your entire account: delete it from the Settings screen. Your posts, uploaded media and connected channels go with it.
- If you have another request, write to our support address; we respond within the period stated in our privacy policy.
Have a question?
If there's anything you want to know about security or data, write to us. You'll also find detailed answers in our privacy policy.
No account yet? You'll create one on the same screen. You can also continue with Google in a single click.