Privacy Policy

Effective date: 2026-10-07. Last updated: 2026-10-19.

This Privacy Policy explains how CAMPOS ANIDO ERNESTO JOSE, a sole proprietor trading as erni.works, Plaza Ginza Shintomi Bldg. 501, 2-11-11 Shintomi, Chuo-ku, Tokyo 104-0041, Japan (Ephemeral, we, us) handles personal data in the hosted service at ephemer.al and app.ephemer.al (the Service). It is part of the Terms of Service. We are the business operator handling personal information under Japan's Act on the Protection of Personal Information (APPI) and, for people in the European Economic Area, the United Kingdom and Switzerland, the controller under the GDPR. The person responsible for personal data is CAMPOS ANIDO ERNESTO JOSE.

Self-hosted software. When you run Ephemeral on your own infrastructure, your run data stays in your infrastructure and we do not have access to it. The only things the software sends us are described in the Self-Hosted License Agreement: the license token, the machine ID, the software version and counts of runs started.

1. Who this covers and the two roles we have

For the account, billing, security and support data below, we decide why and how the data is used, and we are the controller. For the content that you send to the Service in runs (prompts, input, files, connection credentials, outputs), we act on your instructions, as your processor or service provider. If that content includes personal data about other people, you are responsible for having a lawful basis to send it, as the Terms provide. Ask us through the support page if you need a data processing agreement.

2. What we collect, why, and for how long

Account data. Your email address, name and a hash of your password (never the password itself); when you signed up, confirmed your email and last signed in; the organizations you create or join, your role, and invitations you send (the invited email address, for 7 days). An avatar picture, if you upload one. Purpose: to provide the Service and sign you in. We keep it while your account exists. Sign-ups that never confirm their email address are deleted automatically after 7 days.

Sessions. When you sign in we keep a hash of your session token with the time, the IP address and the browser identification (user agent) it started from. Purpose: security, and showing you where your sessions came from. Sessions end when you sign out or change your password, and are deleted soon after they expire.

Activity records. We record meaningful actions on your account (such as sign-ins, password and key changes, billing events and support actions) with the time, the IP address and user agent. We do not record secrets or the content of runs here. Purpose: security, fraud prevention, support and accountability.

Billing data. Credits and licenses are paid by card through Stripe, which collects your card details directly; we never receive your full card number. We keep the references and amounts Stripe gives us (payments, refunds, disputes, receipts), your balance and a ledger of credits and run charges, and your automatic top-up settings with the record of your consent. For license subscriptions we also keep the details you enter in the agreement form (legal entity name, address, country, tax ID, billing email, the signer's name and title) and a record of the acceptance.

Email. We send service email only (confirmations, password resets, invitations and support replies) and keep a short record of what was sent to whom, to support you and find delivery problems. We do not send marketing email.

Support. What you send through the support page (your email, the subject, messages, category and any run you link) and our replies. People without an account can report abuse by EphemeralBot through the form on the bot page; we keep the reporter's email address, the message and the IP address of the request. Purpose: to answer you and act on reports.

Runs and run content. For each run we keep the prompt, input, file contents and file list, connection references, the events (including tool calls, results and model output), the output, cost and status. Purpose: to run the task, show you the record and bill it. With zero data retention on, we keep only identifiers, status, timestamps, cost and usage figures and a generic error category; events and output are held only briefly (see section 7). We remove known credential values, such as connection tokens, from events and output before storing them, but you must not put secrets in prompts or inputs. Connection credentials are stored encrypted. Files, workflows, schedules and connections you save are kept until you delete them.

Technical logs. Our systems keep request logs (time, address, status and the visitor's IP address) and error records, with credentials and tokens removed, to operate and secure the Service.

Security checks. Sign-up, password recovery and some forms use a captcha, and sign-in may ask for one after repeated failed attempts. The captcha provider receives information about your browser and your IP address to tell people from bots.

3. How we use personal data, and our lawful bases

We use personal data to: provide and secure the Service; process payments and keep accounts; send service messages; answer support requests and abuse reports; prevent fraud and abuse; investigate errors and improve reliability; and meet legal obligations. To help answer support requests, staff may have a request summarized and a reply drafted by AI, without your email address; a person reviews every reply. Under APPI these are the purposes of use. Under the GDPR our bases are the contract with you (providing the Service), our legitimate interests (security, fraud prevention, support, reliability and operating the business), legal obligation (tax and accounting), and your consent where we ask for it (for example, automatic top-ups). We do not sell personal data, and we do not use run content to train models.

4. Who we share it with

We share personal data only as needed with service providers that operate parts of the Service for us, and they may use it only for that purpose:

• Hosting and infrastructure, where the Service, its database, files and backups run. These are in Japan.
• Network delivery and protection, which carries traffic to our websites and API and protects them from attacks, and the captcha.
• Payments: Stripe.
• Email delivery, for service email.
• AI model providers, which receive the content of model calls (prompts, files, tool results and outputs) so the model you chose can answer. For zero data retention runs we use only endpoints that neither keep nor train on that content; for other runs the model provider's own data policy applies.
• Internal operations tools that our staff use to run, monitor and support the Service.

We also share data on your instructions: services you connect receive the requests and data a run sends them, and websites an agent visits receive EphemeralBot's requests (they see EphemeralBot's address, not yours). We disclose data where the law requires it, to protect rights and safety, or in a merger or sale of the business (the buyer takes over this Policy's commitments).

5. Cookies and local storage

We use only the cookies and browser storage needed to run the websites. We do not use advertising or analytics cookies or third-party tracking.

• Session cookie (ephemeral_session). Keeps you signed in on ephemer.al and app.ephemer.al. HttpOnly, secure, up to 7 days. Strictly necessary.
• Signed-in hint (ephemeralsignedin). Tells the page whether you are signed in, so it shows the right header. Up to 7 days.
• Language, theme and organization (ephemerallocale, ephemeraltheme, ephemeral_org). Remember your choices. 1 year.
• Browser storage. A short list of recently used commands and a small display preference. These never leave your browser.
• Captcha. When a security check is shown, the captcha provider may set its own cookies or storage.

You can block or delete cookies in your browser; the Service may then not keep you signed in.

6. International transfers

The Service and its data are hosted in Japan. Some of the providers in section 4 process personal data in other countries, including the United States. The data protection laws there may differ from Japan's. We use these providers under contracts with confidentiality and security terms, and for transfers from the European Economic Area, the United Kingdom or Switzerland we rely on standard contractual clauses or another lawful transfer mechanism. On request, we will tell you more about the countries involved and the measures each provider takes.

7. How long we keep it

• Finished runs, with events and output: 30 days after they end. Zero data retention runs: no content kept; output held for at most 1 hour.
• Unconfirmed sign-ups: 7 days.
• Sessions: until you sign out, change your password, or shortly after they expire.
• Activity records: up to 400 days. Error records and technical logs: up to 90 days. Email records: up to 180 days.
• Database backups: 30 days, so a deleted record can remain in a backup for up to 30 days. It is not restored afterwards.
• Billing, payment and ledger records, and agreement acceptances: as long as needed for accounting, tax, disputes and legal claims.
• Support requests: as long as they are useful for support, security and accounting, and on request as section 8 describes.
• Account data: while your account exists, and afterwards only what the law or a dispute requires.

8. Your rights

Under APPI, you may ask us to tell you the purpose of use of, disclose, correct, add to, delete, stop using, or stop providing to third parties the personal data we hold about you, and to disclose records of its provision to third parties, as the law provides. We will respond in a reasonable period and may ask to verify your identity. There may be a fee set under the law for disclosure requests.

Under the GDPR, if it applies to you, you have the right to access your data, to correct it, to delete it, to restrict or object to processing, to portability of the data you gave us, to withdraw consent at any time (without affecting earlier processing), and to complain to your data protection authority.

How to use them. Signed-in users: send a request through the support page at https://ephemer.al/support. People without an account: send a request to [email protected]. You can change your name, avatar and password, and delete saved files, workflows, connections and API keys yourself in the dashboard. To delete your account, ask through the support page. If there is data we must keep (section 7), we will tell you which.

9. Security

We protect personal data with technical and organizational measures, including encryption in transit and at rest, hashed passwords and tokens, encrypted credentials, an isolated machine for every run, and restricted, logged staff access. No system is perfectly secure. We do not claim any security certification.

10. Children

The Service is not directed to children, and you must be an adult to use it. If you believe a child has given us personal data, contact us and we will delete it.

11. Changes to this Policy

We may update this Policy by publishing a new version here with a new date. If a change materially affects how we use your data, we will notify you by email or in the dashboard before it applies, and where the law requires, ask for your consent.

12. Contact

Signed-in users: https://ephemer.al/support. Everyone else: [email protected]. Our business operator details are CAMPOS ANIDO ERNESTO JOSE, a sole proprietor trading as erni.works, Plaza Ginza Shintomi Bldg. 501, 2-11-11 Shintomi, Chuo-ku, Tokyo 104-0041, Japan, and the person responsible for personal data is CAMPOS ANIDO ERNESTO JOSE.

This Policy is provided in English. Any translation is for convenience, and the English version governs.