Privacy policy
Last updated: 28 October 2026
1. Who is responsible
Rigsy is a private, non-commercial project run by an individual based in Lithuania (the “controller” under the EU General Data Protection Regulation, GDPR). Contact for anything about your data: [email protected].
2. What we process and why
| Situation | Data | Purpose and legal basis | Kept for |
|---|---|---|---|
| Visiting rigsy.dev | IP address, time, requested page, browser type (server log) | Running and securing the site — legitimate interest, Art. 6(1)(f) GDPR | 14 days |
| Your account (studio.rigsy.dev) | Google account ID, email address, name, account creation time, sign-in sessions, invite code you used | Providing your account — Art. 6(1)(b) GDPR | Until you delete your account; sessions expire after 30 days |
| Generating on Rigsy Home | Prompts and generated images | Producing what you asked for — Art. 6(1)(b) GDPR | Images: 7 days, then deleted automatically; prompts are kept only in the studio software's memory until its next restart |
| Connecting your own PC | PC name, its public SSH key, connection times; requests between you and your PC pass through Cloudflare and our server | Letting you reach your own PC — Art. 6(1)(b) GDPR. The traffic is forwarded, not stored; only the access log below is kept | Until you disconnect the PC or delete your account |
| Operator's private studio (app.rigsy.dev) | Email address, one-time code, time and IP of the sign-in | Keeping the operator's own tools private — Art. 6(1)(f) GDPR | Per Cloudflare's retention |
We do not sell data, show ads, build profiles or make automated decisions about you. Generations are not used to train models.
3. Cookies
The public pages set no cookies. When you sign in to the studio, it sets one cookie (__Host-rigsy) that keeps you signed in;
the operator's private studio uses Cloudflare Access's CF_Authorization cookie for the same purpose.
These are strictly necessary for the service you requested, so no consent banner is required for them (Art. 5(3) ePrivacy Directive). Signing out removes them.
4. Who else is involved
Google confirms your identity when you choose “Sign in with Google”; Google shares your account ID, email and name with us. How Google handles your data is described in Google's privacy policy.
Cloudflare, Inc. delivers the site, protects it from attacks and handles sign-in to the operator's private studio (Cloudflare Access) as our processor. Cloudflare may process data in the United States; such transfers rely on the EU–US Data Privacy Framework and Standard Contractual Clauses. See Cloudflare's privacy policy.
UAB “Esnet” (VPSnet), Vilnius, Lithuania, hosts the server that runs the accounts service and passes traffic on to Rigsy Home, as our processor within the EU.
The studio itself runs on the operator's own computer in Lithuania. The connection to it is end-to-end encrypted.
5. Your rights
You can ask for access to your data, correction, deletion, restriction of processing, data portability, and you can object to processing based on legitimate interest (Art. 15–21 GDPR). Download and deletion work directly in the studio's settings; for anything else write to [email protected]; we answer within one month.
You may also complain to the Lithuanian supervisory authority, the State Data Protection Inspectorate (Valstybinė duomenų apsaugos inspekcija), or to the authority in your own EU country.
6. Changes
If this policy changes, the date at the top changes with it.