Who this covers#
Keep is a project-management product for service-delivery teams, built and operated by Reveriext Inc. ("Reveriext", "we", "us"), a Delaware corporation in the United States. This policy describes what we collect when you visit hykeep.app, sign up, or use Keep — as a workspace member in the browser, or through an AI client connected on a member's behalf over MCP — and applies to every hykeep.app workspace.
Whose data it is. The content of a workspace belongs to the organization that owns the workspace. That organization decides what is put there and who can see it, and we handle it on its behalf, to run the service. If you are a member of someone else's workspace, questions about what is kept there are best put to that workspace's owner first. For your account, billing details and what this website collects, Reveriext Inc. is responsible.
Keep is for businesses and professionals. It is not directed to anyone under 18, and we do not knowingly collect personal information from children.
Keep never sells data#
Keep never sells data. Not your workspace's content, not member details, not usage records. We do not share it for advertising, and we do not use workspace content to train a model. What reaches another company is limited to the providers listed underSub-processors, which process it to run Keep, and to what the law requires of us, for example a valid court order.
What we collect and why#
What we collect, and what each is for:
- Workspace, project and thread content — requirements, modules, cycles, tasks, decisions, risks, notes, questions, updates, feedback and artifacts, their comments, attachments and version history, logged time, and conversations with Keep's in-product AI. This is the service itself: we store it so your team and your connected agents can read and change it.
- Account and member details — name, email and organization membership, synced from Clerk (our authentication provider) when someone signs up, signs in or is invited. We use them to sign you in, to apply your role, and to send email about your workspace.
- Billing details — the plan, the number of seats, the subscription's status and its dates, copied from Clerk Billing so Keep knows what a workspace may do. Card details are typed into Stripe's own fields on the payment form; they do not pass through Keep's servers and Keep does not store them.
- Sign-up attempts — when someone starts a workspace without an invitation, we record the attempt: the email address, a salted hash of the IP address (not the address itself), the account it was made from, and whether it was allowed. We keep these to enforce one free trial per person and to limit automated sign-ups.
- A log of what happened to a workspace — sign-up, the payment and subscription events Clerk sends us, deletion requests and administrative actions. We keep it so that a question about a charge, a suspension or a deletion can be answered.
- Usage telemetry — page views, feature usage and error events, used to keep the product working and to see what's actually used. This is operational telemetry, not a record of your work content.
- GitHub, once it is offered and a workspace connects it — the Keep GitHub App is not yet publicly available. When it is, a workspace admin will be able to install it on repositories they choose. Keep then stores references to work in those repositories so they can be shown on records: the repository's name, branch names, commit IDs and their subject lines, and pull request numbers, titles and status. Keep does not copy your source code.
- Feedback sent through the Feedback widget — a workspace can put Keep's feedback widget on its own website. When a visitor sends feedback there, Keep stores it for that workspace: the comment, the page's address and title, the element pointed at, a screenshot the visitor chose to send, the browser's type, language and window size, technical details of errors on the page, and the visitor's name and, if they give it, their email address. If a workspace turns on sign-in for the widget, a visitor who uses it gives an email address and a code we send to it, and sees their reports from any browser. The widget keeps a small entry in the visitor's browser so they can see their own reports again. That workspace decides how the feedback is used; a visitor who wants it removed should ask the website's owner.
- What you write to us — email you send tosupport@hykeep.app, billing@hykeep.app or hello@hykeep.app, kept so we can answer it.
This website#
Visiting hykeep.app without a workspace is covered here too:
- Prior Access Requests. Prior to the general availability of self-service registration, Reveriext Inc., a Delaware corporation ("Reveriext"), operated a request form on this website through which prospective users could submit a work email address. Where an individual submitted such a request, Reveriext retains the email address so provided, together with the date and time of submission and the browser user-agent string, for twelve months from the date of submission, after which Reveriext deletes it, and processed that information for the purposes of reviewing the request and transmitting the related invitation and sign-in correspondence. An individual may request earlier deletion of such information by written notice to Reveriext at the address set forth in this Policy.
- Website Analytics. Reveriext measures the public pages of this website by means of Cloudflare Web Analytics, which collects page views, referrer information and page performance data. Cloudflare Web Analytics does not set cookies and does not store any identifier in the visitor's browser.
Cookies. This website's own pages set no cookies. The Keep app, once you sign in, uses the cookies needed to keep you signed in, set by Clerk, and remembers preferences such as light or dark mode. Keep uses no advertising or cross-site tracking cookies.
Where it lives#
Every workspace is its own tenant on Cloudflare: its own D1 database for structured records and its own R2 bucket for files, reached at its own subdomain. No other customer's records sit in that database or that bucket. Account and membership details, billing details, sign-up attempts and the workspace log are held in Keep's own shared database, apart from workspace content.
The data region. The person who creates a workspace chooses where its database lives, from eight regions: US West, US East, Europe (West), Europe (East), Asia-Pacific, Oceania, Africa and the Middle East. Keep suggests the one nearest to them. The choice is given to Cloudflare as the location of the database. It covers the database; the workspace's files and its search index are placed by Cloudflare and are not tied to the region.
A workspace admin can ask for the region to be changed from the workspace's settings. We review the request and carry out the move; the workspace is read-only while it runs.
Other countries. Reveriext Inc. and the providers listed below operate in the United States and other countries, so your information can be processed outside the country you are in, whatever region you chose for the database. If your organization needs contractual terms for this, for example for personal data from the European Economic Area, the United Kingdom or Switzerland, write to us (below) before you put such data in Keep.
Who can see it#
Access inside a workspace follows its member roles — owner, manager, member, viewer and customer — each seeing a permission-checked slice of the same records; a customer-role member never sees commercial information such as rates or contract value. A person's own vault is private even from an owner or admin, enforced by the database, not just the interface.
Beyond your workspace's own members, Reveriext personnel can access workspace data only to provide support you've asked for, to investigate a reported problem, or to keep the service reliable and secure — never to read your work as a matter of course.
Security. Data is encrypted in transit, and at rest by our infrastructure provider. Access to production systems is limited to the people who need it. No system is perfectly secure. If we learn of a breach that affects your workspace's data, we tell the workspace's owners without undue delay, with what we know and what we are doing about it. To report a security problem, write tosecurity@hykeep.app.
Sub-processors#
We rely on a small number of providers to run Keep, each handling a specific slice:
- Cloudflare — hosting, the D1 databases, the R2 file storage, the search index, the AI models and the AI Gateway their calls pass through (below), the email Keep sends, the Turnstile check, and website analytics.
- Clerk — authentication, organization membership, and subscriptions and billing (Clerk Billing).
- Stripe — card payments, through Clerk Billing. The card fields on the payment form are Stripe's.
- Google Workspace — the mailboxes behindsupport@hykeep.app, billing@hykeep.app and hello@hykeep.app. It holds what you email us, not your workspace.
- Slack — alerts to our own team when something needs a person's attention, such as a failed payment or a refused sign-up. An alert names the workspace it is about. It carries no workspace content.
These providers are companies based in the United States that operate in many countries. When we add a provider that handles workspace content, we update this list before it starts. If your organization needs a data processing agreement with us, write to us (below).
AI in Keep. Keep's in-product AI runs on models served by Cloudflare Workers AI, and every call goes through Cloudflare AI Gateway. The models in use today are DeepSeek V4 Flash and GLM-5.3 Flash for chat, and BGE for search. Keep calls no other AI provider. A request carries the part of your workspace it is about to Cloudflare, to produce the answer.
The MCP connector#
Connecting an AI client (Claude, Cursor, VS Code, ChatGPT, or any other MCP client) to Keep is an OAuth grant, not an API key: you sign in, you approve the connection, and the client can then act only as far as your own role permits — every write it makes is attributed to you in the activity trail. A grant is visible, and revocable at any time, from the workspace's Connections page; revoking it takes effect immediately.
A client you connect is your own tool, not one of our sub-processors. What it reads from Keep is then handled by that client's provider, under your arrangement with them.
How long we keep it#
We keep a workspace's data for as long as the workspace exists. After that:
- A record you delete moves to the workspace's recycle bin, where it stays for 30 days before automatic removal; restoring it is one action within that window. The project's owner or a workspace admin can remove it for good sooner.
- A workspace its owner deletes is read-only for 30 days, and the owner can undo the deletion in that time. Then it is purged.
- A plan that is cancelled or ends: after the paid period ends the workspace is read-only for 30 days, then suspended. It is purged 90 days after the period ended.
- A workspace suspended for an unpaid invoiceis purged 90 days after the suspension.
Before a workspace is purged for an ended plan or an unpaid invoice, we email its owners and admins twice: 30 days before and 7 days before. Choosing a plan, or paying, before that date stops the purge and the workspace opens again as it was left.
A purge removes the workspace's database, its files, its search index and its address. It cannot be undone. Three things stay afterwards: the sign-up record (the email address and the salted IP hash), because one free trial per person has to be remembered; the log of what happened to the workspace; and what Clerk and Stripe hold about payments under their own terms, with anything we are legally required to keep (for example, billing records). Members' own accounts are not deleted with a workspace.
We keep the sign-up record, the workspace log, billing records and email you have sent us for as long as they are needed for the purposes described above, or for as long as the law requires. After a purge, copies may remain for a limited time in our infrastructure provider's backups before they expire.
Export and deletion#
You do both yourself, without asking us:
- Export. An owner or admin can download an export from the workspace's settings: a zip of every record, file and attachment. Export keeps working while a workspace is read-only, and owners and admins can still take one after it is suspended.
- Delete. The owner can delete the workspace from Settings → Workspace. Deleting it also cancels its subscription. The 30 days and the undo are described above.
For anything these two do not cover — a correction, a copy of what we hold about you, or removing your own account — write to us (below).
Your rights#
Depending on where you live, the law may give you the right to ask what personal information we hold about you, to get a copy of it, to have it corrected or deleted, and to object to or limit how it is used. Write to us (below) and we will answer within 30 days. We may need to confirm who you are first. We do not treat anyone differently for making a request.
If your request is about the content of a workspace that belongs to someone else, for example your employer or a company you work with, we pass it to that workspace's owner, who decides what is kept there. If you are not satisfied with our answer, you may also have the right to complain to the data protection authority where you live.
Changes to this policy#
We'll update the date at the top of this page when this policy changes, and post the new version here. We won't narrow your rights under an earlier version without telling you first.
Contact#
Keep is operated by Reveriext Inc. For a question about this policy, or to request access to, correction of, or deletion of your data, write to hello@hykeep.app. About a workspace you already have, write tosupport@hykeep.app.