Privacy policy

What we collect

When you create a character, Rukhanka processes the photo you upload, any style example images and description, the character name, your style and reaction choices, generated images and animations, and the records needed to complete and support the order. Uploading a photo may include personal information about the person depicted.

A private browser session links your creations and purchases. For Plata by mono purchases, payment records include the invoice reference, purchased item, payment state, currency and amounts needed for order and refund accounting. Card details are entered on the bank’s payment page, not in Rukhanka’s forms. Hosting also processes IP addresses, browser details and error logs to serve and secure the service.

How your data is used and shared

Your photo, chosen style examples and description, and generation choices are sent to Google’s Gemini API to create the character and animations. Generated media may also be sent to that API to evaluate the animation. Google’s processing is governed by its Gemini API terms and privacy information.

Google Cloud and Firebase provide hosting, private file storage and order records. Rukhanka processes files there to remove backgrounds, prepare downloads, maintain your session and handle support. Plata by mono processes checkout information on the bank’s payment page. These providers may process information in other countries.

For any earlier purchase made through Paddle, use the support link in its receipt or contact Paddle buyer support.

Your uploaded photos and creations are not placed in a public gallery. Access to the creator’s files requires your signed-in profile, the guest browser session associated with the order, or its private recovery key. Once guest creations are linked to a profile, their former guest cookie and recovery key no longer grant access. Downloads use private signed links that expire after 60 seconds; anyone holding such a link can use it until it expires.

Telegram receives the exported sticker files only when you choose Add to Telegram, never your original photo. Anyone with the set link or one of its stickers can open the published set. Later reactions are added to that set; chosen versions replace the corresponding stickers. A refund removes only stickers belonging to that purchase. Deleting a creation in Rukhanka does not delete its Telegram set; contact support for removal.

Your profile

If you choose Google sign-in, Rukhanka verifies the Google sign-in credential on the server and stores your Google account identifier, verified email, display name and profile image address. These identify your profile and associate your saved characters and purchases across devices. You can edit your display name and sign out; signing out revokes that Rukhanka session. We do not store the Google login token. Contact us to request removal of your profile.

Cookies and local storage

A necessary session cookie keeps your creations associated with this browser. It expires after 30 days unless renewed. Your recovery key can restore access for 365 days from when it was issued; keep it private.

A draft containing your photo, style examples, description and choices can be saved in this browser’s local database so you can continue an interrupted checkout or submit a paid creation. The draft is removed when the creation is successfully submitted or you explicitly sign out. Clearing site data removes locally saved drafts and may remove access unless you saved a recovery key.

The creator does not currently load advertising analytics. The Plata by mono payment page has its own storage and privacy practices.

Retention and deletion

When character previews are available before payment, only a reduced-resolution image with a baked-in watermark is shown. Originals and animations require payment. Preview access expires after the configured lifetime, usually 24 hours; expiry does not automatically delete privately stored source files. A preview linked to checkout may require support to remove safely. Hashed IP information and preview admission records help limit abuse and generation costs.

Uploaded and generated media remain available in active service storage until you delete the creation or request deletion. Use Delete in My creations for a finished or stopped creation. A running or unresolved generation may need to finish or be reviewed before deletion can complete.

Deleting a creation removes its active uploaded and generated files. Google Cloud Storage retains deleted files for seven days through soft deletion. Firestore point-in-time recovery retains earlier database versions for up to seven days. Deleted information may remain in these recovery copies until their retention periods expire. Minimal order, transaction and deletion records remain for accounting, security, refund handling and legal obligations. Deleting files in Rukhanka does not itself delete records held independently by monobank, Google or Paddle (for any earlier Paddle purchase).

Your requests

You can ask about, access, correct or request deletion of your information through the contact below. Depending on your location, you may have additional rights, including a right to object to processing or complain to a data-protection authority. We may need to verify that a request relates to your order.

Service operator: Ivan Habor
Privacy contact: hello@ivanhabor.com