Personal data policy

1. Controller and scope

Individual entrepreneur Skrybykin Nyurgun Gavrilovich, INN 143525314628, OGRNIP 325140000060559. Contact: skrybykindev@yandex.ru. This policy covers budget.dojdu.com, the Budget Android app and server synchronization. It applies to visitors, users, shared-budget participants and people contacting support.

2. Data and purposes

Data comes from you, your device and your chosen sign-in provider.

• Sign-in and recovery: email, nickname, provider identifier, password hash, session information and recovery tokens.
• Financial records and sharing: accounts, transactions, amounts, currencies, categories, plans, goals, notes, photos, budget membership and permissions.
• Support and security: messages and attachments, sender contact, installation, device and session identifiers, platform and technical error information.
• Subscriptions: internal user and family identifiers, product, purchase and invoice identifiers, amount, currency, period, payment and renewal status, and confirmation of purchase terms. The app does not collect card numbers or CVV.

Processing necessary for requested features relies on entering into and performing the user contract (Article 6(1)(5), Federal Law No. 152-FZ). Legal obligations and protection of rights rely on Article 6(1)(2) and (7), subject to the user's rights. Optional processing needs its own lawful basis. Where consent is required, it is separate: this policy, sign-in and “Got it” do not replace it.

3. Storage and security

Android local mode keeps financial records on your device. Synchronization sends records and photos over HTTPS. Web works with the server; your browser can retain preferences and drafts. The server is hosted in Moscow, Russia, by JSC Selectel.

Server access is limited by membership permissions and operational need. Passwords are stored as hashes. Android uses SQLCipher for the database and OS secure storage for its key and session token; separate photo files are not protected by that database encryption.

4. Access and service providers

Shared-budget participants see records and materials according to their permissions. You need a lawful basis to provide another person's data. Do not upload passwords, complete card details or special-category data, such as health or intimate-life information. Photos are not used for biometric identification.

Configured sign-in providers can include Yandex ID, VK ID, Apple and Google; their own policies apply on their services. RuStore processes subscription payments and receives app-user and purchase-intent identifiers, not budget records or photos. Contractors receive access within their tasks under applicable processing and confidentiality requirements; ask the controller for details. Government authorities receive data where legally required.

Android uses Yandex Mobile Ads; the website uses the Yandex Advertising Network. To display, select and measure ads, Yandex may process advertising and technical identifiers, cookies, IP addresses, device, browser and network information, visited pages and ad interactions under its privacy policy. We do not pass financial records, photos or account and shared-budget identifiers in ad requests; page-text collection for web ad targeting is disabled. The Android SDK starts only with separate permission; withdraw it in Settings → Ads with “Do not allow ads”. SDK access to device geolocation is disabled.

Web ads load only after the separate “Allow ads” choice. You can choose “Without ads” and continue using the website. Withdraw permission with “Disable ads” in the Ads section of settings: new advertising requests from the website stop after the page reloads. The ad unit does not load while a subscription with the ad-free feature is active. Russian localization and cross-border-transfer requirements under Articles 18 and 12 of No. 152-FZ apply regardless of the selected advertising or sign-in provider.

5. Cookies and browser storage

Web uses necessary session and external sign-in cookies. They are HttpOnly and Secure on the production HTTPS site. The session cookie lasts until session expiry and is removed on sign-out; the external sign-in cookie lasts until sign-in completes or at most 30 minutes. Yandex's advertising code loads separately, with your permission, and may use its own cookies and other identifiers.

Your browser also stores language, theme, navigation, unfinished forms, photo drafts, notice dismissal and your ad choice. Withdrawing permission does not remove previously created Yandex cookies; manage them in your browser. Clearing site data removes preferences and unsent drafts, not your server account. Blocking necessary cookies may prevent sign-in. More about cookies.

6. Retention and deletion

Account data is needed while you use the features. Technical records, support messages and payment information are retained within their purposes and applicable legal obligations. Continued retention needs a lawful basis; backups do not permit indefinite storage.

Delete your account after sign-in in Privacy and data settings. Sign-in methods, sessions and your personal account are removed; a sole participant's whole budget and related photos are deleted. Shared records remain for others without the deleted author's name. Notes and photos may still contain personal data; ask the controller to review their retention, correction, blocking or deletion. Cancel active renewal before deletion; a shared-family administrator must transfer administration.

When a purpose ends or consent is withdrawn without another basis, data must generally be destroyed within 30 days, subject to Article 21 exceptions. If technically impossible, data must be blocked and destroyed within six months unless law provides otherwise. These requirements also cover relevant copies; account deletion does not mean immediate erasure of every archive.

7. Rights and requests

You can obtain processing information and access your data free of charge, request correction, blocking or deletion where legally provided, withdraw consent for specific processing and complain to Roskomnadzor or a court.

Email skrybykindev@yandex.ru with your request and information identifying the account. Do not send your password or a full passport scan in your first message. The controller verifies identity before disclosing data or acting on an account; formal access requests follow Article 14(3) of No. 152-FZ.

Processing information is provided within 10 working days, extendable by up to five working days with reasons; confirmed inaccuracies are corrected within seven working days. Requests to stop processing follow Article 21: 10 working days, extendable by up to five, with statutory exceptions. Emailing consent withdrawal does not request deletion of the whole account; processing with an independent lawful basis may continue. Disabling ads does not delete your account. The separate account-data consent withdrawal command in settings starts account deletion and requires confirmation.

8. Updates

The current version and revision date are published here. Changing this policy does not automatically obtain consent for new processing purposes.