Skip to main content

Legal

Privacy Policy

Last updated:

View raw markdown
On this page

Keynodex LLC publishes keynodex.com and the Keynodex Memory service. This policy explains what we collect, why we collect it, how long we keep it, and the choices you have. It is written in plain English and describes the system as it actually works today.


1.0 Who we are

1.1 Keynodex LLC is a Florida limited liability company and the controller responsible for the personal data described in this policy.

1.2 The best way to reach us about privacy is [email protected]. Our controller contact is [email protected].

1.3 This policy covers keynodex.com (including the Rep name waitlist), the Keynodex Memory service (the app at memory.keynodex.com), and the Keynodex connectors that let AI assistants call Memory tools. PingRep products are separate services with their own privacy policy at pingrep.com.


2.0 The short version

2.1 We collect the minimum needed to run the website, the recruiting pipeline, the ambassador programme, the Rep name waitlist, and Keynodex Memory.

2.2 We do not sell your personal data.

2.3 Your memories belong to your tenant. They are used to provide the Memory tools — not to train Keynodex models and not for advertising.

2.4 Memory is encrypted in transit. It is not end-to-end encrypted; section 4.4 explains exactly what that means.

2.5 You can access, export, correct, or delete your data. Section 8.0 explains how.


3.0 What we collect

3.1 Visiting the website

3.1.1 Standard server logs needed to serve pages and stop abuse, plus, only with your performance consent, page path, referring host, UTM campaign parameters and a tab-scoped session identifier. The Cookie Policy lists every key.

3.1.2 Product analytics (PostHog). When analytics is allowed (Cookie Policy 5.9), we record a small set of events: pages viewed (path, campaign parameters and the referring site's host), clicks on calls to action, whether the contact form or the waitlist form was sent or rejected (with a reason code, never what you typed), and clicks on links and buttons. Events carry a random visit identifier held for the life of the tab, and your browser, operating system and device type. We do not record what you type, the text of pages, your location or your sessions, and our PostHog project discards IP addresses.

3.1.3 Error reports (PostHog). When something breaks, PostHog receives the error, the page path without any query string, your browser and operating system, and the version of our site. Reports from our own server are sent whatever you choose, because they are about our server failing. Reports from your browser follow the same rule as analytics. Cookies, headers, request content, IP addresses and user identifiers are removed, and email addresses and phone-like numbers in messages are replaced, before a report leaves.

3.1.4 Where you are. To apply the right consent rule we read your country from your IP address for that page load and compare it with your browser's time zone. Our site does not store the country.

3.1.5 Feedback chat. When you use the feedback chat (the "Feedback" button), the Keynodex feedback assistant asks you a few short questions. To ask them, your messages and the assistant's earlier replies in that chat go to the AI provider running it (Anthropic), with pictures of our own page and nothing else: no IP address and no account. When the chat ends, or when you tap to finish it, the Keynodex team receives one message with a short summary and your own words, by email and in the team's private Telegram channel. If you open the feedback chat from an answer the Rep gave you ("Share your question" or "Give feedback"), the question you asked, and for feedback on an answer the Rep's answer, are shown in the feedback chat. They are sent, to the AI provider and to the team, only when you send them. We do not save the chat on our servers or write it to our logs; for one hour we keep a one-way fingerprint of your words, only to stop the same chat being sent twice. We don't ask for your name or contact details; if you type them, the team will see them. We use feedback only to improve the site and our products. To have yours deleted, email [email protected] with roughly when you chatted and a phrase you wrote, so we can find it.

3.2 Job applications

3.2.1 When you apply for a role: your name, email address, phone number, resume and any links or free-text answers you submit, together with the IP address used to submit them (for spam and abuse triage).

3.3 Ambassador programme, referrals, and surveys

3.3.1 Ambassador and referral records: name, email address, payout method, tier, status, amounts and Stripe references.

3.3.2 Survey invites and responses: email address, name, referral codes, payment amounts for paid surveys, and the free-text answers you provide.

3.4 Accounts, billing, and security

3.4.1 Account identifiers for the Keynodex Memory service (sign-in email, tenant, plan, and Stripe subscription references), connector and OAuth data needed for supported AI assistants to call the Memory tools on your behalf, and operational and security logs used to run the service, investigate abuse, and respond to support or legal requests.

3.5 Rep name waitlist

3.5.1 When you reserve a kndx.me link name for your Rep, we collect your email address and the link name you chose. We also keep the time you asked and the time you confirmed.

3.5.2 We use your email address only to hold the name for you and to email you about it: a message to confirm your request now, and one message when Rep opens. We also use the link name to check it and to tune those checks (3.5.6 and 3.5.7).

3.5.3 The confirm link carries a one-time secret. We store only a one-way hash of it, never the secret itself, and we clear the hash once you use the link.

3.5.4 To keep to one name per person and to catch look-alike names, we also store two values worked out from what you gave us: a keyed hash of your email address that treats small variations of one address as the same address, and a simplified form of the link name.

3.5.5 If you later sign in to Rep with the same verified email address, we link your confirmed name to your account, so only your account can take it.

3.5.6 We check each link name with our own rules and then with OpenAI (section 6.4). A name that looks like a phone number or an email address is refused before it goes any further.

3.5.7 To tune these checks, we keep a log of what each check decided about a name: the simplified name, the check, the category that matched, the scores, the result and the time. The log holds no email address, no IP address and no account. A name that looks like a phone number or an email address is logged without its text.

3.5.8 The form uses a bot check (Cloudflare Turnstile). To limit abuse, we also count requests by network address and by email. The counts are stored only as keyed hashes, never as the address itself, and are kept for a day at most.

3.6 Security log

3.6.1 To prevent abuse, to keep the site secure, and to meet legal obligations, we keep a security log of each message sent through the contact form (whether we accepted or blocked it) and each résumé uploaded for a job application. Each entry holds the time, the kind of event, the outcome and a short reason code, your IP address, and a one-way hash of your email address. For a résumé upload it also holds a fingerprint of the file (a one-way hash) and its size. It holds no message text, no name, no email address and no résumé content.

3.6.2 We keep your IP address in this log as it is, because we need it to block an abuser and, if we ever receive illegal material, to make the report the law requires (18 U.S.C. 2258A). We keep the hash of your email address so we can match repeat abuse without keeping the address. We use the log for these purposes only.

3.6.3 Entries are deleted after 90 days. We keep an entry longer only when the founder places a hold on it, for a security incident or a legal duty. A held entry is kept until the hold ends; where we have reported an upload as the law requires, we keep it for at least one year. We also record each time a hold is released (who released it, when, and which entries), and we keep that record.

3.6.4 Only the founder can open the security log, through the protected admin area.

3.7 Chatting with Keynodex's Rep on keynodex.com

3.7.1 When you send a message to the Rep on keynodex.com/rep, we save the chat: your messages, the Rep's replies, the suggested question you started from (if any), the time, which AI model answered, and how long and how much each reply took. We do not ask for your name or sign you in, and we do not save your IP address with the chat.

3.7.2 Before a chat is saved, we automatically remove email addresses and phone numbers written in the usual ways. This can miss some, so please don't share them or other sensitive information in the chat.

3.7.3 We use saved chats only to improve Rep: to find questions it answers badly, to test changes, and to compare AI models on quality and cost. Keynodex staff and the AI tools we use to build Rep may read them. We do not sell them, use them for advertising, or use them to train AI models.

3.7.4 To answer you, your messages go to the AI provider running the chat at that moment, Anthropic or OpenAI (section 6.5).

3.7.5 The notice above the message box tells you this before you send. If you don't want your chat saved, don't send a message.

3.7.6 To avoid repeating itself, the Rep keeps a short technical note of which topics it has already covered in a chat. The note holds no message text and is deleted automatically 24 hours after the chat's last message.

3.7.7 So that your chat is still there when you come back to the page, your browser keeps a copy of it in that tab (session storage, see our Cookie Policy). The copy stays on your device. It is removed when you choose "New chat" and when the tab's session ends (normally when you close the tab). A copy whose last message is more than 24 hours old is not shown again and is removed the next time you open the page. "New chat" does not delete the saved chat described in 3.7.1.


4.0 Keynodex Memory notice

4.1 Memory data belongs to your tenant

4.1.1 Keynodex Memory is a model-agnostic memory service for AI assistants. Your memories are stored for your tenant and are used to provide the memory tools, not to train Keynodex models or sell your content.

4.2 What Keynodex Memory stores

4.2.1 Memory records you choose to store, including content, summaries, tags, projects, entities, links, versions, verification metadata, and timestamps.

4.2.2 Account and billing identifiers, connector and OAuth data needed to let supported AI assistants call the Memory tools on your behalf.

4.2.3 Operational and security logs used to run the service, investigate abuse, and respond to support or legal requests.

4.2.4 How you found us. When you sign up, we record your sign-up source as short labels: the kind of source (for example a campaign link or another website), the campaign labels from the link, and the host of the site that sent you. If you are in the United States and your browser does not send Global Privacy Control, the Memory app may keep these labels in a first-party cookie for up to 30 days before you sign up (Cookie Policy 5.11). Everywhere else, and whenever your browser sends Global Privacy Control, the app sets no such cookie. We never record full web addresses, search terms, your email address or your IP address as part of your sign-up source.

4.3 How Keynodex Memory uses it

4.3.1 To provide tenant-scoped memory retrieval, storage, export, and deletion workflows.

4.3.2 To enforce account access, billing entitlements, rate limits, and connector permissions.

4.3.3 To debug, secure, and support the service when you ask for help or when abuse or reliability issues require investigation.

4.4 How Keynodex Memory protects it

4.4.1 Memories are isolated per tenant and encrypted in transit. Access requires an authenticated session scoped to your account.

4.4.2 Your memories are stored on a server we rent from Hetzner in Singapore. Sign-in, sessions and account records (plan, billing references and sign-up source) are kept by Cloudflare.

4.4.3 Keynodex Memory does not use end-to-end encryption today. Authorized operators can technically access stored data through administrative paths when needed to operate the service, investigate abuse, comply with law, or act on your request.

4.5 AI assistant handoff

4.5.1 When your assistant retrieves a memory, a copy of that memory is returned to the assistant provider, such as Anthropic or OpenAI.

4.5.2 That provider then processes the copy under its own terms, privacy policy, plan settings, and data-control choices.

4.5.3 Keynodex is responsible for the data we store and send through the connector. You are responsible for configuring the assistant provider settings for your own account or workspace.

4.6 Export and deletion

4.6.1 Export is part of the product promise. Self-serve open-format export is being added to every plan, including Free.

4.6.2 Today, the delete_memory tool hides a memory from normal reads and preserves a deleted record for history. For full erasure of memories or your account, email [email protected]. We acknowledge erasure requests within 3 business days and target completion within 30 days.

4.7 Usage events and error reports

4.7.1 Keynodex Memory sends PostHog (US cloud) four account milestones: you signed up, an AI assistant connected for the first time, your first save, and your first recall. Each event carries a pseudonymous identifier (a salted hash, never your email address or account id), your plan, which assistant was used, and your sign-up source labels (4.2.4). Events never contain memory content, your searches, tool inputs or results, your email address, your name or your IP address.

4.7.2 When the Memory app or server fails, Sentry receives the error, the part of our code that failed, the route and the software version. Cookies, sign-in headers, request bodies, query strings, email addresses and memory content are removed before a report leaves.

4.7.3 We use these to see where people get stuck and to fix failures (legitimate interests, 5.2). To object, email [email protected].

4.8 Healthcare data

4.8.1 Do not store protected health information if your use requires a BAA or HIPAA-covered workflow. HIPAA support is under review.


5.1 Contract. To provide the services you sign up for, including Memory storage and retrieval, accounts, and paid plans.

5.2 Legitimate interests. To secure the services, prevent abuse and spam, debug reliability issues (including error reports from our own server, 3.1.3), and improve the website. We balance these interests against your rights.

5.3 Consent. For analytics and advertising storage, which stay off until you turn them on, except in places where the law lets analytics start on behind a notice you can decline (Cookie Policy 5.9). You can withdraw consent or decline at any time.

5.4 Legal obligation. To keep financial records for tax and accounting purposes and to respond to lawful requests.


6.0 Who we share it with

6.1 We do not sell personal data. We share it only with service providers that operate the services for us:

Provider Purpose Data
Vercel Hosting and delivery Request logs
Fly.io (US East, Ashburn, Virginia) Runs the server behind the Rep name waitlist Requests to that server: email address, link name
Managed Postgres Database for keynodex.com: job applications, ambassador, referral and survey records Those records
Hetzner (Singapore) Runs the Keynodex Memory server and stores your memories Memory records, account identifiers
Cloudflare (Workers, D1, KV, R2, Turnstile) Runs the Keynodex Memory app and sign-in; object storage; form security Memory accounts, sessions, plan and sign-up source; uploaded files; abuse signals
Google Sign-in for Keynodex Memory Your Google account email address and account id
Sentry Error reports from the Keynodex Memory app and server The error, route and software version; no cookies, request content, email addresses or memory content
Upstash Redis (AWS, Singapore; Global database, may keep read copies in other regions) Rate limiting, caching, and the security log (section 3.6); storing saved chats with the Rep Short-lived keys, IP-derived counters; security log entries (IP address, hashed email, file fingerprint); saved chats (3.7)
Stripe Payments Billing identifiers, payout details
Resend Transactional email Email address, message content
Anthropic Runs the feedback chat on keynodex.com; answers chats with the Rep on keynodex.com Your feedback chat messages and the assistant's replies; your chat messages and the Rep's replies
Telegram Delivers feedback chat summaries to the Keynodex team's private channel The summary of a feedback chat and the words you wrote in it
OpenAI Memory processing features; checking Rep link names; answering chats with the Rep on keynodex.com Memory text sent for processing; for the name check, the link name only; your chat messages and the Rep's replies
Google (Tag Manager, Analytics) Analytics, only with your consent Usage data
PostHog (US cloud) Product analytics and error reports for keynodex.com: analytics and browser error reports only when analytics is allowed, server error reports always. Keynodex Memory account milestones (4.7) Page path, campaign parameters, referring host, click events, random visit id, browser, operating system, device type; for errors, the error message, stack trace and site version
PingRep Tracking ingest for aggregate performance metrics, only with your performance consent Session id, page path, referring host, UTM parameters

6.2 When an AI assistant retrieves a memory, the assistant provider you configured receives a copy under its own terms — see section 4.5.

6.3 We may disclose data when required by law, to protect rights and safety, or as part of a merger or acquisition under this policy.

6.4 Rep name check. To check a link name we send OpenAI the name and nothing else: no email address and no IP address. OpenAI says it does not use data sent to its API to train its models, and that it keeps API requests for up to 30 days to check for abuse (longer where the law requires). See OpenAI's data controls page.

6.5 Chats with the Rep. We send the AI provider your messages and the Rep's earlier replies in that chat, and nothing else: no IP address and no account. Anthropic and OpenAI each say they do not use data sent to their APIs to train their models, and keep it for a limited time to check for abuse. See Anthropic's privacy policy and OpenAI's data controls page.


7.0 How long we keep it

7.1 We keep personal data only as long as needed for the purposes in this policy, to meet legal obligations, and to resolve disputes.

7.2 Current practice, plainly stated:

  • 7.2.1 Financial records (ambassador payouts, referrals, paid surveys) are kept as required for tax and accounting purposes.

  • 7.2.2 Job applications, résumés, IP addresses, survey responses and feedback chat summaries have no automated purge today; records are kept while the hiring or research purpose remains active and are deleted on request (section 8.0).

  • 7.2.3 Server security logs and rate-limit counters are used for abuse prevention and forensics and are short-lived by design.

  • 7.2.4 Unconfirmed name requests (the email address and link name) are deleted 24 hours after you ask. The confirm link stops working at the same time.

  • 7.2.5 Confirmed names are held until 30 days after Rep launches. If you have not set up your Rep by then, we release the name and delete the reservation, including your email address. If you set up your Rep with the name sooner, we delete the reservation then.

  • 7.2.6 Names held for a check (a person needs to look at them, or the check could not run) are dropped, with the email address, after 7 days.

  • 7.2.7 The name-check log keeps the simplified name only, with no email address and no IP address, for 90 days.

  • 7.2.8 Link names of deleted accounts are held for 90 days, so nobody can take one at once to pass as you. We store only a one-way hash of the name and the date the hold ends. Nothing in that record says whose name it was.

  • 7.2.9 Analytics events (PostHog) are kept for 12 months.

  • 7.2.10 Error reports (PostHog) are kept for 12 months, like analytics events.

  • 7.2.11 The security log (section 3.6) keeps each entry for 90 days. An entry on hold for a security incident or a legal duty is kept until the hold ends, and a reported upload for at least one year. The record of released holds is kept.

  • 7.2.12 Memories are kept until you delete them. A deleted memory is hidden at once and kept for history until it is erased; ask for full erasure at any time (4.6).

  • 7.2.13 Your Memory account record and sign-up source are kept while your account exists.

  • 7.2.14 Saved chats with the Rep are deleted automatically 90 days after the chat starts. To have one deleted sooner, email [email protected] with the chat ID (the line "Chat ID" in a chat copied with "Copy whole chat") or, if you don't have it, roughly when you chatted and a phrase you wrote, so we can find it.

7.3 You can ask us to delete specific records at any time — section 8.0.


8.0 Your rights and how to exercise them

8.1 Depending on where you live, you may have the right to access, correct, delete, export, or restrict processing of your personal data, and to object to processing based on legitimate interests.

8.2 To exercise any right, email [email protected]. Requests submitted to [email protected] are acknowledged within 3 business days and processed within 30 calendar days.

8.3 We will not discriminate against you for exercising your privacy rights.

8.4 Rep name reservations. To see or delete your reservation, email [email protected] from the address you used. We will tell you what we hold and delete it when you ask. Deleting a reservation releases the name. Our operators have tools to export and erase a reservation by email address. The name-check log holds no email address, so it cannot be looked up by email; its lines expire after 90 days.


9.0 Cookies

9.1 Cookies and similar storage are described in the Cookie Policy. Analytics and advertising storage are optional and off by default, except that in places where the law allows it (today, the United States) product analytics and error reports start on behind a notice you can decline. Advertising never starts on. A Global Privacy Control signal forces targeting off and puts you under the opt-in rule.


10.0 International transfers

10.1 We are based in the United States and use service providers in the United States and other countries. Where personal data protected by GDPR or similar laws is transferred, we rely on appropriate safeguards such as standard contractual clauses. Our analytics and error-report provider, PostHog, stores this data in its United States region. Saved chats with the Rep (section 3.7) are stored with Upstash Redis in Singapore (AWS ap-southeast-1); the database may keep read copies in other regions.


11.0 Children

11.1 The services are not directed to children under 13, and we do not knowingly collect their personal data. If you believe a child has provided us data, contact us and we will delete it.


12.0 Changes to this policy

12.1 We will post changes on this page and update the date above. Material changes are also surfaced in the product or by email where appropriate.


13.0 Region supplements

13.1 EEA, UK, and Switzerland. You have the GDPR rights described in section 8.0, including the right to lodge a complaint with your local supervisory authority. Where EU or UK law requires us to appoint a representative, their contact details will be published in this section.

13.2 United States. California, Virginia, Colorado, Connecticut, Texas, Oregon, Nevada, Utah, and Iowa residents have the rights described in section 8.0, including the right to opt out of sale or sharing. We do not sell personal data.


14.0 Contact

14.1 Privacy requests: [email protected] 14.2 Controller contact: [email protected]