What we hold, who can see it, and what we have not done yet
You are about to give Postiplex access to your blog and your social accounts. This page says exactly what that means, in plain words, with the gaps included.
- What we store about you
- Your account email, your business profile as you confirmed it, your website's scanned pages, the keywords researched for you, the articles, images, posts, episodes and videos we made, their publishing results, the tokens for your connected accounts, and the analytics those platforms return.
- What we never store
- Passwords for any of your accounts, card numbers (payments, when live, go through a payment provider), and anything from your customers' side of your business.
- Who can see it
- You, and anyone you add to your account. On our side, the people who build Postiplex, for support and debugging, under the same access rules as the app.
- Where it lives
- A Postgres database and file storage at Supabase, the app on Vercel, the media service on Railway.
- Deleting it
- Disconnect any channel from Integrations at any time; the token is deleted. To close an account and delete everything, email hello@postiplex.com. What was published to your own site and accounts stays yours.
What is in place
Every row belongs to one customer
All data is keyed by your website's account. Every query the app makes is scoped to that account at the point it is built, and the scoping was audited call by call. Row-level security is on and deny-by-default on every table, so nothing can be read through the database API with the public key.
No passwords, only tokens
Social channels connect through each platform's own sign-in; we keep the token it issues, which you can revoke there. WordPress uses an application password you create; Shopify a custom app with content scopes only. The app never sees a password of yours.
Untrusted text is treated as data
Your website's pages, and the pages that rank, are fed to the model as quoted material with an instruction that nothing inside them is a command. Model output never touches the database directly; the app writes it.
Secrets stay on the server
API keys for the model, search and publishing providers are server-side environment variables. None ship in the browser bundle. Staged files are checked for secrets before every commit.
Encrypted in transit and at rest
Every connection is HTTPS. The database, file storage and backups at Supabase are encrypted at rest; Vercel and Railway do the same for what they run.
Backups
Supabase takes automatic daily backups of the database. Everything we publish also lives on your own site and accounts.
Nothing real is touched by tests
The daily test suite runs against a throwaway database with every outside service faked; any call that tries to reach the real internet fails the run.
Not done yet
Said here so you do not have to ask.
- No third-party certification (SOC 2, ISO 27001) and no external penetration test yet. We will say so here when either is done.
- Rate limits on the money-spending endpoints are a per-account cap on planning runs today, not a general limiter; vendor-side spend caps back it up.
- Payments are not live yet; when they are, webhook signatures will be verified and plan checks enforced on the server before anything else ships.
- There is no customer-facing audit log of who changed what in an account.
Services that process your data
- Supabase
- Database, authentication, file storage
- Vercel
- Hosting for the app
- Railway
- The research and media service
- Anthropic
- Writing, planning and fact-checking models
- OpenAI
- Article images
- ElevenLabs
- Podcast voices, including voices you record
- HeyGen
- Avatar presenter video, if you turn it on
- Creatomate
- Short video rendering
- DataForSEO and a SERP provider
- Search volumes, difficulty and result pages
- Pexels
- Stock photos
- A social publishing partner
- Holds your platform tokens and sends posts
- Resend
- Transactional email
- ScrapingBee
- Reading sites that block automated visitors
Found something?
Email hello@postiplex.com with the word security in the subject. We acknowledge within two business days, fix first and write it up after.
See one real week on your own site.
Connect your website and your channels. The first article is planned within the day.