Privacy policy.

Controller: Ape on a Bike Industries LLC (operating as "Kijito"), a Florida limited liability company.

Address: Ape on a Bike Industries LLC, 2234 North Federal Hwy, #1137, Boca Raton, FL 33431, United States.

Privacy contact: [email protected]

This Privacy Policy explains what data Kijito ("the Service") collects, how we use and protect it, who we share it with, and your rights. Kijito is a persistent semantic-memory service for AI agents and their users: it stores memories (text), recalls them by meaning, and forms a graph (edges/themes) over them.

Age: Kijito is for adults only - you must be 18 or older to use it.

1. Data we collect

2. How we use your data

• Provide the Service - store, recall, encrypt/decrypt, index, and graph your memories; authenticate you; serve your requests.
• Operate and secure the Service - rate-limiting, abuse/bot prevention, audit logging, error monitoring, and protecting cross-tenant isolation.
• Communicate - transactional email (verification, security/account alerts).
• Billing - when paid plans are live, to manage subscriptions through Stripe.
• Legal - to comply with law and enforce our Terms and Acceptable Use Policy.

We do not sell your data, and we do not use your memory content to train third-party AI models.

3. How your memory content is protected - encryption & the tiered posture (please read)

We want to be precise about what "private" means here, because the honest answer differs between the hosted service and the local/self-hosted options.

• Encrypted at rest. Your memory content - and theme labels, centroids, and embeddings - are encrypted at rest under a key derived from your password (a scrypt key-derivation function produces a per-user content key).
• Transient in-RAM decryption (hosted tier). To recall or serve your requests, the hosted daemon transiently decrypts your content in RAM while a request is in flight, using the key loaded from your session. This means the hosted tier is encrypted at rest, NOT operator-blind - an operator with both server access and a live session could in principle read decrypted content during processing.
• No third-party content egress. The hosted daemon never sends your memory content to any external LLM or embedding API. Embeddings are computed locally by a self-hosted embedding model running within Kijito's own infrastructure, and the scheduled consolidation passes are mechanical (numeric/graph operations), not an AI/LLM call. Apart from error reports to Sentry (see Subprocessors), the only outbound call made while serving you is to Mailgun (email).
• Operator-blind only when decryption runs off our servers. True operator-blindness requires the decryption/recall to run outside our infrastructure - via an Enterprise on-premises deployment, or a local helper you run (on our roadmap). We reserve the unqualified term "zero-knowledge" for those local/self-hosted paths, not for the default hosted service. Neither is generally available yet.

Plain summary: Encrypted at rest, not operator-blind on the hosted service; operator-blind only when decryption runs off our servers, via the local/self-host paths. The hosted service decrypts transiently in memory to serve your requests and never sends your memories to any third-party AI.

4. Subprocessors

We use the following third-party processors to operate the Service.

Anthropic is not a subprocessor of your memory content. Kijito can be used with Claude clients, but the hosted daemon does not send your memory content to Anthropic.

5. Hosting, location & international transfers

• Where your data lives. Compute and storage are hosted on DigitalOcean in the United States (the SFO3 / San Francisco region) - the daemon box and Managed PostgreSQL run in the same private VPC.
• International transfers. If you are in the EU/UK, your data is processed in the US. Our Data Processing Addendum sets out the transfer safeguards we intend to use: the EU Standard Contractual Clauses (SCCs) (Commission Implementing Decision (EU) 2021/914 - Module Two for personal data we process on your behalf, and Module Three for onward transfers to our sub-processors) and the UK International Data Transfer Addendum (UK IDTA) for UK data. During the beta that addendum is provided as-is and has not yet been reviewed by counsel. An EU/UK Article 27 representative has not yet been appointed.

6. Retention & deletion

• Export. You can export all your data (memories + graph + consents) at any time via the authenticated self-serve export (GET /api/export).
• Deletion. You can delete your account end-to-end. Deletion purges your server-side data - graph nodes/edges, account row, keys, OAuth/JWT residue, and billing rows. There is one exception, and it is the next bullet.
• Abuse and safety reports are kept. Abuse reports survive account deletion. If you report another account, or another account reports you, that report is retained after either account is deleted, including the reporting user's id, the subject and target of the report, and the free-text details submitted with it. A report is resolved by an operator; it is not deleted. We keep it because deleting an account and signing up again must not clear a safety record, and because we have to be able to show how a report was handled. These records are used only for enforcement, safety and audit - never for advertising or profiling. We do not currently expire them: there is no scheduled deletion for abuse reports, and resolving one changes its status rather than removing it. If you believe a report about you is being retained without justification, write to [email protected].
• Grace window. We retain deleted data for a short grace window before final purge: 30 days (soft-delete, then permanent purge). This protects against accidental deletion.
• Backups. Encrypted at-rest data is included in operational backups (encrypted backups are written daily, with point-in-time recovery on the managed PostgreSQL control plane). Backups roll off on their own retention schedule, after which residual copies are purged.

7. Your rights & how to exercise them

Depending on where you live (e.g., GDPR/UK-GDPR, CCPA/CPRA), you have rights over your data. We map each to a concrete mechanism:

We respond to verifiable requests within the timeframe required by applicable law. You may also lodge a complaint with your local data protection authority.

8. Cookies & authentication tokens

The Service itself uses only strictly-necessary authentication/session tokens (JWT access/refresh) to keep you signed in and to operate it. The kijito.ai website also offers one optional analytics cookie, Google Analytics, which loads only if you choose Accept in the cookie banner; Decline loads nothing. Your choice is stored in your browser so we ask once. We do not use advertising cookies.

9. Security

• Passwords stored as scrypt hashes with per-user salt; recovery codes hashed.
• Per-user content encryption; a cross-tenant isolation gate enforced on every scoped query.
• TLS in transit (Cloudflare Full (strict) to origin).
• Bot/abuse protections: per-IP and per-email signup rate limits, disposable-email blocking.
• Authentication: JWT access/refresh with token-version revocation; OAuth for connectors.

No system is perfectly secure, and the Service is offered as a public beta, in an early state.

10. Children

Kijito is not intended for anyone under 18. We do not knowingly collect data from people under 18 and will delete such data on a credible report.

11. Changes to this Policy

We may update this Policy. For material changes we will provide notice (email or in-app) and record which version you accepted in our consent log.

12. Contact

Privacy questions, rights requests, or general enquiries: [email protected]

Ape on a Bike Industries LLC, 2234 North Federal Hwy, #1137, Boca Raton, FL 33431, United States.