Privacy Policy

Last updated: October 19, 2026

This is a draft policy for Krewbill and should be reviewed by counsel before launch. Krewbill is in early access, so where something is planned but not in place, this policy says so.

What we store

• Your account email address, and sign-in details handled by our authentication provider.
• A profile record with your user ID, email and the date you signed up.
• Workspaces, their members and roles, and invitations (the invited email address, the role and the space). Invitations expire after 14 days.
• Spaces: the name, the kind (for example client, project or course) and an optional description.
• Notes in a space: the title, text, type, tags, status, source, who created and approved them, and dates.
• Connection keys, stored only as one-way hashes with a short visible prefix, plus when each was last used and which spaces it may read.
• An audit log of who did what and when. It records the action and identifiers, not the content of notes.
• A rough use for each workspace, described in the next section.
• Which setup steps you have dismissed on a workspace. It holds your account and the workspace, and no content.
• Feedback you send from the feedback page: your three answers, the email address if you choose to give one, and the time. It is not linked to your account, and only the Krewbill owner can read it. Ask us to delete it by writing to hello@krewbill.com. We ask you not to put note content or personal data in it.

We do not store whole conversations with assistants, and we do not receive your files. Sample data from our earlier test connection remains in the database. It is made-up example content and is not customer data.

What we measure

• We do not ask you who you are or how you found us. We note a rough use for each workspace from the kind of space you create first (for example a client space or a course space) and store it on the workspace. We use it to understand who the product is for.
• We record activation events: when a workspace is created, when its first space is created, when its first connection key is created, when an assistant first reads from it, when a first note is approved, and whether an assistant has read from it in the last seven days. Each event stores only the workspace identifier, the name of the event and the time. It never stores note content, names, emails or what an assistant asked.
• We use these counts, grouped by that rough use, to decide what to build. They are viewed by the Krewbill owner only, as totals. They are not used for advertising and are not shared.
• Activation events are deleted when the workspace is deleted.
• To keep the service running we count server errors by type and time, for example how many connection errors happened in the last ten minutes. A count never holds the error message, a person, an address or any note content. If the count is high we email the Krewbill owner the type and the number.

Who can see it

• Within a workspace, people see only the spaces they have been given, with the role they were given. Owners and admins of a workspace can see every space in it.
• A connection key lets an assistant read the approved notes of the spaces that key was given. A workspace admin chooses whether the key may also suggest new notes. It can never approve them. Anyone holding a key can use it, so keep keys private and revoke any that leak.
• Krewbill staff do not read customer content as part of normal operation. We access it only where you ask us for support, where it is needed to keep the service secure, or where the law requires it.
• We do not sell your data or share it for marketing.

Models and training

We do not use your content to train models, and Krewbill makes no calls to a language model. Search by meaning is not switched on. If we switch it on, the text of approved notes and of search queries will be sent to an embedding service that returns a numeric representation, and we will update this policy and tell workspace owners first. The assistants you connect are run by their own providers, and their handling of what they read is governed by your agreement with them, not by this policy.

Services that handle data for us

• Supabase: database and sign-in.
• Vercel: hosting.
• Resend: sending sign-in and invitation emails.
• An embedding service: not in use. See above.

Cookies

We use only the cookies needed to keep you signed in. We do not use advertising or cross-site tracking cookies.

Retention and deletion

• You can export a space as Markdown or JSON at any time.
• An admin can delete a space, which removes the notes in it. An owner can delete a workspace, which removes everything in it: spaces, notes, keys, members, audit entries and activation events.
• Revoking a key stops it working immediately.
• You can delete your account from Settings. This removes your sign-in and your profile.
• You can also ask us to delete your data by writing to hello@krewbill.com from your account address.
• Our database provider may keep routine backups for a limited time, depending on our plan. Deleted data leaves those backups when they expire.
• If you are the only owner of a workspace, delete the workspace or make someone else an owner before you delete your account.

Minimum age

You must be at least 18 years old to use the service.

This is temporary pending legal review.

Changes and contact

We will say on this page when the policy changes. Questions, access requests and complaints can be sent to hello@krewbill.com.