Back to home

Privacy and Data Trust

CVs, AI processing, exports, deletion, and your rights wherever you live

What PersonalBrandOS keeps about you, why, when AI reads it, and how to take it with you or delete it. We would rather give you clear controls and plain limits than broad legal claims, so everything on this page describes what the app actually does today.

Open Data Controls

You can see what we keep and why. Each kind of information is listed below, with what it is for and when AI reads it.

AI only sees what a task needs. Each feature sends the parts of your profile it uses, such as your CV for a job match or your goals for the weekly coach note on your dashboard.

You can take everything with you or leave. Export it all as a ZIP, or delete your account, from Settings > Data & Privacy. Deletion happens 30 days after you ask, and you can cancel it until then.

We stay away from sensitive details. We never ask for your ID number, race, health or disability, and the Z83 guide does not collect your form details at all.

Wherever you live

Using PersonalBrandOS outside South Africa

One standard for everyone

PersonalBrandOS is run from South Africa, so South Africa's Protection of Personal Information Act (POPIA) governs how we handle your information. We apply it the same way to every user, wherever you live. If the law in your country gives you more rights than this page describes, you have those too.

Where your information goes

Your account and everything you save are stored in a database in London, United Kingdom, run by Supabase. The app itself runs on Vercel. When you use an AI feature, the text that feature needs is sent through OpenRouter to the AI model provider for that task. Emails are sent through Resend, background jobs run on Inngest, and payments go through PayFast in South Africa. Several of these providers are based in the United States, so your information is handled outside your own country and outside South Africa.

Your rights, wherever you are

You can export or delete everything from Settings, and correct anything on the page where you entered it. The rights listed on this page apply to you whether you live in South Africa, Botswana, Kenya or anywhere else.

If something is wrong

Email us first and we will put it right. If you are not satisfied, you can complain to South Africa's Information Regulator, or to the data protection authority in your own country.

Questions or requests: support@personalbrandos.co.za

Data map

CV and Resume Files

Uploaded CVs, parsed text, extracted roles, education, skills, certifications, and projects.

Purpose: Build the user profile, improve job matching, and avoid asking users to repeat career history.

AI use: Sent to AI only when the user asks for parsing, scoring, matching, or generation that needs resume context.

Control: Users can delete individual resumes from Resume Vault and request a full account export or deletion.

Profile and Goals

Name, headline, location, target roles, career goals, blockers, next actions, and skills to build.

Purpose: Personalise guidance so recommendations are based on the user's desired career outcome.

AI use: Used as prompt context for scoring, content, Smart Suggest, job matching, interview prep, and weekly planning.

Control: Users can edit profile details and goals from Profile, Dashboard, and onboarding review screens.

Proof Vault and Projects

Wins, projects, metrics, story angles, proof links, and selected public proof-profile items.

Purpose: Turn real evidence into CV bullets, LinkedIn content, interview stories, and application material.

AI use: Used when the output needs evidence. Hidden or unselected proof is not included in public proof profiles.

Control: Users choose what proof to save, update, delete, and publish to a shareable profile.

AI Prompts and Generated Content

Prompts, generated drafts, calendar plans, comments, interview reports, and usage metadata.

Purpose: Save useful outputs, preserve credit history, and let users continue work across devices.

AI use: Generated outputs are returned by the selected AI provider and stored only when the workflow saves them.

Control: Users can delete generated Content Vault items and request a full export or account deletion.

Voice and Style Samples

Optional voice/style samples and derived voice-profile traits used to make content sound more personal.

Purpose: Improve tone matching for posts, interview prep, and career content.

AI use: Used only for voice analysis or generation flows where the user asks for personal tone matching.

Control: Users can reset voice profile data from Settings and avoid voice workflows entirely.

Account, Credits, and Activity

Authentication ID, email, subscription status, credit usage, onboarding events, and app activity records.

Purpose: Operate the account, prevent surprise credit use, and understand where onboarding needs improvement.

AI use: Usage metadata is not needed for normal AI generation, except for routing and cost-control decisions.

Control: Users can request export, schedule deletion, and keep billing-provider choices separate until decided.

Waitlist Email

The email address given when joining the pre-launch waitlist, when it was added, and whether the person asked to test before launch.

Purpose: Tell the person when PersonalBrandOS opens, and invite them to test early if they asked to. It is not used for anything else.

AI use: Never sent to AI.

Control: Anyone on the waitlist can ask to be removed by emailing support@personalbrandos.co.za. It is not linked to any account.

Browser Extension (PersonalBrandOS Copilot)

The visible text of a job posting when you click the extension, the text you highlight to save or to reply to in Comment Crafter, or the name and profile link of a LinkedIn profile you are viewing when you click Add to Target List, plus the address of that page.

Purpose: Carry what you captured into PersonalBrandOS so you do not have to copy and paste it. The extension reads nothing until you click it or right-click your own selection. On a profile it reads only the page title and main heading, for the name.

AI use: The extension sends nothing to any server, AI or otherwise. It opens a PersonalBrandOS page with the text filled in, and nothing is saved or analysed until you click the button on that page yourself.

Control: Captured text stays in your browser until the PersonalBrandOS page picks it up, and anything older than two minutes is discarded instead of used. Removing the extension removes it all.

Updated 7 October 2026

If you are not a PersonalBrandOS user

Our users write about, hear from and are visited by people who never signed up. This is what we hold about you in each case, who can see it, and how to have it removed. PersonalBrandOS is run by Disele Mphafe t/a PersonalBrandOS. For any of these, email support@personalbrandos.co.za, say which user's page or which request it concerns, and we will act on it.

You sent an enquiry through a freelancer's page, a speaking invitation through a creator's speaker page or a partnership proposal through a business's partner page; a freelancer or a business owner keeps you in their client, customer, investor or partner list; or a creator tracks a talk, podcast or panel you invited them to or they pitched to you

What we hold:
If you used the form on their page: the name, email address and message you typed (and, for a speaking invitation, the event and its date; for a partnership proposal, your company), and when you sent it. No IP address or device details are kept with it. If they added you themselves: what they typed, such as your name or your event's name, what the work or talk is, a link or email, notes, a value or fee, an event date and follow-up dates, and any proposal they write for you.
Why:
So they can reply and keep track of the work or the talk. It appears in their private Clients, Customers, Investors, Partners or Speaking list.
Who sees it:
Only that freelancer. It is never shown on a public page. If they turned on follow-up reminders, your name and a short summary of the work can appear in a reminder email we send them through our email provider (Resend).
AI:
Only when the freelancer or business writes a proposal for you, or a customer story about finished work: the details they see and can edit before sending (what the work is, what you needed, what was done and the result, with you described rather than named) are sent to the AI provider to draft it. Your name, email address and link are never sent. Nothing else about you is sent to any AI provider.
Kept:
Until the freelancer deletes it, resets their data, or closes their account.
Your choice:
Ask the freelancer to delete it, or email us and we will deal with the request.

You wrote a testimonial for a user

What we hold:
Your name, job title and company, the words you wrote, a contact detail if you gave one, the places you agreed it may appear, and when you agreed. If the user copied in a recommendation you wrote on LinkedIn, it is kept unused, shown nowhere and never sent to an AI provider, until you confirm it through the link they send you; if you ignore the link, it stays unused until they delete it.
Why:
So the user can show your words in the places you agreed to: their profile and CV, their LinkedIn posts, or their public page.
Who sees it:
The user who asked you. In public, only the places you ticked, shown with your name, title and company. Your contact detail is never shown publicly.
AI:
Only if you ticked LinkedIn posts. Then, when the user drafts content, bios or positioning with AI, your words and your name and role can be included as evidence in what is sent to the AI provider. If you ticked only a CV or a public page, your words are never sent to an AI provider.
Kept:
Until you withdraw it or the user deletes it. Withdrawing erases your words and details and keeps only a record that a testimonial was withdrawn.
Your choice:
Reply to the message that asked you for it, or email us, to have it withdrawn.

A user added you to their Target List, the people whose posts they plan to comment on

What we hold:
Your name and a link to your profile, which the user either typed or captured with our browser extension while viewing your LinkedIn profile, plus a one-line note on why you matter to them and the dates they logged engaging with your posts or messaging you. The extension takes only your name and profile link, and only when the user clicks it. Nothing else is collected from LinkedIn or anywhere else, and nothing is collected automatically.
Why:
Reminding the user to engage with your public posts, and suggesting when to send you a message.
Who sees it:
Only that user. It is never shown on a public page.
AI:
If the user asks for help writing a message to you, your first name, their note about you and anything they type about your posts are sent to the AI provider to draft it. Your full name and profile link are not.
Kept:
Until the user deletes you from the list, resets their data, or closes their account.
Your choice:
Ask the user to remove you, or email us.

A user saved one of your public posts

What we hold:
The text of the post and the link to it, as the user saved it. No separate author details are stored.
Why:
So the user can come back to a post that inspired them.
Who sees it:
Only that user.
AI:
Never used as facts about the user. The text is sent to the AI provider only if the user chooses to write their own post based on it.
Kept:
Until the user deletes it or closes their account.
Your choice:
Ask the user to delete it, or email us.

You visited a user's public page or speaker one-sheet

What we hold:
A daily count of visits and of clicks on each button or link on that page. No name, IP address, cookie or device detail is stored with a count. Your IP address is used for a moment in our server's memory to stop abuse, and is not saved.
Why:
So the page owner can tell whether their page is working, for example whether anyone clicks their main button.
Who sees it:
The page owner sees the totals.
AI:
Never sent to AI.
Kept:
While the page owner's account exists.
Your choice:
Nothing identifies you, so there is nothing to remove. These pages set no tracking cookies and load no analytics or advertising scripts.

User rights

For every user, wherever you live:

Know what personal information is collected and why.

Access a record or description of personal information held by the app.

Request correction or deletion of inaccurate, excessive, outdated, incomplete, misleading, or unlawfully obtained information.

Object to processing where the law allows it.

Be notified when there are reasonable grounds to believe personal information was accessed or acquired by an unauthorised person.

AI boundaries

Use the minimum career context needed for the task.

Do not route sensitive Z83 personal fields through AI providers in the current product scope.

Do not use private user content to train public AI models.

Keep provider/model routing server-side so users are not asked to make privacy decisions through raw model names.

Show credit cost and generated-output persistence clearly before paid AI work runs.

Not collected now

Do not store ID or passport numbers unless a future reviewed workflow truly requires it.

Do not ask for race, disability, health, criminal-record, disciplinary, or equity information inside reusable prompts.

Do not send WhatsApp messages automatically or store WhatsApp phone numbers before explicit opt-in.

Do not publish proof-profile items unless the user selects them for sharing.

Do not treat generated AI outputs as final application material without user review.

Sources and next work

Add production-ready privacy policy and PAIA/Information Officer details before launch.

Add a saved consent ledger for WhatsApp opt-in, provider routing, public proof profiles, and future Z83 helpers.

Add data-retention settings for stale resumes, exports, voice samples, and unpublished proof.

Add an admin privacy-requests queue so exports, correction requests, and deletion events are auditable.