Your work deserves
a considered home.
Clear boundaries. Careful handling. Honest answers.
Here’s how we look after the things you bring to Inklyst.
This page describes the product today. Inklyst is not SOC 2 or ISO certified, and has not completed a formal external penetration test.
Shared with intention.
Your organization and workspaces define the boundaries around your content.
Access to workspace content is checked on the server against the person making the request, their membership, and the resource they want to open. Roles determine what people can see and change.
Being signed in does not grant access to another organization’s content. These checks are enforced in the backend, alongside the product’s sharing controls.
A familiar way in.
A clear way out.
Sign in with your email and password, a code we email you, or your Google, Microsoft, GitHub, or Apple account. Passwords are hashed before storage, and sessions use HTTP-only cookies.
Signing out ends the session in the browser you’re using. If you forget your password, ask for a reset from the sign-in page. We email you a link; choosing a new password signs out your existing sessions.
Your files, notes, and conversations are the reason this space exists. Here are the details behind it.
Uploaded files, web captures, notes, transcripts, citations, conversations, and the account information needed to run your workspace, including your email, display name, and memberships.
We do not sell customer content or use it to train our own models. Our privacy policy explains the AI providers involved, their handling of content, and the dated changes to their settings.
Questions deserve answers.
Reports deserve attention.
Evaluating Inklyst, or found something we should look into?
Send the details privately to our security contact.
Please keep vulnerability reports out of public issues
so we can coordinate a fix with you.