Privacy
What ravl stores, for how long, and who else sees it.
Who we are
- Ravl is made and run by Debargha Bhadra, in India. If you have a question or a concern about your data, you can write to [email protected] or use the contact page. That's also our grievance contact, and we'll reply within 30 days.
What you run
- The code and input you run, and the recording of the run, are stored so the run can be replayed.
- Without an account, runs are deleted after 7 days, and runs you shared after 30 days.
- With an account, runs are deleted after 30 days unless you save or share them. Saved runs (up to 50) stay until you remove them, and runs you shared are kept.
- You can delete your own runs. A deleted run disappears from your account and any link to it stops working, but we keep a copy for up to 30 days, and administrators can still read it until it is removed.
- A shared link can be opened by anyone who has it. Don't share runs containing anything private.
- Database backups are kept for 14 days, so deleted data can remain in them until they expire.
- ravl's administrators can see every stored run, including its code and input, and which account it belongs to. We do this to help you, understand how ravl is used, make it better, fix problems and stop abuse. Runs made without an account show no name or email, though anything you wrote in your code is visible. Every time an administrator opens a run or an account, it is logged.
- Your code is stored unencrypted. Don't run anything secret.
- We also keep technical details of each run, like how long it took and how much memory it used.
Bug reports
- A bug report stores what you write, your email if you give it, and the page, browser, language, step and view on screen. If you're signed in, it's linked to your account.
- Your code and input go along only if you tick Attach this run on a run of your own (or one made without an account). We keep a copy with the report so we can look into it, even after the run itself is deleted. If you report someone else's shared run, we link to it instead of copying it, so it goes away when they delete it.
- Administrators read bug reports to fix problems, and use your email only to ask about your report. Reports are deleted after a year.
Messages you send us
- When you write to us from the contact page, we get your name, email, subject and message (and your account email if you're signed in). It reaches us by email through our email provider, and we keep it for up to a year so we can help you.
Your account
- You can delete your account from your dashboard. Your runs, saved runs and shared links stop being available right away, and your data is deleted within 30 days: your runs, email and sign-in. Until then administrators can still read your runs, and you can restore the account by signing in, or ask us to. Any bug report you sent keeps only what you wrote, without your email or code. See the account deletion terms.
- Accounts are optional. Signing in stores your email address, and your name and picture if your sign-in provider (GitHub or Google) gives them.
- Administrators can see accounts, including their email, activity and runs, and can give credits, suspend, delete or restore them. Each of these is logged.
- Sign-in is handled by Supabase, which also hosts our database.
- We keep a short record of your sign-ins (when, the kind of browser and a hashed network address) and of your credits, for 90 days, to keep accounts secure and limits fair. Administrators can see this too.
Reported links
- If you report a shared link, we keep the report so we can look into it, and delete it within a year.
Emails
- We send the emails your account needs, like sign-in links and account notices. Product updates and beta invites only if you tick the box for them; you can stop them any time.
Your data, your choice
- Want a copy of your data, or something corrected or deleted? Just ask from the contact page and we'll sort it out within 30 days.
Age
- Ravl is for people aged 18 and over. If you're younger, you're welcome too, with a parent's or guardian's permission. A parent or guardian can ask us to delete their child's account at any time from the contact page.
Daily limits
- To enforce daily run limits without an account, your browser keeps a random ID, and we store a salted hash of that ID and of your IP address, not the address itself. The ID identifies nothing but your browser. Administrators can see the runs made from one browser or network, by these hashes only, and can block one to stop abuse. Each time they look or block, it's logged.
Error reports and usage statistics
- We may use Sentry to learn about crashes. Reports never include your code, input or account details.
- We may use PostHog to count how the product is used: pages opened, runs started and finished, examples opened. It uses no cookies, and never receives your code or input.
- Bot checks on anonymous runs may use Cloudflare Turnstile, which is run by Cloudflare.
- Sign-in codes and contact messages are sent by email through our email provider.
- Ask AI is switched off, so your code is not sent to any AI provider. If we turn it on, this page will first say which provider receives what.
Cookies and browser storage
- Signing in uses a cookie to keep you signed in. Your browser also remembers your theme, layout and view choices, and the random ID described above. We use no advertising cookies, and we don't sell your data.