Privacy
What Estela stores, what it never stores, and who the little it does gets shared with. Written to be read in full, not just to exist.
Last updated: September 10, 2026.
Who's responsible
Zaisor Technology LLC operates getestela.dev and is responsible for processing the data described on this page. For anything related to your privacy — accessing your data, correcting it, asking for it to be deleted, or any question — write to jdaniel.leonruiz@gmail.com. A person answers, not an automated inbox.
What Estela stores, depending on what you use
Estela starts out local: the Free plan runs entirely on your machine and sends nothing anywhere unless you decide to publish a panel. What does reach our servers depends on what you turn on:
| If you use | Stored on the server |
|---|---|
| Just Free, local | Nothing. It all lives in ~/.estela/estela.db, on your disk. |
| Creating an account | Your email, and nothing else — we don't ask for a name, a company, or a card until you subscribe. |
| Publishing a panel | The hours and the amount for that project, so whoever has the link can see them. Nothing from your machine, only what that project already calculated. |
| Syncing (Pro) | The daily hour total for each project, so it looks the same across your machines. Never the content of your commits or your prompts. |
| Team (Teams) | For each invited person: daily hours, and the detail of where the work went — the branch, a short description, and the commit hashes that back it up. Never the full commit message, never the diff. It's exactly what's already in the repository of whoever's paying. |
| Subscribing to Pro or Teams | Your email and the customer ID Stripe gives us. Stripe sees and stores your card directly — we never see it or store it, not a single digit. |
| Writing to us | The email and the message from the contact form, so we can reply. |
What we never store
This is structural, not a loose promise: the code has no column where the following would fit, so it's not that we "don't look at it" — it doesn't fit.
- The content of your prompts or your conversations with your AI agent.
- The source code, or the
diffof any commit. - The full message of a commit — the team's description only stores one short line, plus the branches and hashes that back it up.
- Your payment card, in any form.
AI cost is a special case
If you use AI agents, Estela measures their cost — but never per person, without that person explicitly granting it. A team lead can ask to see that cost; whoever's asked gets a notice and decides whether to share it. If they say no, the lead finds out it was denied, never the number. And even when it's granted, what travels is an aggregated project total, never broken down person by person — whoever contributes with their own AI subscription is excluded from the calculation, so no one can deduce their spend by elimination.
Who it's shared with
No one who doesn't need the data to provide you the service. The ones who do:
| Who | What for | What reaches them |
|---|---|---|
| Stripe | Billing Pro and Teams | Your email and the payment details you give them directly. |
| Resend | Sending Estela's emails (sign-in links, invitations) | Your email and the content of that specific email. |
| DigitalOcean | Hosting the server | Everything in the table above, encrypted in transit. |
| Google Analytics | Knowing how many people visit the landing and from where | Nothing until you accept it in the cookie notice — see below. |
There's no other third party.
Where your data lives
The server is in Frankfurt, Germany — inside the European Union, for those who subscribe from here. If you use the Free plan, your data never leaves your own disk.
How long it's kept
As long as your account exists. There's a daily backup of the database, kept for 14 days and then discarded on its own. If you ask for your account to be deleted (see below), it's removed from the live database; backups from the 14 days before the request may still exist until they expire on their own.
Your rights
Access what we have on you, correct it, ask for it to be deleted, or ask for a portable copy of your data. The last two are self-service: from Billing in your panel you can download all your data as JSON whenever you want, and delete your account yourself — any active subscription is cancelled and everything is deleted in cascade, without waiting on anyone to do it for you. To access or correct anything self-service doesn't cover, write to jdaniel.leonruiz@gmail.com. A person replies, usually within a week.
Cookies
One technical one, always active: the one that keeps you signed in to your panel
(estela_session). No advertising cookies, no third-party ones, no
cross-site tracking.
Beyond that, if you accept the notice that appears when you arrive, Google Analytics sets its own to count visits — never before you accept it. We use Google's Consent Mode: the site explicitly tells Google to store nothing until that moment, not a decorative notice on top of tracking that was already running. You can decline it and keep using Estela exactly the same — nothing about the product depends on that analytics.
Minors
Estela isn't intended for anyone under 16, and we don't knowingly collect data from anyone below that age.
Changes to this policy
If anything changes in a meaningful way, it's noted here with the date updated at the top. We don't promise an email for every minor change, but we do for any that affects what's stored or who it's shared with.
Something unclear here? Write to us directly at jdaniel.leonruiz@gmail.com. A person answers.