Privacy policy
Last updated: 18 October 2026
This policy explains how Cresec (“we”, “us”) handles information about you when you use cresec.ai or contact us. If anything is unclear, email us at privacy@cresec.ai.
Pilot requests and optional details
You can request a pilot with a work or personal email and contact consent. You may also tell us your company, the AI assistant you use and the systems your routine touches, and afterwards your role, team size and what the routine does. We use these details to contact you about Cresec and review potential pilots. Downloading a resource does not subscribe you or submit a lead.
We retain the source, campaign and entry page supplied with a contact request to understand which content brings interest. Only when you accept analytics cookies do we associate the request with your browsing identifiers. A short-lived request token lets you add optional details after signup. We store its hash and submission counts to limit abuse. We record the verified operator identity and time when our team changes a follow-up stage; submitting details does not automatically qualify you or activate a product account.
Booking a meeting
“Book 30 minutes” links open our booking page on Cal.com, the scheduling service we use, in a new tab. What you enter there, such as your name, email address and notes, is collected by Cal.com and shared with us so we can arrange and hold the meeting. Cal.com handles it under its own terms and privacy policy, and we use it as described in this policy. On this site we only count clicks on those links, as part of the interactions described below; a click does not tell us whether you booked.
Connected accounts
When you use a tool governed by Cresec and connect an account to it, such as Gmail, we keep two things:
- the account connection, encrypted in Cresec’s credential vault;
- a signed record of each call made through Cresec: who made it, through which tool and version, the decision and the outcome, a hash of the request and a redacted form of it. We do not keep the full content of the request.
This data is stored in the United States. Cloudflare runs the service, delivers sign-in and service emails, and processes requests, including drafts, in transit; PlanetScale stores the data on Amazon Web Services in the us-east-1 region. Our other subprocessors for connected accounts are Google (the accounts you connect) and the model providers named below: Cloudflare Workers AI, Anthropic and TypeSafe.
When you ask Cresec to turn a written skill into a tool, we send the text you paste to a model to produce the tool’s definition: to Cloudflare Workers AI when your workspace uses Cresec’s model allowance, or to Anthropic under your workspace’s own key. Workers AI cannot be limited to one region, so these requests may be processed outside the United States. Data from your connected apps is not sent at that step. Leave customer data out of the skill text, and enter it in the tool’s fields when you run it.
When a tool has a step that chooses between options you declared, the text from the tool’s fields for that step is sent to Jev, a decision model run by TypeSafe (api.typesafe.ai), which returns the option it chose.
Retention is your decision, set in your agreement with Cresec. Unless agreed otherwise, we keep these records for up to one year.
You can disconnect an account at any time in the Cresec console, and also on Google’s third-party access page. Disconnecting in Cresec stops the connection from being used for any new call at once. It then deletes the stored connection from the vault and asks the provider to revoke it. If either step fails, the connection stays unusable through Cresec and we record the failure; to be sure the provider has revoked it, check Google’s page as well. The records of calls already made are kept as described above. When a workspace is closed, we delete its data within 30 days.
What we collect
We collect any information you choose to provide to us, and basic technical information that is sent automatically when you use the site. By providing information to us, you agree that we may collect, store and use it as described in this policy.
To understand how the site is used, we record interactions — which pages and sections are viewed and for how long, how far people scroll, and which links and buttons are used. We never store your IP address or record typed answers in interaction analytics. Unless you accept cookies (see below), these interactions are anonymous. If your browser sends a Global Privacy Control or Do Not Track signal, we don’t record them at all.
Cookies
We only set analytics cookies if you choose “Accept” in the cookie banner. You can change your choice at any time with “Cookie settings” at the bottom of every page.
cresec_vid— a random number that recognises your browser when you come back, so we can understand return visits. Kept for one year.cresec_sid— a random number that groups the pages of one visit. Ends after 30 minutes without activity.
Your choice itself is remembered in your browser’s local storage so we don’t ask again, and so are any display and accessibility settings you pick (theme, text size and so on). These stay on your device. If you send us a request while these cookies are accepted, your visits to the site are linked to it, so we can see how you used the site before getting in touch. If you reject cookies, we set no analytics identifiers and only record anonymous interactions page by page. Preferences you explicitly choose are separate from analytics cookies.
Routine check and demo
The routine check asks three yes-or-no questions about a routine. Your answers stay in the page’s memory and are not included in analytics or page URLs; it needs no contact details. The demo is a scripted walkthrough: nothing you do in it is sent anywhere, apart from the analytics described below.
With accepted analytics cookies, we record which result of the routine check was shown, and which demo preset was run, as fixed categories to understand which pages are useful. Without acceptance, only generic interaction counts are recorded. Global Privacy Control and Do Not Track disable this interaction tracking. Submitting a request does not subscribe you to a newsletter.
How we use it
We use this information to run and improve Cresec, to get in touch with you about it, and to keep the site secure and free from abuse. We don’t sell your information and we don’t use it for advertising.
Who else sees it
Your information is available to the Cresec team and to the service providers that host and run the site for us, who may only use it to provide their services. We may also share information if the law requires it, or with a company that takes over Cresec, which would have to follow this policy.
How long we keep it
We keep information only for as long as we need it for the purposes above, or as the law requires.
Your rights
You can ask us to show you the information we hold about you, correct it, delete it, or stop contacting you. Email privacy@cresec.ai. Depending on where you live, you may also have the right to complain to your local data protection authority.
Keeping it safe
We take reasonable steps to protect your information, though no system is perfectly secure.
Children
This site is not meant for anyone under 16.
Changes to this policy
If we change this policy, we’ll update it here and change the date at the top.
Contact
Questions or requests: privacy@cresec.ai.