Privacy Policy

Last updated: October 8, 2026

The short version Enkava runs in your web browser, with no advertising and no third-party tracking. We count anonymous app opens so we know how many people use it — nothing that identifies you. You can use the whole editor without an account, and if you do, your artwork never leaves your device. Accounts and cloud saving are optional: if you create one, we store your email address, and if you save a project to the cloud, that project is stored on our servers so you can open it elsewhere. You can delete either at any time. Payments are handled by Stripe, not by us.

Enkava (“Enkava,” “the Service”) is a browser-based drawing, vector, and animation tool operated by Calivo LLC (“we,” “us,” “our”), a limited liability company based in South Carolina, USA. This policy explains what information is and isn’t involved when you use Enkava at enkava.com.

1. Information we collect

Without an account: nothing that identifies you. You can use the entire editor without signing up. We don’t ask for your name, email, or any personal information to draw, animate, or export, and nothing you make is sent to us. We do count anonymous app opens so we know how many people use Enkava — that count carries no identifier and cannot be traced back to you (see §2).

If you create an account (optional): we store the email address you sign up with, and a securely hashed version of your password — hashing means we cannot read your password, only check it. We also store the date you signed up, when you last signed in, and the day you last used Enkava while signed in (the date only, not the time or what you did), so we can tell which accounts are still in use. That is all an account itself involves; we do not ask for your name, address, or anything else.

Your artwork stays on your device unless you choose otherwise. Everything you draw is created and held locally in your browser. Saving a project keeps it in your browser’s own storage, and exporting a copy downloads a file to your own computer; neither path touches our servers. Cloud projects are the exception, and they are opt-in per project: when you use “Save to cloud,” that project’s artwork and settings, and a small preview image of it, are uploaded to our storage so you can open it on another device. We can technically access files stored this way in order to operate and support the service, but we do not look through your work, and we never use it to train anything or share it with anyone. You can delete a cloud project at any time from inside the app, which removes its files from our storage.

Local browser storage for signing in. When you are signed in, your browser stores a session token so you stay signed in between visits. Signing out removes it.

Local browser storage. Enkava uses your browser’s localStorage to remember your own settings between visits — things like your editor preferences, custom brushes, and color palettes. This data lives only in your browser, is not transmitted to us or anyone else, and you can clear it at any time through your browser’s settings.

2. Cookies, analytics & tracking

Enkava counts anonymous, aggregate usage statistics — essentially, how many times the app is opened — so we know how many people use it. There are no cookies, no advertising, no third-party trackers, and no identifier stored on your device for this. We do not profile you, and we do not sell or share your personal information.

To tell a repeat visit apart from a new visitor on the same day, our server briefly combines your IP address and browser type into a scrambled code, using a secret key that changes every day. Your IP address itself is never stored, and both the codes and the daily keys are deleted within two days — after that, nothing can link a count to anyone. What we keep is only the daily totals.

This is separate from having an account. If you create one, we hold the email address you signed up with and the other account details described in §1 — but that record is never linked to these usage counts.

The browser storage described above holds your own settings and, if you are signed in, your session token — it is never used to track you across sites, and there are no advertising cookies.

3. Hosting and server logs

The Enkava website is served by GitHub Pages (a service of GitHub, Inc.). Like essentially every website host, GitHub may automatically record standard technical information — such as your IP address, browser type, and which files were requested — for security and to operate the service. This information is collected and handled by GitHub under GitHub’s Privacy Statement. We do not use it to track or identify you.

Accounts and cloud storage are provided by Supabase. If you create an account or save a project to the cloud, that data is held on infrastructure operated by Supabase, Inc. on our behalf, in the United States, under Supabase’s Privacy Policy. Access is restricted by database security rules so that one account cannot read another account’s projects. The anonymous usage counts described in §2 are processed and stored there too.

Account emails are sent through Resend. Confirmation and password-reset messages, and the one reminder sent to an account that has not been verified (see §7), are delivered by Resend, Inc., which receives the email address needed to send them, under Resend’s Privacy Policy. We do not send marketing email, and there is no mailing list.

4. Payments (tips and subscriptions)

If you choose to leave a voluntary tip through the “Chip in” button, you are taken to a checkout page hosted by Stripe, Inc. Any payment details you enter — such as your card number — are collected and processed by Stripe under Stripe’s Privacy Policy. We never receive or store your full card number. We receive only limited transaction information from Stripe (for example, the amount and any name or email you provided to Stripe) so we can confirm the payment. Tipping is entirely optional; you can use everything in Enkava without ever making a payment.

If you take out a paid subscription, Stripe additionally keeps a customer record and your billing history, tied to your email, so it can bill you each period. From Stripe we receive your subscription status (for example, active or lapsed) and the renewal date, which we store to unlock your paid features — but, again, never your card number. A subscription is optional; the editor is free without one.

5. Links to other services

Enkava links to a few third-party services, such as our community Discord and the Stripe checkout above. When you follow those links you leave enkava.com, and your activity there is governed by that service’s own privacy policy, not this one.

6. Children’s privacy

Enkava is not directed to children under 13, and accounts are not intended for them. We do not knowingly collect personal information from children. If you believe a child has created an account or otherwise provided us personal information, contact us and we will delete it.

7. How long we keep things

Cloud projects are kept until you delete them — we do not expire them on a schedule. Account details are kept for as long as the account exists. Delete your account and we remove your account record and any projects stored with it. Backups may take a short time to cycle out afterwards.

Earlier versions of a cloud project (Enkava Pro). With a Pro subscription, saving a cloud project keeps the version it replaced, so you can go back to it. Those earlier versions are stored with the project. Ones you haven’t pinned are removed automatically as they age — none is kept longer than 30 days — and a version you pin is kept until you delete it. You can delete any version at any time, and deleting a cloud project deletes all of its versions.

If a Pro subscription ends, the earlier versions and the saved symbol library that came with it are locked, not deleted: they stay stored, and come back if you subscribe again. We may delete them once an account has been without Pro for 12 months, and we will email the account’s address before we do. Your ordinary cloud projects are not affected by this.

Accounts that are never verified are deleted automatically. If the email address on a new account hasn’t been verified within about two days, we send one reminder to that address with a link to verify it. If it still isn’t verified 24 hours after that reminder, the account is deleted. An unverified account can’t be signed into, so it holds nothing but the address and sign-up date.

The anonymous usage counts in §2 are kept as daily totals, which contain nothing about any individual. The short-lived codes used to tell visitors apart are deleted within two days.

8. Your choices and rights

Without an account there is still nothing for us to look up — the only record of your visit is an anonymous count that cannot be tied back to you. If you do have an account, you can:

See and delete your cloud projects at any time from inside the app.
Delete your account, and everything stored with it, by emailing support@enkava.com from the address on the account.
Ask for a copy of the personal information we hold, or ask us to correct it, at the same address.

Depending on where you live you may have additional rights over your personal information — such as access, correction, deletion, or objecting to certain processing. We honour those requests regardless of where you live; just ask. The local data Enkava stores in your browser is entirely under your control and can be cleared at any time through your browser’s settings. Records tied to a tip are held by Stripe as the payment processor; contact us and we’ll help where we can.

9. Changes to this policy

We may update this policy from time to time. When we do, we’ll revise the “Last updated” date at the top, and for material changes we’ll note it on the site. Continuing to use Enkava after an update means you accept the revised policy.

10. Contact

Questions about this policy or your privacy? Email support@enkava.com.