How V8 protects your accounts
Updated 12 November 2026
V8 holds something worth protecting: permission to publish on your business's behalf. This page says what stands in the way of anyone else using it, who has looked at that, and where the gaps are. It names the limits as well as the measures, because a page that only listed the measures would be an advertisement.
Nobody can see another workspace
Every row of your data is fenced to your workspace by the database itself rather than by our application code. The practical difference is the one that matters: a mistake in the product cannot show you someone else's posts or connected accounts, because the thing refusing is underneath the product rather than part of it.
That is tested rather than assumed. It has been checked from outside, as an unauthenticated caller with no session at all, and checked again with two real workspaces running side by side — the second could see none of the first's accounts, handles or posts.
We do not hold the keys to your social accounts
When you connect an account you authorise it on that platform's own consent screen. The access token that results goes to our publishing provider and stays there; what V8 stores is a reference to the account, not the means to post to it. So the most dangerous thing in the system is not in our database, and it is not something we could hand over, leak or be asked for.
The trade is worth stating plainly: publishing to your accounts depends on that provider's security as well as on ours. You can revoke V8's access at any time from the platform's own app or connected-account settings, without asking us, and that revocation takes effect immediately whatever we do.
How signing in works
There are two doors and you choose. The first is a link emailed to you, which expires and can be used once. The second is a password, which you set yourself from the Settings page — we never see it, and no email is involved in using it.
A password must be at least 10 characters and must contain a lowercase letter, a capital letter, a number and a symbol. Those rules are enforced by the sign-in server and not only by the form, so a password that the screen accepts is one the server will accept too. What is stored is a one-way hash: we could not tell you your own password, and neither could anyone who obtained the database.
The limit, stated rather than left out: your password is not checked against the public corpus of passwords exposed in other companies' breaches. That check requires a paid database tier V8 is not on. Until it is, the protection against a password already known to attackers is that you choose one nothing else uses — which is why the honest advice is to let your phone generate and save it rather than to invent one.
Where it runs, and how it travels
Your workspace, your posts and your uploaded images are stored in Germany, and the application that serves them runs in Frankfurt. Everything between your browser and us travels encrypted, and the stored data is encrypted where it sits. Every third party that touches any of it is named, with its purpose and its country, in the privacy notice.
What V8 will never do
- Publish without you. Nothing leaves V8 until you press publish or set a time yourself. There is no automatic posting, no filling of quiet days, and no replying to anyone in your name.
- Sell or share your data. It is not sold, not shared for advertising, and not used to build a profile of you or your clients.
- Train anything on your posts. The text you write is sent to the service that rewrites it for each platform, for that purpose and no other, and is not used to train models.
What has been checked, and when
A full security review of the product was carried out on 2 October 2026 and its findings acted on. It covered the workspace boundary described above, every privileged database operation the product can perform, whether any of them is reachable by a caller with no account, and whether the scheduler that publishes your timed posts proves who it is before it is obeyed. Changes since then are reviewed against the same standard, and the product carries several hundred automated checks that run before any change ships.
The second limit: no independent third-party penetration test has been commissioned. V8 is invitation-only — an address that has not been invited cannot create a workspace at all — so the people who can reach the inside of it are a known, short list. That is the reason, and it stops being a reason the day anyone can sign themselves up, which is the point at which an external test is the right thing to buy.
If you think something is wrong
Email hello@v8social.app and say what you saw. A suspected compromise of your own accounts is worth acting on before you write: disconnect V8 from the platform's own settings, which takes effect immediately, and change your password there. If something has gone wrong on our side that affects your information, you will be told what happened and what it touched — POPIA s22 requires that, and it is also simply the only acceptable way to behave about it.
Kayden Wright is the Information Officer and the person who answers this mailbox. Reports about the product itself are welcome from anyone, client or not.