Privacy notice

What we collect, why, and how you stay in control.

Who we are

RepoLantern is operated by AELSHA INNOVATIONS OPC PRIVATE LIMITED (AELSHA™), which is responsible for the personal data described here.

What we collect

• Your account: your sign-in e-mail address and name from your sign-in provider.
• Your guides: the guides, questions and answers you create, the repository address, and cost and usage figures.
• Security records: an audit log of actions, with your IP address and details encrypted under a key specific to you.
• Visits to this website, only if you agree: see Analytics on this website.

What we never keep

Your model API keys and private-repository access tokens are never stored. Repository source code is read to write your guide and is not kept afterwards. What is kept: the guide itself, short summaries of files (reused so that a later guide for the same code costs less; for private repositories, only for you), and a list of file and function names used to check answers.

Who processes your data

The AI provider you choose receives repository text for your job, under your own account and their terms. Our hosting runs on Google Cloud and Firebase. For the readiness checklist, the names and versions of a repository's dependencies (never its code) are looked up in OSV.dev, the public PyPI and npm registries, and deps.dev (Google's Open Source Insights, which mirrors the PyPI, npm, Go, crates.io, Maven Central and RubyGems registries); for private repositories only if you agree. If you add a web-search key and agree, package names and versions (never code) go to the search provider you chose, under your own account. Operational tracing, when the operator turns it on, carries only names, counts and timings, never code, questions or answers. Its trace metadata is kept for 14 days in Arize Phoenix, which we run on Google Cloud; its database is at Neon, Inc. (Amazon Web Services, us-east-2, United States). A trace holds a job id, a pseudonymous account id, the repository's host, model names, token counts and timings.

Analytics on this website

If you agree, the public pages of this website use Google Analytics, a service of Google LLC, to count visits. Google processes this data for us and may do so in the United States. The RepoLantern app (under /app) never uses it. Nothing is sent to Google until you choose Accept in the bar at the bottom of the page. If you choose Reject, or choose nothing, your browser requests nothing from Google.

What it collects: the pages you view, the page you came from, an approximate location worked out from your network address, your device and browser, and how long you engage with each page. Google Analytics 4 does not log or store IP addresses. Google signals and ad personalisation are off, so the data is not linked to a Google account and is not used for ads.

Cookies: Google Analytics sets two cookies on this site: _ga, to tell browsers apart, and _ga_<container-id>, to keep the state of a visit. Google's default lifetime for both is 2 years (Google's list of Analytics cookies); we set them to expire after 13 months. Your choice itself is kept in your browser for up to 13 months; then we ask again.

How long Google keeps it: data that can be tied to one browser (each visit's events and the _ga identifier) is deleted after 2 months, the shortest period Google Analytics offers. Google keeps only totals, such as visits per page or per country, for its standard reports (Google's data retention).

How to withdraw: choose Cookie settings at the bottom of any page, then Reject. Google Analytics stops at once, its _ga cookies are deleted, and it does not load again.

Product and AELSHA™ news e-mails

If you tick "E-mail me about AELSHA™ products" when you sign in, or turn it on in Settings, AELSHA INNOVATIONS OPC PRIVATE LIMITED (AELSHA™) may e-mail you about RepoLantern and other AELSHA™ products. It is your choice: the box starts unticked, and saying no changes nothing else in RepoLantern.

What we use: your e-mail address and name; when you signed up; when and where you agreed (at sign-in or in Settings) and the exact wording you saw; and a short activity summary: the dates of your first finished guide and latest activity, how many guides you finished, and which model providers you used. We use it only to decide which news is relevant to you. We never use your repository addresses, code, questions or answers for this.

How to stop: turn it off in Settings at any time, in one click, as easily as you turned it on. After you stop, you are left out of every list we make from then on.

How long we keep it: each yes and no, with its time, place and wording, is kept while you have an account, so we can show what you agreed to. When you erase your data in Settings, the whole record is deleted.

Questions or complaints: write to support@aelsha.com or security@aelsha.com. We answer within 90 days at most. You may also complain to the Data Protection Board of India.

How long we keep it

Guides are kept until you delete them. Operational records are pruned automatically. When you erase your data, it is deleted, and the key protecting your audit entries is destroyed. Copies can remain for a short time in backups: the database backup keeps 24 hours of history, older backup copies are removed when the service restarts once they are 7 days old, and deleted files can be recovered by us for 7 days before they are gone. Long-term cost records keep amounts, models and dates without your identity. Erasing your data doesn't delete your sign-in account (your e-mail address with our sign-in provider); write to us to remove it too.

Your choices

Delete any guide, or erase everything from Settings at any time. For questions, contact AELSHA INNOVATIONS OPC PRIVATE LIMITED (AELSHA™) at security@aelsha.com.