Elucify

Privacy

Last updated 8 October 2026 · Terms

Who is responsible

Algorithmica Consultancy Ltd, trading as Elucify (registered in England and Wales, company number 12203791, registered office Office 408, Screenworks, 22 Highbury Grove, London N5 2ER, United Kingdom), is the controller of the personal data described here under UK data protection law. Contact: privacy@elucify.dev.

What we collect, and why

• When you sign in with Google: Google tells us your account's ID and email address, and whether the email is verified. We keep the ID (to recognise you next time) and the email (to contact you about your account); we don't get your name, contacts or password.
• When you continue without an account: no name, email or password; we create a random creator ID.
• Either way: your app (for example Claude Code) registers its name and the address it returns to, and we keep the tokens that let it act for you, stored only in a form that can't be turned back into the token. We use this to provide the service and to apply your limits.
• Your explanations: the title, scenes and narration text your AI assistant sends us, and the narration audio we generate from that text. Elucify doesn't talk to your AI provider; it stores only what your assistant sends. We use it to show the explanation to people with its links.
• Usage counts: how many minutes of narration you've used this month, and when an explanation was last watched (to know when its audio can be deleted).
• Measurement: events such as "explanation created", "link opened" and "seconds watched", with random IDs and the kind of link (private or share), so we can see whether Elucify works for people. These never include titles, content, links or tokens.
• Reports: if you report an explanation, the reason, any details you write and, only if you give it, your email address, so we can review the report and reply. Each report is also emailed to us.
• Your IP address: used briefly to limit how many requests one connection can make and to check the sign-in page isn't a bot. We don't keep a log of requests; error messages from the service, which don't include IP addresses or content, are kept for a few days to fix problems.

Our legal bases are providing the service you asked for, and our legitimate interests in keeping it secure, preventing abuse and understanding how it's used.

Cookies

When you open a link, the viewer sets one cookie that lets your browser watch that explanation for 24 hours. Signing in sets short-lived cookies (ten minutes) that make sure the sign-in finishes in the browser that started it. Signing in to your explanations page at elucify.dev/account keeps you signed in with a cookie for 30 days, or until you sign out. Continuing without an account sets a cookie, kept for 30 days, that lets you move what you made into a Google account later from the same browser. All of these are needed for the service to work, so we don't ask for consent. We use no advertising or tracking cookies. The sign-in page's bot check (Cloudflare Turnstile) may process information about your browser to tell people from bots.

Who processes it for us

If you choose it, Google signs you in and tells us who you are. Elucify runs on Cloudflare, which hosts the service and data, generates narration audio (Workers AI) and provides the bot check (Turnstile), under a data processing agreement. Cloudflare operates worldwide, so data may be processed outside the UK, with the safeguards UK law requires. We don't sell personal data or share it with advertisers. We may disclose information if the law requires it.

How long we keep it

• Narration audio: deleted 90 days after the explanation was last watched (30 days for explanations made without an account). The explanation then plays with captions.
• Explanations: kept until they are removed. There is no delete button yet; email privacy@elucify.dev with the link and we'll delete it.
• Sign-ins: end after a year, or after 90 days unused. Your Google account ID and email are kept while you use Elucify; email privacy@elucify.dev to have them deleted.
• Reports: deleted once dealt with. We keep a record that an explanation was removed or a report dismissed, with the reason chosen, but not what the reporter wrote or their email.
• Measurement events: kept in aggregate tools for up to about three months.

Links and previews

Anyone with an explanation's link can watch it. When a share link is posted in apps such as Slack, X, iMessage or WhatsApp, those apps fetch the title and preview image and keep their own copy, under their own privacy policies.

Children

You must be 13 or older to create explanations.

Your rights

You can ask for a copy of your data, or ask us to correct or delete it, restrict or object to how we use it. Because we don't know who you are, tell us the link or explanation ID so we can find it. Email privacy@elucify.dev. If you're unhappy with how we handle your data, you can complain to the Information Commissioner's Office at ico.org.uk.