Privacy policy
Last updated 2026-11-13. Operated by Happi Hacking AB, org. nr 556912-2707, Sweden.
Who is responsible
Happi Hacking AB, org. nr 556912-2707, Sweden, is the controller for personal data handled by Eldrim Compute. Questions and requests: support@eldrim.ai.
What we collect, and why
- Account details: name, email address, company, and for each API key a hash of the key, the name you give it, who created it, and when it expires or was revoked. Used to provide the service and contact you about it. Legal basis: contract.
- BEAM developer grants: your verified email identity, event attribution, accepted offer revision, grant expiry, token usage and reservations. A campaign-scoped email digest prevents duplicate grants across sign-in methods. Email sign-in can recover the campaign grant for that address without inheriting other accounts. Verification budgets keep email and link digests, event and request time for 30 days; expired budget records are removed on the email purge cycle. These digests are personal data. Campaign signup does not subscribe you to marketing. We record one quota-threshold event and, if you request it, an interest-in-continuing event. A quota notice uses the verified grant address and the existing email outbox. Its recipient and outcome follow the 30-day mail retention policy; the grant event remains with the account so purging mail cannot resend the notice.
- Payment details: card payments are handled by Stripe. We receive the payer's name, billing address, VAT number and the amounts paid, not the card number. Used for billing and bookkeeping. Legal basis: contract and legal obligation.
- Usage metadata: for each API request, the time, its request ID, the account, which of its API keys made it (an internal id, never the key itself), the model and the provider's name for it, the provider and the jurisdiction configured for it, status, token counts, price and cost with the price list or contract they come from, response time, and how the request was handled (which providers were tried or skipped and why, a refusal under a concurrency limit, or that it came from the console's test box). A sponsored request also records the campaign grant it used. Used for billing, capacity planning and support. Legal basis: contract.
- Console sign-in: the email address and account identifier of the Google account you sign in to the console with, or, when you sign in with a link we email you, that email address; which Eldrim accounts you may act for; and your sign-in sessions with the times they started and were last used. For each sign-in link we keep a hash of the link (the queued email contains the usable link until sending ends), the address it went to, and when it was sent, expires and was used. Sign-ins and account changes are recorded by an internal user number, not by email address. Used to give you access to the console and to know who acted for an account. Legal basis: contract.
- Business enquiries and prospects: company and business-contact details, short conversation summaries, their source references, expected workloads, follow-up dates and draft pricing. We use these to answer enquiries and discuss potential services or partnerships. Information comes from our correspondence, introductions and relevant public company information. Access is restricted to named Eldrim administrators. You can ask us to correct or remove a record or stop contacting you.
- Signup requests: what you enter in the signup form, and the IP address it was sent from, used to answer you and to limit abuse. Hearth and coding trial requests store your email address and which trial you requested for manual review; their IP addresses are used only in the in-memory counters below. Legal basis: legitimate interest.
- Rate limits: to stop abuse of our public forms and sign-in, our gateway counts requests per IP address (the address our proxy reports for your connection) on the signup form, the Hearth and coding trials, invitation pages, console sign-in and sign-in links by email. For the trials and sign-in links by email it also counts requests per email address; that counter holds a hash of the email address. In the console, linking an account is counted per user, and creating API keys per account. Each counter covers one clock hour. The gateway keeps these counters in memory, deletes each within two hours, and does not write them to files or to its logs. Legal basis: legitimate interest in preventing abuse.
- Email we send: the recipient's address, the subject and the text of each message, and whether our mail relay accepted it. We send an invitation link to a person we invite, and a sign-in link to an address that asks for one and can sign in. We tell an account's owners and its contact address when one of its API keys is created or revoked, and the contact address when someone links the account to a console sign-in, naming that person's email; a notice names the key, never the key itself. For an account invoiced in arrears, we tell its contact address when it has used most of its credit limit, with the amounts. Used to deliver the message and to see whether it went out. Legal basis: contract for account notices, legitimate interest for invitations.
What we do not collect
Our gateway processes prompts and responses in memory and is designed to exclude their content from application logs and the database. Host paging, model caches, provider commitments and historical records require separate consideration. We do not currently offer a verified end-to-end zero data retention guarantee across all routes. See inference data and retention for the current controls and limitations. Our web servers do not keep access logs with visitors' IP addresses.
Who processes data for us
- Bahnhof AB, Sweden: hosting of the website, API gateway and database.
- Stripe: payments. Stripe is also a controller for some payment data; see stripe.com/privacy.
- Google (Google Workspace): email. Console sign-in uses your own Google account; Google manages that account under its own terms and tells us its email address and identifier when you sign in.
- Compute providers: the prompt and response of each request pass through the provider that serves it, chosen within your residency policy and named in each response. Test models run on test machines that Happi Hacking operates in Sweden. They serve invited testers and coworkers, our internal account and the coding trial.
- Berget AI AB, Stockholm, Sweden: runs some of the models we offer. It processes the prompts and responses of requests to those models on our behalf, and each of those responses names Berget as the provider.
Stripe and Google may process data outside the EU/EEA, under the EU-US Data Privacy Framework or the EU standard contractual clauses.
How long we keep it
- Account details: while the account is open, and 12 months after it is closed.
- Billing records and the usage metadata they are based on: 7 years, as Swedish bookkeeping law requires. The response times and routing details in usage metadata are kept with those records until a separate period is set.
- Campaign grants, attribution and reservation evidence: follow account retention above; sponsored requests follow the usage record policy. Operator review after campaign expiry checks unresolved work and records kept for support. Verification-budget digests are retained for 30 days, with deletion on the next email purge cycle, including startup after downtime.
- Signup requests that do not lead to an account: 12 months.
- Prospect records: kept while needed for the business discussion, with operator review of records inactive for 12 months. Operators can delete the record and its associated contacts, notes and draft prices from the active database. Existing database backups expire after 30 days.
- Console sign-in sessions: until you sign out, or at most 7 days, or 24 hours without use. A sign-in identity, Google or email, that is not a member of any Eldrim account is deleted once its sessions have ended; one that is a member is kept while it is.
- Audit records of sign-ins and account changes: 2 years. The gateway deletes older records once a day, and when it starts. Database backups keep a deleted record for up to 30 days.
- Sign-in links by email: a link works once and for 15 minutes; its record is deleted within 10 minutes after it expires, or, if our gateway is stopped then, when it starts again.
- Email we send: the text is deleted once sending has ended, whether or not the message was delivered, and the record of the message 30 days after it was created.
Cookies and browser storage
The sales site at eldrim.ai and the API at api.eldrim.net set no cookies and store nothing in your browser. None of our sites use analytics, advertising or tracking, and our pages load no fonts, scripts or other content from other companies.
The console at console.eldrim.net stores only what signing in and the features you use need. Each item below is strictly necessary for a service you have asked for, so under the Swedish Electronic Communications Act (2022:482), chapter 9, section 28, we do not ask for your consent. The cookies are first-party, are sent only to console.eldrim.net over HTTPS, and cannot be read by scripts on the page.
- __Host-eldrim_console_login: set when you choose to sign in with Google. It ties Google's reply to the browser that started the sign-in. It holds random sign-in values and, if you arrived through an invitation link, that invitation's code. It lasts at most 10 minutes and is deleted when Google sends you back to the console.
- __Host-eldrim_console_email: set when you ask for a sign-in link by email. It holds a hash of the link and no email address, so the page the link opens can tell whether you asked from the same browser. It lasts at most 15 minutes, and is deleted sooner when you sign in with that link in the same browser.
- __Host-eldrim_console: your console session. It holds a random identifier that our server links to your sign-in. It lasts until you close the browser. Our server ends the session sooner if you sign out, after 24 hours without use, and in any case 7 days after you signed in. A browser that restores your previous session after a restart may keep the cookie; our server's limits still apply.
- eldrim_budget_guide:<account id>, in the tab's session storage: if you set a budget guide target in the console, your browser keeps it there so the meters can show it. It never leaves your browser. It is deleted when you close the tab, choose Clear or sign out in that tab. A browser that restores your tabs after a restart may restore it with them.
The console does not keep your API keys in your browser.
The session cookie identifies your signed-in session, and the other two cookies can be linked to your email address or invitation while you sign in, so we treat all three as personal data. We use them to give you access to the console (legal basis: contract) and to protect your account. The sections on what we collect and how long we keep it describe the sign-in records behind them.
When you sign in with Google or pay for credit with Stripe, your browser goes to Google's or Stripe's own site. Those companies can set their own cookies there under their own policies (policies.google.com/privacy and stripe.com/privacy). We do not read those cookies, and no Google or Stripe code runs on our pages.
If we add storage that is not strictly necessary, such as analytics or an option to stay signed in longer, we will update this section and ask for your consent before setting it.
Your rights
You may ask for access to, correction or deletion of your personal data, ask us to restrict its processing, object to it, or receive it in a portable format. Write to support@eldrim.ai. You may also complain to the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, imy.se).