This page says plainly how KnownBy handles your data today, including its limits. Where something depends on how the service is hosted, we say so rather than claim more than we can show.
1Your space is yours alone
Everything you create is tied to your account. Every request is checked against the signed-in account before anything is read or written, so another member cannot open your material. This check runs in the application on every request; it is not a separate isolation layer inside the database.
2What we can and cannot see
Running the service means the people who operate it can reach the database, as with any online tool. Our admin screens show account details, plan and billing, your profile (including the text of a CV if you uploaded one) and counts of what you have saved. They do not display your saved material, drafts or posts, and we do not go looking for them.
Messages you send us through the feedback button, a problem report or the contact form are read by the team.
3Passwords and encryption
Passwords are stored only as bcrypt hashes, never as plain text. The site is served over HTTPS, so data is encrypted on its way between your browser and our server. Your data is kept in a single database on the server that runs KnownBy; we do not add our own encryption at rest beyond what our hosting provides. Keys for outside services stay on the server and are masked in admin screens.
4The one honest limit
KnownBy is not end-to-end encrypted, and we will not pretend it is. To turn what you save into signals and drafts, the system has to read your content, and so do the AI models that write for you. We protect it by tying it to your account and by sending each model only what a request needs.
5The services behind KnownBy
A small set of outside services do specific jobs. Some are switched on only when a feature is in use.
- AI models: writing and analysis run on models from Anthropic and OpenAI, called directly through their APIs. The relevant parts of your profile, posts and saved material go with the request, and each provider's own terms govern how it handles them.
- Web search: to find news, trends and openings relevant to you, we send search questions to Perplexity, which searches the public web and returns sources. The questions can include the topics and roles you follow.
- Reading saved links (when switched on): when you save a web page by its address, we may use Firecrawl to fetch that public page and read its text. Only the address goes to Firecrawl.
- Reading LinkedIn: when you, or a visitor using the free read, paste a LinkedIn profile address, we use Apify to read that public profile and its recent public posts. Apify also gathers public job listings for the opportunities we show you. We never sign in to LinkedIn as you.
- Posting to LinkedIn (optional): if you connect LinkedIn, we use its official sign-in and publish only posts you approved.
- Payments (paid plans): card payments are handled by Stripe. Card details go to Stripe; we do not see or store them.
- Email (when switched on): account and notification emails are sent through Resend.
6What KnownBy learns
KnownBy learns your patterns: the themes you return to, how you write, and which suggestions you keep or turn down. What it learns is shown to you as a proposal you accept or reject; nothing changes how it writes for you until you say yes. We do not train AI models on your content, and your material is not used to write for anyone else.
7Your control
Export everything as a JSON file, or delete your account, at any time from Settings. Deleting your account removes your profile, saved material and content from the live database straight away and cancels any active subscription. If our hosting keeps backups, copies in them expire on the host's schedule.
Questions about your data? Write to us through the contact page or at support@knownby.me.