Creator programme data policy

1. Operator and scope

The personal data operator is the individual Panin T. R. Contact: noreply@timur-p.ru. This document covers applications and the creator programme portal, rather than budget entries, tasks or other couple data in the Мы app.

The programme uses the same Supabase authentication service as the app. The same email has a shared password. The programme login and browser session are stored separately: signing in to the portal does not automatically sign you in to the app, and signing out of the portal does not sign you out of the app. These are separate portals, rather than two independent Supabase Auth accounts.

2. Data we process and its purposes

• Email and authentication information: for signing in, account recovery and security. Supabase Auth handles the password; the CRM does not store it as plain text.
• Name or platform name, Telegram contact, a social profile/channel/website link and an optional comment: for reviewing the application and contacting you about participation.
• Application status, decision and participation terms: for granting access after approval.
• Promo codes, anonymous labels for referred couples, confirmed purchases, refunds, rewards and adjustments: for statistics and reward calculations.
• Payout request amount and status, details for the selected payout method and payment confirmation: for processing and reconciling payouts.
• Document acceptance timestamps and versions, technical request and session information: for consent records and security.

Creators do not receive the names, emails, expenses, tasks or other personal records of referred couples.

3. Access and data storage

A creator can access their own portal. The programme administrator can access applications, contact information, terms, calculations and payouts to process them. Website data is transmitted over HTTPS. The frontend is hosted on Timeweb; a protected technical mirror on Vercel is also used. Authentication, the database, server functions and protected payout detail storage use Supabase infrastructure outside Russia. Requests may pass through the api.vdvoemwallet.com proxy.

Full payout details are stored encrypted using Supabase Vault; general lists show a shortened label. When processing a payout, the details are used only for the selected method and shared with the relevant payment participant when necessary for the transfer.

Cross-border storage limitations apply: Supabase data is stored outside the Russian Federation. If you do not agree to this processing, do not submit an application. You can contact the operator about data already provided.

4. Retention, deletion and withdrawal

The application and profile are used for review and participation. You can withdraw consent and request to end participation or delete programme data by emailing the operator from your registered email address. Specify that your request concerns the creator programme. Requests are considered within 30 days unless applicable requirements provide another period.

Records of rewards, refunds, adjustments, requests and completed payouts may be retained to fulfil obligations, reconcile calculations and meet legal requirements. Backup data disappears through backup rotation. Ending participation does not automatically delete calculation evidence or outstanding payout obligations.

Do not delete the shared app account to close only the programme: deleting the Supabase Auth account may end access with that email in both portals. Contact the operator to close only the programme.

5. Sessions and your rights

The programme browser session needed for sign-in is stored separately. Language and appearance preferences may be shared on the same website. Optional website analytics runs only after a separate cookie choice; accepting programme documents does not consent to promotional mailings.

You can request information about processing, correction, a copy or deletion of data, or withdraw consent. Email the operator and describe your request. We may need to verify account ownership to protect other people's data. Document changes will be identified by a new version and, where required, a separate confirmation in the programme.