Privacy policy

Contexel is a shared memory for AI apps. You save things, and your AI apps look them up later, so we hold what you save. This page explains what we collect, why, who else handles it, how long we keep it, and what you can do about it. "We" and "us" mean Technoledgy LLC, a California limited liability company doing business as Contexel. Using Contexel is also covered by our Terms of Service.

What we collect

Your account

We use WorkOS to sign you in. You can sign in with an email address, Google or GitHub. WorkOS confirms who you are and tells us your user ID, your organization ID, your email address and your name.

On our servers we keep your user ID and organization ID, the access you have to each workspace, which workspaces you own, and which version of our Terms of Service was in effect when you signed in to the console, with the date. For each organization you belong to, we also keep your first name and the first letter of your last name, as WorkOS gives them, so Contexel can say who saved a memory (see "Who saved a memory" below). We don't keep your full last name or your email in our database.

We also keep your time zone, which the console reads from your browser and you can change under Settings, so dates like "tomorrow" in your notes and "what changed since Friday" are worked out in your own time. When you ask an AI app to catch you up, we keep the time of that catch-up for each workspace and each app or access key, so the next one can start from there. We delete these when you revoke that app or key, and when you delete your account.

In your browser, a cookie holds your name and email so the console can show who is signed in, and the sign-in screen remembers the last email you typed (see "Cookies and browser storage").

One exception: when you invite someone to a workspace, we store that person's email address with the invitation, so the workspace owner can see who has access.

When you sign in

WorkOS records when you sign in, your IP address and your browser, to keep your account secure.

When you sign in to the console, our servers also record that sign-in: your user ID, your organization ID, the time, how you signed in (for example with a password, Google or your company's single sign-on), and which version of our Terms of Service was in effect. We use it to ask you to sign in again before a sensitive action, and to offer a password change only to people who sign in with a password. It expires after 30 days, the longest a console sign-in lasts, and expired records are removed as new sign-ins arrive. It is filed under a scrambled form of your sign-in session's ID, never the ID itself.

Where your sign-up came from

Some links to our website carry a campaign tag: the ref, utm_source, utm_medium or utm_campaign part of the address, which says, for example, that the link was in our newsletter.

• What we keep: if your link had a tag, we keep it with your new organization, once, when the organization is created. Each tag is one short word of letters, digits, dots, dashes or underscores, so it cannot hold an email address.
• Nothing else: not your IP address, not the page you came from, and not your browser. (Like any request, the visit is in the CloudFront access logs below, for 30 days.)
• In your browser: our public pages pass the tag to their sign-up buttons and store nothing. The sign-up page keeps it in that tab's storage, not a cookie, until you finish signing in.
• What it is for: only to count which links bring people who sign up, connect an AI app, save a memory and choose a plan.

Access tokens

If you create an access token to connect an app, we keep the name you give it and the access it grants. We store only a scrambled form of the token itself (a one-way hash), never the token.

What you save

• Memories: the notes, decisions and documents you or your AI apps save, stored in your workspace in our database, with a version history.
• Notes waiting to be filed: quick notes your AI app captures. They are later turned into tidy memories, and the original notes stay in the workspace.
• Suggested changes: edits waiting for someone to approve them, and a record of past ones.
• Where each memory came from: each saved memory records which account or access token saved it, and when.
• A search index built from your memories, so search is fast.
• Feedback from your AI apps: which results helped, which didn't, and words your AI said were missing. We use this to show you searches that found nothing.
• Copies of GitHub repositories, only if you connect one.

An activity log

We keep an activity log that shows if anyone has altered it. It records who did what and when: saves, approvals, exports, access changes and settings changes, by account and token IDs, workspace names, counts and times. It never records the text of your memories, your searches or your notes.

Paid plans and free trials

For each organization, we keep: its Stripe customer and subscription IDs, its plan, whether its payments are up to date, how many seats it pays for, when its free trial started and ends, whether we gave it the Founding plan and when, and the user ID of the person who created the organization (who keeps their own private workspace on the Free plan if a trial or plan ends unpaid). We never see or store card numbers: Stripe handles payment details directly. The billing address, and the business name and tax ID if you give them, which Stripe uses to work out sales tax, stay with Stripe; we don't copy them to our servers.

When you contact us

If you use the contact form, we get your name, your email, who Contexel is for, and your message. Formspree delivers the form to us and also sees your IP address, which it uses to filter spam. We use what you send only to reply to you, and we delete it 12 months after our conversation ends.

Requests to our servers

Our servers run on Amazon Web Services, behind its CloudFront network.

• CloudFront's access log: CloudFront keeps an access log of every request to contexel.ai: your IP address, the time, the address you asked for including the part after the question mark, the site that sent you and your browser type. It never logs cookies. We keep these logs for 30 days to investigate attacks and outages, and then they are deleted. The one-time sign-in code in the address you come back to after signing in works only once and expires within minutes, so the copy in the log cannot be used to sign in.
• Our request log: our own servers write a line for each console, sign-in and AI app request, and for any request that fails: a random reference number, the address without the part after the question mark, the result, and your user, organization and token IDs. It never holds your IP address, your email, the text you save or your searches. We keep these logs for 30 days.
• Performance statistics: for an AI app request, that line also says how it went, in numbers and short labels only: which Contexel tool it used, whether it worked, the kind of error, how long it took, and counts such as how many memories came back. It never includes what you asked, what came back or what you saved. To see how Contexel performs over time, we keep a trimmed copy of these AI app lines for 13 months: only those numbers and labels and the request's reference, with your user and organization IDs replaced by scrambled codes. We may also send that copy to Better Stack, which stores it in the United States.
• The reference code: if something fails on our side, the console or your AI app shows you the request's reference, which starts with the letter r. Quote it when you contact us so we can find that request. It is a random code and says nothing about you.

Error reports

When something breaks on our servers, we send an error report to Better Stack, which stores it in the United States. It says what kind of error happened and where in our code, with a short description. Before anything is sent, we remove email addresses, access tokens, file and folder names, workspace and repository names, and the text of your memories and notes, and we replace workspace names and IDs in the failing web address with placeholders. Your organization appears only as a scrambled code. Reports never include request bodies, cookies, sign-in headers, your IP address, your browser details or query strings.

Visits to our website

Our public pages have no advertising trackers and set no cookies. To count visits we use Plausible Analytics. When you open one of our public pages, your browser loads Plausible's script from plausible.io. Plausible stores nothing on your device and does not keep your IP address. It turns your IP address and browser type into a code that changes every 24 hours, so it can count visitors for one day without knowing who they are. We see totals only, such as how many people read a page, which site sent them, and how many clicked through to sign up. The console, where you sign in, does not load Plausible. Everything else on our pages, including fonts, comes from our own servers. Contexel's own code does not record your IP address; the CloudFront access logs described above do.

How we use it

• To run the service: store what you save, search it, and show it to you and the people you share a workspace with.
• To sign you in and check what each person and app is allowed to see and change.
• To file your notes into lasting memories (see AI distillation below).
• To say who saved a memory, by first name, to other members of your organization (see "Who saved a memory" below).
• To keep the service secure and working: the activity log and error reports help us spot misuse and fix problems.
• To tell admins about their plan and free trial: we email your organization's admins before its free trial ends, and when its trial ends with no plan chosen, its paid plan ends, or its plan goes unpaid. If its shared workspaces are paused, we also email them 30 and 7 days before we delete the paused shared workspaces and the data of members other than the creator. We look up their email addresses from WorkOS when we send, and don't keep them.
• To count visits to our public pages, as totals only.
• To see which links bring sign-ups: we count new organizations by the campaign tag their sign-up link carried, if any, and how many of them go on to connect an AI app, save a memory and choose a plan.

Search runs entirely on our own servers, including the part that works out what your words mean. Your searches are not sent to an AI company.

We don't sell your data, we don't use it for advertising, and we don't use it to train AI models.

Cookies and browser storage

Our public pages set no cookies. The console uses the cookies and browser storage below. Each one is needed to sign you in, keep your account safe, or remember a setting you chose. None is used for advertising or to follow you across other sites, so we don't ask for cookie consent.

In your browser's storage the console keeps:

• The last email you typed on the sign-in screen, until you click Change or sign out.
• Whether you turned on Advanced settings.
• The last numbers you saw under At a glance (counts, a date and the Health word, never your memories), so they show at once next time, until you sign out.
• Three short-lived items that last only while one tab is open.
• A sign-up link's campaign tag, if you arrived through one, until you finish signing in, sign out or close the tab.

Signing out clears the cookies, the remembered email, the remembered numbers and any campaign tag. You stay signed in until you sign out, or for up to 30 days after your last visit.

Who else handles your data

We use a small number of other companies to run Contexel. Each gets only what it needs.

• Amazon Web Services runs our servers and stores all Contexel data, in the United States (the Oregon region). It also stores our encrypted backups, in a separate account in the United States. It also sends our emails to organization admins, such as the notices about your free trial and about paid plans. For those it receives each admin's email address and the text of the email, which never includes anything you saved, and it keeps a list of addresses that bounced or marked an email as spam, so we stop emailing them.
• Fly.io ran our servers, in the United States, until we moved to Amazon Web Services in September 2026. We no longer use Fly.io for anything, and our daily check that the newest encrypted backup can be restored now runs on Amazon Web Services.
• WorkOS handles sign-in, keeps your sign-in account (your email, name and organization membership) and sends sign-in and invitation emails for us. It uses Cloudflare to protect the sign-in page. If you sign in with Google or GitHub, that company tells WorkOS who you are.
• Anthropic, the maker of Claude, is used only for AI distillation (below).
• Better Stack receives error reports and, if we turn it on, statistics about AI app requests (never their content), both stored in the United States. It also checks from outside that Contexel is up.
• Stripe handles payments and sales tax for paid plans. When an organization admin starts a purchase, Stripe receives that admin's email address and your organization's IDs. The card details go straight to Stripe, and so do the billing address, and the business name and tax ID if you give them, which Stripe uses to work out the tax. Stripe keeps its own payment records, as the law requires.
• Sentry received error reports until we moved them to Better Stack, and keeps those older reports until we close our Sentry account.
• GitHub is used only if you connect a repository. We read it with read-only access.
• Formspree delivers messages from our contact form.
• Plausible Analytics counts visits. It uses no cookies and does not keep your IP address. Its data is stored in the European Union.

Each of these companies works for us under a contract that limits what it can do with your information.

Everyone you give access to a workspace can read what's in it. We may also disclose information if the law requires it, or to a buyer if the business is sold, under the same promises as this policy.

Why we're allowed to use it

If you are in the European Economic Area or the UK, the law asks us to explain why we are allowed to use your information.

• Our agreement with you: we use your information to run your account and the service you signed up for.
• Legitimate interests: we use it to keep the service secure, keep the activity log, fix errors, count visits and see which links bring sign-ups, because we have a legitimate interest in running a safe, working service, and these uses have little effect on you. We use your contact form message to reply to you, for the same reason.
• The law: we also keep information when the law requires it.

We also tell members of your organization who saved a memory, by first name (see "Who saved a memory"), because an organization has a legitimate interest in knowing where its shared memories came from. Workspace owners and organization admins can turn names off for a workspace, and you can ask us to hide your name.

You can object to any use based on legitimate interests by emailing privacy@contexel.ai.

When your company uses Contexel

If you use Contexel through your organization, your organization decides what goes into its workspaces. For that content we work on your organization's instructions as its service provider, called a "processor" in European law. The companies in "Who else handles your data" are the only ones that handle that content for us. Contact us for our data processing agreement.

Your organization's admins can open any of its workspaces, including a member's private workspace. Each time an admin opens someone's private workspace, it is recorded in the activity log, and the member sees a notice in the console saying who opened it and when.

If a memory mentions you and you are not a Contexel user, contact the organization that saved it, or email privacy@contexel.ai and we will pass your request on.

Who saved a memory

When an AI app looks up a memory for a member of your organization, Contexel can tell it who saved that memory, by first name. When two members share a first name, it adds the first letter of the last name.

• Only inside your organization. A name is given only when the person asking is a current member of the same organization. It is never given to people outside it, such as someone invited to a single workspace, never to an access token that is not a current member's own, and never with an email address.
• The AI app keeps what it is told. The name goes to the AI app that asked, as part of its answer, and that app keeps it under its own privacy policy, like the rest of the answer.
• On unless someone turns it off. Workspace owners and organization admins can turn names off for a workspace, in that workspace's settings in the console. Then nobody is named there: what was saved reads as saved by "a teammate", or "a family member" in a Family workspace. A private workspace has no such setting: only its owner saves there.
• You can ask us to hide your name. Email privacy@contexel.ai. We stop giving your name in that organization and clear it from our servers.
• When someone leaves. When a member leaves the organization, we clear their name, and in a workspace where names are on, what they saved reads as saved by "a former teammate", or "a former family member" in a Family workspace.

Questions to the person who saved a memory

When a memory looks out of date, you can ask your AI app to send one short question to the member of your organization who saved it. Your AI app shows you the exact words first, and nothing is sent until you say yes.

• Who can ask. Current members of your organization who can make or suggest changes in that workspace. Someone who can only view it cannot ask, and neither can someone invited from outside your organization or an access token that is not a current member's own.
• Who is asked. Only the person who saved the memory, and only while they are a current member who can still change that workspace. Nobody is asked about a memory in a private workspace, a memory copied from GitHub, a memory whose saver we don't know, or your own memory.
• You are named. The person you ask sees your question, the memory it is about, the workspace, the date, and your first name (with the first letter of your last name when two members share a first name), under the same rules as "Who saved a memory" above. Where a workspace has names turned off, you show as "a teammate", or "a family member" in a Family workspace. There are no anonymous questions. When they answer, you see their answer and their name the same way.
• Nobody else sees it. Only the person who asked and the person who saved the memory see a question and its answer. If the answer fixes the memory, the fix is saved with the saver's own access, and the memory's history says it was fixed after a question without saying who asked. The person you ask learns nothing else about you: not what else you looked up or asked your AI.
• Health and child details. If a question, or a fix given in answer, looks like it contains a health detail or a detail about a child, your AI app (or the console) asks you to confirm before it is sent or saved.
• Where it is shown. In the AI app of whoever asks for their Contexel suggestions, and in the console under "Questions for you". The AI app keeps what it is shown, under its own privacy policy, like the rest of its answer. We don't email anyone about a question.
• How long we keep it. A question nobody answers closes after 30 days. A question and its answer are deleted 30 days after it closes. If the person who asked leaves the organization, their questions are hidden at once and erased within about 6 hours. If the person who was asked leaves, their open questions close and the asker is told. Questions are encrypted like your memories and are not included in our backups, so no copy outlives these limits.
• What our records keep. The activity log records that a question was asked, answered or erased, by account and memory IDs only, never the words. Our server logs and error reports never include a question, an answer or a name. To tell you a question or an answer is waiting, we keep a small record with the account IDs of the two people, the workspace and the times, and no text. It is deleted with the question, with either person's account, or with your organization.
• You can turn it off. In the console's "Questions for you" box, tick "Don't let teammates ask me about memories I saved". After that nobody can send you a new question, and anyone who tries is told you aren't taking questions right now. Questions already waiting stay until you answer them or they close. Untick it to take questions again.

AI distillation

AI distillation turns the quick notes your AI apps capture into tidy, searchable memories. When it runs with an outside provider, the text of the notes being filed is sent to that provider, which returns a draft memory. Where it is on, it runs shortly after new notes arrive, or when someone asks for it.

• Only where we turned it on. AI distillation is available only to organizations Contexel has turned it on for. Everywhere else it is off and does not appear in the console: notes are filed by simple rules on our own servers, as your AI app wrote them, and nothing is sent to Anthropic or anywhere else.
• The default where it is available: it is on for every workspace until its owner turns it off.
• You can see it. Where it is available, each workspace's settings in the console show whether AI distillation is on and which service it uses.
• You can turn it off. A workspace owner (or an organization admin) can turn it off in that workspace's settings. When it is off, notes are filed by the same simple rules and nothing is sent anywhere. Those rules do a plainer job: each note is kept word for word, and a note that only repeats another is folded into it.
• Not used for training. Anthropic doesn't use the notes we send to train its models: our account with it is set so it can't.
• It is logged. Every time notes are sent, the activity log records that it happened, how many notes went, and which model. It never records the notes.

Encryption and who can read your data

Your data travels to our servers over an encrypted connection (HTTPS).

Encrypted, with a key we manage. Every organization's memories, notes and search index are encrypted at rest with a key dedicated to that organization, from the moment it is created. There is nothing to turn on. We keep that key, protected by Amazon Web Services' key management service, so search can run for you. That means we can technically access your data, and we'd rather tell you than hide it.

Kept separate. Each organization's data is kept apart from every other customer's, both in our database and by its own encryption key: one organization's key can never read another's. Everything else we store, including copies of GitHub repositories you connect, is protected by our database's encryption.

Passwords, secrets and sensitive information

When your AI app saves a note, suggests a change, or when we copy a connected GitHub repository, Contexel first looks for common secrets and replaces them with a marker. It catches private key blocks, AWS access keys, GitHub and Slack tokens, JSON web tokens, passwords inside connection strings and web addresses, and secret-looking values written next to names like password, api_key, token or secret.

This is a safety net, not a guarantee. It won't catch every secret, and it does not remove personal details such as names, phone numbers or health information. Please don't save passwords or other credentials in Contexel.

Contexel is not designed for protected health information (such as patient records) or payment card data. Don't store either in it.

How long we keep it

• What you save: for as long as the workspace exists. Notes stay in the workspace after they are filed.
• Deleting a workspace: a workspace owner can delete it in the console. Deleting a workspace archives it. Archived workspaces are kept until someone chooses Delete forever, which removes it for good. Archiving removes everyone's access and the search index at once, and keeps its memories in your organization's history so it can be restored. Delete forever erases its memories, including every earlier version, from that history. Backup copies are gone within 35 days after that.
• Deleting your account: in the console, open Settings, then Account, then Delete my account at the bottom.
  • What goes: your sign-in account at WorkOS, your private workspace, your access tokens, your access to shared workspaces, and your sign-in and Terms records on our servers. You are signed out. We keep your user ID for one more day so that any sign-in still open elsewhere stops working, then delete it.
  • What stays: memories you saved in shared workspaces stay with your organization, and the activity log keeps its records as described below.
  • If you are the only admin: make someone else an admin first.
  • If you are the only person in your organization: Delete my account deletes the organization with your account, after the same 7 days as deleting the organization (below).
  • If you also belong to another organization: email us at privacy@contexel.ai and we will delete your account everywhere, and confirm when it is done. We aim to finish within 30 days.
• Deleting your organization: an organization admin can delete it in the console: the People tab, then the delete link at the bottom (Delete household, Delete team or Delete organization). For an organization that is just you, Delete my account does it.
  • The first 7 days: nothing is deleted. Everyone can read and download their memories but not change them, and any admin can cancel. Your plan stops renewing and ends when the 7 days are up.
  • Then: we delete every workspace, memory, member's access and billing record of the organization from our servers, and the organization and anyone left in no other organization from WorkOS. Backup copies are gone within 35 days after that.
• Backups: we keep encrypted backups in a separate Amazon Web Services account in the United States. Each backup is locked for 30 days after it is made, and nobody, including us, can remove it in that time. Deleted data is gone from backups within 35 days. Our database also keeps point-in-time copies for 7 days, and the stopped copy at Fly.io from before our move to Amazon Web Services is deleted two weeks after the move. While any of these copies still holds deleted data, including a deleted account, we can bring it back, but only when you ask us to: we never restore a deleted account on our own, and every restore is recorded in our activity log.
• Paused shared workspaces: when a free trial or a paid plan ends and no new plan is chosen, the organization moves to the Free plan. The creator's private workspace keeps working; shared workspaces pause, and other members lose access. Shared workspaces that stay paused for 12 months, and the data of members other than the creator, are deleted, after we email the organization's admins 30 and 7 days before. The creator's private workspace on the Free plan is not deleted while the creator is a member. The 12 months never start before September 30, 2026. Backup copies are gone within 35 days after that.
• Plan and trial records: kept while your organization exists, and deleted with it. Stripe keeps its own payment records for as long as tax and accounting laws require.
• Activity log: kept for 6 years, including after a workspace is deleted, because it is our security record. It holds IDs, counts and times, never your content.
• Which terms version you signed in under: kept while your account exists, and in the activity log for 6 years, because it is our record of our agreement with you.
• Feedback from your AI apps: kept until your account's data is deleted.
• Your first name and last initial (who saved a memory): kept while you are a member of the organization. Cleared when you leave it or ask us to hide your name, and deleted with your account or with the organization.
• Questions to the person who saved a memory: an unanswered question closes after 30 days, and a question and its answer are deleted 30 days after it closes, or within about 6 hours of its asker leaving the organization. They are not in our backups. The activity log keeps only IDs, for 6 years.
• Sign-in cookies: the session cookie lasts 8 hours and the cookies that keep you signed in last 30 days. Signing out clears them.
• Server and access logs: 30 days, then deleted.
• Console sign-in records: they expire after 30 days and are removed as new sign-ins arrive.
• Error reports: kept by Better Stack for the limited period set in our Better Stack account, then deleted. Older reports sent to Sentry are deleted when we close our Sentry account.
• Statistics about AI app requests (numbers and labels, with IDs scrambled): kept 13 months on our servers, then deleted. The copy sent to Better Stack is kept for the limited period set in our Better Stack account.
• Failed requests: records of failed requests, with IDs and times and no content, are kept 30 days.
• Contact form messages: 12 months after our conversation ends.
• Visit counts: totals only, with no personal information.
• A sign-up's campaign tag: kept while your organization exists, and deleted with it.
• Browser storage: as described in "Cookies and browser storage".

Your choices and rights

• Download your data. "Download", in the console under Settings, then Download my data, gives you every workspace you can read as plain text files. You can also email us for a copy.
• Delete a workspace you own, in the console.
• Turn off AI distillation for a workspace you own, in that workspace's settings in the console, where your organization has AI distillation.
• Hide your name from "who saved a memory": email privacy@contexel.ai. Workspace owners and organization admins can turn names off for a workspace, in the console.
• Turn off questions from teammates in the console's "Questions for you" box.
• Remove access: revoke access tokens, remove people from a workspace, or disconnect a GitHub repository. Disconnecting deletes our copy of that repository.
• Ask us. Email privacy@contexel.ai to see, correct or delete the personal information we hold about you, or to object to how we use it. We answer within one month and don't charge for it.

You can also ask for a copy of your information in a format you can take to another service, ask us to limit how we use it, and take back any permission you gave, such as permission to send notes to an AI provider. To protect your account, we answer requests sent from the email address on the account, or we confirm with you there first.

Depending on where you live, data protection laws (such as the GDPR in Europe and the UK, or state privacy laws in the United States) give you these rights. We offer them to everyone. If you are in Europe and not satisfied with our answer, you can complain to your local data protection authority. In the UK you can complain to the Information Commissioner's Office.

California and other US states

In the last 12 months we collected these kinds of personal information, using California's labels:

• Identifiers: your name, email address, user and organization IDs, the IP address WorkOS records at sign-in, and the IP address in our CloudFront access logs.
• Internet activity: the activity log, server and access logs, console sign-in records, feedback from your AI apps, error reports, and the campaign tag of the link you signed up through.
• Content you choose to save: this can include any kind of information, depending on what you put in it.

It comes from you, the AI apps you connect, your organization, WorkOS and the sign-in service you choose, and GitHub if you connect a repository. We use it for the purposes in "How we use it" and give it only to the companies in "Who else handles your data".

We don't sell personal information, and we don't share it for cross-context behavioral advertising, as California law defines those terms. We haven't done either in the last 12 months, and we don't knowingly sell or share information about anyone under 16. Because we do neither, there is nothing to opt out of.

We treat every visitor the same whether or not the browser sends Global Privacy Control or Do Not Track. No other company collects information through Contexel about what you do on other websites.

We use sensitive information, such as your sign-in details, only to provide the service and keep it secure.

To ask what we hold, or to delete or correct it, email privacy@contexel.ai. Someone you authorize can ask for you; we will ask for your signed permission and may confirm with you directly. We will never treat you differently for using these rights.

Where your data is stored

Contexel's servers are in the United States. If you sign up from another country, you send your information to us in the United States. When a company that works for us handles information about people in the European Economic Area, the UK or Switzerland, we rely on the EU-US Data Privacy Framework and its UK and Swiss extensions where that company is certified, or on the European Commission's standard contractual clauses.

Children

Contexel is for adults. You must be at least 18 to use it, wherever you live. There are no accounts for children, and no one can sign up on a child's behalf. We don't knowingly collect personal information from anyone under 18. If you believe someone under 18 has given us personal information, email privacy@contexel.ai and we will delete it.

Changes to this policy

When we change this policy, we will post the new version on this page and update the effective date at the top. If a change affects how we handle data you have already given us, we will tell account holders in the console or by email before it takes effect.

Contact us

Questions or requests about your privacy go to privacy@contexel.ai. Technoledgy LLC, a California limited liability company doing business as Contexel is responsible for your information. You can also write to us at 2108 N St #4624, Sacramento, CA 95816, USA.