RiggyTry it

Privacy policy

This page lists what the service keeps about you and where it goes, as the code does it today. Questions and requests: hello@riggyapp.com.

Your account

  • Your email address (it is your sign-in) and the display name you set.
  • Your password as a salted scrypt hash — the password itself is not stored.
  • When you signed up and last signed in.
  • How you first found the site: the referring site and the utm tags of your first visit, the page of ours you landed on, the last page of ours you read before signing up, and the invite code if you came by an invite link.
  • Your balance, every top-up and charge, and the Ethereum address issued to you for top-ups.

Your work

The PSD files and images you upload, the rigs built from them, previews and the chat with the model are stored on our server until you delete the project. A project you share is visible to the people you share it with.

The operator can open a project read-only to answer a support request or investigate a failure; each such view is recorded in the server log.

What is sent to AI providers

When you send a message, your message, the conversation so far, a description of the rig and small thumbnails of its parts are sent to the provider of the model your project uses — Anthropic, OpenAI, DeepSeek or Z.ai (Zhipu) — through their API, under their API terms.

When you press the Cut button on a flat picture, the whole picture (resized to at most 1536 px on its long side) and the list of parts to cut it into are sent to fal.ai, the service that runs the model that cuts it, under its API terms. Nothing is sent to it until you press the button.

When you press the button to paint in a hidden part or to generate a part, the picture of the rig at rest (at most about 1000 px on its long side), the part to paint in and your words for it are sent to Scenario (scenario.com), the service that runs the model that draws it, under its API terms. The pictures are uploaded to a Scenario project as assets and stay there. Nothing is sent to it until you press the button.

The text of your message — and only it: not the conversation, the rig or any pictures — is also sent to typesafe.ai, under its API terms, to classify what the message asks for. The answer is kept with the message and does not change what the model does.

Nothing is sent to any of them when you edit with the mouse, undo or export.

Logs

The server writes a log line for:

  • each request: the address, the status, your account name and a random visit id;
  • each turn: the text of your message, its duration, cost and token counts;
  • a few actions in the browser that the server cannot see otherwise — screens, play, file drops, errors. What you type is not recorded, only its length.

Logs are kept by our hosting provider, Railway, for about a week. There are no analytics or advertising trackers on the site, and fonts are served from our own server.

Support messages

Messages you send to support are stored with your account. The operator is notified of each one through Telegram, and the notification contains the text of the message.

Cookies and browser storage

  • One cookie: your session, so you stay signed in. It lasts 30 days.
  • Three records in your browser's local storage, kept up to 30 days: an invite code, the source of your first visit and the last page of this site you opened. Before you sign up they stay in your browser; signing up sends only the paths of our pages, the referring site without its query and the utm tags.

Payments

Top-ups are stablecoin transfers on Ethereum. Transactions on a public blockchain are public by nature. No card data is collected.

Your choices

You can delete any of your projects yourself. To get a copy of your data or to delete your account, write to hello@riggyapp.com or to support from your account. This policy changes when the service does; the date above says when it last changed.