R3al Home

Privacy Policy

Last updated 2026-10-03.

Who makes R3al

R3al is made by one person, Vjatseslav Totski, based in Estonia. Write to info@etorn.ee for anything about this policy.

Camera and microphone

The camera and microphone are processed on your phone, in real time, to draw the effect you built. Neither the video feed nor the audio leaves your device. The only still images that reach our server are the preview of an effect you publish and, while you are signed in to an account, the thumbnail of each draft.

Photos, video and files

A photo or video you shoot is saved straight to your phone's gallery. For a Movie File In node, the app keeps a link to the file you pick, or a copy in its own storage when the picker gives no lasting access, so the file keeps playing after you close the picker. The file is never uploaded, not even with a draft kept in your account.

Your account

The current version of R3al publishes only from an account. The account holds your email address, the account name shown with your effects, a salted scrypt hash of your password, when the account was created and last changed, and which version of the terms you accepted and when. The password itself is never stored. Your email address is not shown to other people.

Each phone you sign in on gets a random token, and the server keeps only its hash. Like the app's settings, the token can end up in your Android backup. Signing out ends the session on that phone, and changing or resetting the password ends the sessions on all your other phones.

Email

You sign in with your email address. Apart from replying when you write to us, R3al writes to it only to send a confirmation code: when you register, when you reset the password, and when you change the address (the code then goes to the new one). There are no newsletters. Zoho Mail (Zoho Corporation, EU data centre) sends the codes on our behalf, so Zoho receives your address and the message with the code. A code works for 15 minutes, and the server keeps only its hash.

Publishing an effect

Publishing sends the effect's graph, its name, your account name, a preview image, and the time, plus what you fill in on the effect's edit screen: the description (“Info / Instructions”), the pack you put it in and its tags. All of it is visible to anyone using the app or browsing the site. On our server, the effect is also linked to your account.

Drafts

While you are signed in, your drafts are also kept in your account on our server, so they come back when you sign in after reinstalling the app or on another phone. A draft is anything unpublished that is kept on the phone. The server gets the draft as the phone keeps it: the graph, the title, what you typed on its edit screen, the identifiers and times the app uses to match copies on different phones, and, for a draft made from a published effect, that effect's name. Its thumbnail goes too. The thumbnail is a frame of the effect taken while the draft was open, so it can show what your camera saw. When you sign in, drafts made on the phone without an account are added to your account too.

No other user can open the drafts in your account, and they never appear in the library. Deleting a draft while you are signed in removes it and its thumbnail from the server as well. What stays there is the draft's identifier and the time it was deleted, so that your other phones delete it too. Deleting the account deletes all its drafts. Signing out leaves the drafts both in the account and on the phone.

Without an account

Older versions of R3al can still publish without an account. When such a version registers a display name, which it asks for before the first publish at the latest, the server gives the phone a random token. The server keeps a hash of the token, never the token itself, along with the display name, when the identity was made and which version of the terms it accepted. This token and name are the phone's identity. The token stays on the phone and can end up in your Android backup, so a restore brings the identity back. A recovery code, if you asked for one, is also kept as a hash. Signing in to an account on a phone with such an identity moves its effects into the account and deletes the identity.

Reports

Reporting an effect or an author sends the reason, any text you add, and what it concerns. If you were signed in, the report is filed under your account. A report from an identity without an account is filed under a hash of its token, not the token itself. A report sent with neither keeps a one-way hash of your network address instead, used only to tell repeat reports apart.

Crash reports

If the app crashes, it sends a report the next time it starts: the app version, your phone's make and model, the Android version, and the crash itself. Nothing in a crash report identifies you, and you can turn this off in Settings.

Update log

Only the version of R3al downloaded from our own site checks for updates itself, and it logs how that went: the versions involved, your phone's make and model, the Android version, which step the update reached, and certificate hashes if it was rejected over a signature mismatch. This log is not linked to your account or identity.

Camera report

Settings has a button to send a report about your phone's cameras, for diagnosing dual-camera support. It only sends when you press it: the app version, your phone's make and model, the Android version, what the cameras can do, some speed measurements, and a hash of your token.

Vision models

The Background, Face Track, and Hand Track nodes need a model file each. Those download from the same server the library lives on, the first time you use one of them.

Where this runs

The server is in Germany, hosted by netcup. Requests normally pass through Cloudflare, with a fallback route through Vercel if your network blocks the main address. Both pass each request on to the server, so they handle what it carries, your device's IP address included. Zoho Mail sends the confirmation codes. We pass data to these companies only so that R3al can run. R3al carries no advertising and no third-party analytics, and does not sell your data.

How long we keep things

A published effect stays on the server until you delete it, on its own or together with your account. That includes an effect a moderator has removed, which only you can still see. An account stays until you delete it, and so do the drafts in it, unless you delete them sooner. A confirmation code works for 15 minutes. Diagnostic logs are capped by size: once a log passes 5 MB, its older half is dropped.

Your rights

You can see and delete what R3al holds about you: in the app, on the delete-account page, or by writing to info@etorn.ee. In the app, the Profile screen shows your account's email address and name and how many effects and drafts it holds. You can change the name, the address and the password there. You can object to processing that relies on our legitimate interest, and you can complain to Estonia's data protection authority, the Andmekaitse Inspektsioon. Processing rests on performing the service you asked for (your account, the drafts in it and the shared library), our legitimate interest in crash reports and moderation, and your consent wherever we ask for it.

Children

R3al is not directed at children under 13, and we do not knowingly collect data from them.