← Back to BECOMER

Privacy Policy

What We Are

BECOMER is a memory API for developers. Developers integrate BECOMER into their applications to give those applications persistent memory. We store the memories developers write to us and return them when queried. That is the complete scope of our service.

What We Store

When a developer uses BECOMER, we store:

• Text content submitted via the API
• Timestamps of when content was submitted
• The API key associated with each submission
• Account information you provide at signup: email address and a one-way hashed password

We do not store personal information about your end users directly. Developers are responsible for what content they submit through their API key.

What We Never Do

Storage and retrieval happen on dedicated cloud infrastructure hosted in India. The only third party involved is our cloud infrastructure provider, which supplies the servers our software runs on — it provides hosting only and does not access, process, or use your content. Your data is never sent to any external AI service, analytics provider, or processing pipeline.

How We Protect Your Data

• Encrypted at rest — your stored memories are held in an encrypted database. Even direct access to the disk does not reveal your content.
• Encrypted in transit — all connections use HTTPS (TLS 1.2+).
• Hashed API keys — keys are stored as one-way hashes. We cannot recover your key, only verify it.
• Restricted access — access to stored content is limited to essential system operations. There is no routine human access to your memories in the normal course of running the service.
• Isolated storage — each account's data is isolated at the database level. One customer can never read another customer's memories.

Data Retention

Your data is retained as long as your account is active. If you delete your account or your memories, all associated data is permanently deleted within 24 hours. This deletion is irreversible.

Your Rights

You have the right to:

• Access — know what data is stored (available directly in your dashboard)
• Export — request all data stored under your API key (email hello@becomer.net)
• Delete — erase all data stored under your API key (available directly in your dashboard, no request needed)
• Correct — update your account information at any time

---

India — DPDP Act 2023 Compliance

BECOMER operates from India and complies with the Digital Personal Data Protection Act, 2023 (DPDP Act). For data we process as a Data Fiduciary (your account email and password):

• We collect only what is necessary to operate your account.
• We obtain your consent at signup before processing your data.
• You may withdraw consent and delete your account at any time.
• We notify affected users in the event of a personal data breach, as required by the Act.
• For the memory content you submit through the API, you are the Data Fiduciary and BECOMER acts as a Data Processor on your behalf.

Grievance contact for DPDP matters: hello@becomer.net

United States — CCPA / State Privacy Compliance

For users in the United States, including California residents under the California Consumer Privacy Act (CCPA):

• We do not sell or share personal information. There is nothing to opt out of, because we never sell data.
• You have the right to know what personal information we hold, the right to delete it, and the right to non-discrimination for exercising these rights.
• All deletion and access rights are exercisable directly in your dashboard or by emailing hello@becomer.net.

International Data & Sub-Processors

Our servers are located in India. By using BECOMER, you understand that your account data and stored memories are processed on infrastructure located in India. We do not transfer your data to any other jurisdiction.

We rely on a single category of sub-processor: a cloud infrastructure provider that supplies the servers BECOMER runs on. This provider hosts the encrypted environment but does not access, analyze, or use your content. We use no other sub-processors — no analytics services, no third-party AI, no external data processors.

---

Developer Responsibility

BECOMER is infrastructure. Developers who use our API are solely responsible for:

• Compliance with data protection laws applicable to their own end users
• Obtaining appropriate consent from their end users before submitting data to our API
• Ensuring their use of BECOMER complies with the laws of their jurisdiction

Any application built using BECOMER is under the sole discretion and compliance responsibility of the developer who built it.

Contact

For any privacy-related request: hello@becomer.net

Changes

We may update this policy. Changes will be posted on this page with an updated date. Continued use of the API after changes constitutes acceptance.