Personal Data Processing Policy

Revision of October 29, 2026 · Русский

Translation from Russian. In case of discrepancy, the Russian text prevails.

This Policy has been prepared pursuant to Article 18.1(2) of Federal Law No. 152-FZ of 27.07.2006 “On Personal Data” and describes what information about you is received by the “Jeweler Calculator” app and the jewelercalc.ru website, why it is needed, to whom it is disclosed and how you can control this.

1. Who processes the data

The Operator is the right holder of the app and the website. The Operator owns the app, the website and the server on which they run, accepts payment for the Premium subscription, organizes the processing of data and responds to requests concerning it. Details of the Operator are given in Section 13.

For in-app purchases through Google Play or the App Store, the payment is processed by the app store, and for card payments, by the payment service Robokassa. Each of them processes your data as an independent operator under its own rules — see Section 5.

Hereinafter, “the Service” means the app and the website together.

Processing is carried out by mixed means — both automated and non-automated — and includes collection, recording, systematization, accumulation, storage, updating, retrieval, use, transfer in the cases described in Section 5, blocking, deletion and destruction.

2. What data is processed

Only the data without which the Service cannot work. The calculators and reference guide can be used without an account — in that case the Operator receives neither your email address nor any other information about you, apart from technical information.

When you create an account:

email address — which is also your login; it receives emails confirming registration, password changes and payments, as well as service notifications;
password — stored only as an irreversible hash; neither the Operator nor the database has the password itself;
interface language — the language in which emails are sent;
the date and revision of the documents you have accepted.

If you sign in with Google or Apple:

the identifier of your Google or Apple account — the Service uses it to recognise you the next time you sign in;
the email address provided by Google or Apple. Instead of your real address Apple may provide a private relay address — emails then reach you through it. The Service does not request or store your name from Google or Apple;
when signing in with Apple — the sign-in revocation key issued by Apple: when the account is deleted, the server uses it to tell Apple that sign-in to the Service has ended.

When the account’s Premium works on your devices:

the app installation number — stored only as an irreversible hash. On Android it is derived from the system device identifier, which is different for each app; on iPhone and computers it is a random string created by the app;
the device name — the phone model or computer name as reported by the system, and the platform (Android, iOS, Windows);
when the device was last used, and when it was added and turned off.

This information is needed so that one account’s Premium works on no more than three devices at the same time, and so that you can see the list and turn off an extra device. A device on which the subscription was taken out in an app store does not count towards this number: the store itself opens access on it.

When the app sends you notifications:

the device identifier for notifications (token) — it is issued by the notification delivery service, is tied to the installed app rather than to you, and changes when the app is reinstalled. The app sends it to the server only while you are signed in and notifications are on;
a hash of the app installation number, the delivery service (Firebase Cloud Messaging or RuStore Push), the store the app was installed from, and the app version;
notifications sent to you — title, text and a service link to a section of the app.

Reminders about orders in the diary are composed and shown by the app itself, on the device: they are not sent to the server. The desktop app receives notifications directly from the Operator’s server, without delivery services.

When you keep the order diary with a Premium subscription while signed in to an account:

order records — title, mode and status of the order, start and due dates, type of item and work, metals, weights and losses, stones, prices and payments, comment, reminder settings;
the list of craftsmen — first name, last name, position, phone, email address and comment that you have entered;
metal stock — metal receipts and consumption by order;
information about your customers that you enter in an order — name, phone, email address;
when each record was created, changed and deleted.

This information is stored on the server so that the diary is not lost when you change or lose your phone and is the same on every device where you are signed in. Photos attached to orders are not sent to the server and stay on the device where they were added. Without an account or without active Premium, the diary is stored only on the device and is not sent to the server.

Information about your customers and craftsmen. You determine its purposes and contents, so you are the operator of this data, and the Operator processes it on your instructions (Article 6(3) of Law No. 152-FZ): it only stores it, synchronises it between your devices and deletes it. The instruction and the obligations of the parties are set out in Section 7 of the Terms of Use. The Operator does not use this data for its own purposes, does not contact your customers, does not disclose it to anyone other than the persons in Section 5 who maintain the server, and does not view it except when you yourself ask for this in a support request.

If you used earlier versions of the app:

your login (email address), password hash and purchase information that were stored on the app’s previous server have been transferred to the new one so that you do not lose the access you paid for;
device identifier — a random string that the earlier version of the app created on your phone. It is used to transfer access paid for without an account to your account when you first sign in.

When you pay:

subscription information — the plan, payment method, status, access end date, whether auto-renewal is enabled and at what price, and service identifiers in the payment service or app store;
for card payments — payment information: amount, date, success or failure status, invoice number, and the email address to which the receipt is sent;
consents to automatic charges — date, plan, amount, offer revision, the exact consent text and the email address at that time. Each consent is a separate record, so it is clear what exactly you agreed to before each charge;
for app store purchases — purchase information provided by the store: purchase and subscription identifiers, the product purchased, purchase, renewal and expiry dates, renewal, cancellation and refund status, store country, price and currency.

Bank card details are not transferred to the Operator and are not stored by him: they are processed by Robokassa, the app store and the bank. Nor does the app store transfer to the Operator your name, email address or other information about your store account.

Technical information:

IP address, device type, operating system version and app version, date and time of requests to the server, service error records — including when the app requests metal prices;
app crash report — only in the Google Play build and only when the app has crashed: device model, operating system and app version, amount of free memory, the place in the program where the crash occurred, the time of the crash and a random installation identifier. The report contains no name, email address or account identifier. Where it is sent is described in Section 5.

What stays with you and is not transferred to the Operator:

calculations, calculation history, settings and files you open in the app — they are stored on the device;
photos of orders in the diary;
backup — if you have enabled it, the app saves it to a hidden folder on your Google Drive. You grant access to your Drive to Google yourself, the app sees only its own folder, and neither the access nor the contents of the backup reach the Operator’s server;
the 3D printer’s address and key — the app connects to the printer directly, at the address you have specified.

The Service does not collect or request:

your name, phone number or postal address;
identity documents;
precise location;
contact list, gallery contents or the contents of other apps;
biometric data.

The Service does not build a profile of your work: the database does not record which calculators you opened or what you calculated. Requests to the server remain in service logs for a short time but are used only for investigating failures. The Operator does not buy or collect information about you from third parties.

3. Why it is needed

to create an account, confirm your email and protect sign-in;
to provide access to Premium on your devices — on no more than three at the same time, verify purchases and keep records of the subscription, including auto-renewal;
to store the order diary in your account and synchronise it between your devices;
to transfer access paid for in earlier versions of the app;
to send emails about your account and subscription — email confirmation, password changes, reminders of an upcoming charge, notices that Premium was turned on for a new device;
to send notifications about your account and subscription to your devices — unless you have turned them off;
to respond to support requests and resolve disputes;
to comply with the law — issue payment documents and retain information about them;
to keep the Service running and investigate failures.

The Operator does not use user data for advertising, does not transfer it to advertising networks and does not sell it. Ads in the free version of the app are shown by the Yandex advertising network under its own rules — see Section 5; no ads are shown with a Premium subscription. The website contains no third-party advertising or analytics trackers.

No decisions producing legal consequences for you are made solely on the basis of automated processing.

4. Legal grounds

your consent — which you give in the app and upon registration, by a separate action (Article 6(1)(1) of Law No. 152-FZ); its text is the Consent to Personal Data Processing;
performance of a contract to which you are a party — the user agreement and the offer (Article 6(1)(5));
performance of obligations imposed by law — including issuing payment documents and retaining information about them under tax legislation and Federal Law No. 422-FZ of 27.11.2018 (Article 6(1)(2));
protection of the Operator’s rights in resolving disputes and violations (Article 6(1)(7));
the user’s instruction — for information about the user’s customers and craftsmen in the diary (Article 6(3)). The legal basis for processing it is ensured by the user as its operator.

5. To whom data is disclosed

Recording, systematization, accumulation, storage, updating and retrieval of personal data are carried out using databases located in the territory of the Russian Federation, as required by Article 18(5) of Law No. 152-FZ.

The following parties are engaged in processing — each on behalf of the Operator and only to the extent necessary for its task:

a Russian hosting provider — hosting of the server and database in a data center in Russia;
an email service on the jewelercalc.ru domain — delivery of service emails; an email contains your address and its text. Email is handled by the same Russian provider;
a Russian cloud storage service — database backups. They contain everything in the database, so the backups are kept in a separate private storage in Russia;
push notification delivery services — Firebase Cloud Messaging by Google, together with Apple Push Notification service by Apple on iPhone, and RuStore Push in the RuStore build. They receive the device identifier for notifications and the text of the notification; what exactly is sent and where is described below, in the paragraph on cross-border transfer;
Firebase Crashlytics by Google — collection of app crash reports from the Google Play build. It receives the crash report and the IP address of the device from which it was sent.

Providers are named only where your device connects to their servers directly: the delivery service when a notification arrives, Crashlytics when the app sends a crash report. Otherwise the role is named rather than the provider: the contractor may change, but the data available to it does not. The Operator will tell you on request who fills each role today — this is your right under Article 14 of Law No. 152-FZ.

In addition, data is received by independent operators that act not on behalf of the Operator but under their own rules:

the payment service Robokassa (ROBOKASSA LLC, robokassa.com) and the acquiring bank — accepting card payments and auto-renewals; they receive your email address, the amount and the receipt contents, while you enter your card details directly with them;
the Google Play and App Store app stores — processing in-app purchases. You make the purchase directly in the store, under your account with it and on its terms;
Google and Apple — signing in to the account with their account, if you choose to. You confirm the sign-in with them, on their terms;
the Yandex advertising network (Yandex LLC) — showing ads in the free version of the app. The advertising module built into the app itself transmits to Yandex technical information about the device, the advertising identifier, the IP address and ad impression data. On iPhone, the advertising identifier is available only if you have allowed it in the system prompt;
Google — if you have enabled backup to Google Drive: the backup is stored in your Google account under its rules;
the Federal Tax Service — payment information in the cases provided for by law.

The Robokassa payment page is not the Operator’s website, and it is governed by the payment service’s own documents, including its privacy policy. They are worth reading before you pay. The content of these documents is determined by the payment service; the Operator has no influence over them and does not control changes to them.

Likewise, the app stores, Yandex and Google process data under their own documents: the Google Privacy Policy, the Apple Privacy Policy and the Yandex Privacy Policy.

Cross-border transfer. It occurs in five cases, all described below. In none of them does the Operator transfer payment data, or an email address the recipient does not already have, outside Russia.

Verification of app store purchases. You make the purchase yourself, directly in the store, and the store receives the information needed for payment from you, not from the Operator. To confirm a purchase and check its status, the Operator’s server sends the store only the purchase identifier that the store itself assigned. The Google and Apple servers that respond to such requests are located outside Russia.

When you buy, the app passes the store the internal number of your account with the Operator — without your email address or name. The store returns it with the purchase information, and the Operator uses it to know which account a payment belongs to, including on renewal and refund.

Signing in with Google or Apple. If you choose this, the app receives a sign-in key from Google or a one-time code from Apple and passes it to the Operator’s server. To verify the sign-in, the server sends the key to Google and the code to Apple — that is, to whoever issued them. When the account is deleted, the server sends Apple the sign-in revocation key. The Google and Apple servers are located outside Russia.

Push notification delivery. To deliver a notification to your phone, the Operator’s server contacts the delivery service and passes it the device identifier — the same one that this service issued — and the text of the notification. For the Google Play build and on iPhone this is Firebase Cloud Messaging by Google; on iPhone it passes the notification on to Apple Push Notification service by Apple. The servers of both services are located outside Russia. For the RuStore build it is RuStore Push, which operates in Russia. A notification briefly reports an event in your account — for example, that your subscription will end soon; it contains no email address, payment details or diary records. The delivery service receives neither your name nor your email address. If notifications are turned off in the app or in the phone settings, the Operator’s server forgets the identifier and sends no notifications to the delivery service.

The app obtains the identifier itself, directly from the delivery service. In the Google Play build and on iPhone the built-in Firebase Cloud Messaging module contacts Google’s servers when the app starts — even without an account and with notifications turned off: this is how it issues and renews the identifier. Google then sees the device’s IP address and a random installation identifier created by the module itself; this request contains no account information. The identifier reaches the Operator only while you are signed in and notifications are on.

Crash reports. If the app from Google Play has crashed, on the next launch it sends a crash report to Firebase Crashlytics — a Google service whose servers are located outside Russia. The contents of the report are listed in Section 2; it contains nothing that would identify whose account it is, and the Operator cannot link the report to your account. Reports are needed only to find and fix the error. The RuStore and iPhone builds and the website do not send reports to Firebase Crashlytics.

Reference materials. Some images and files of the reference guide are downloaded by the app from Google’s Firebase cloud storage, whose servers are located outside Russia. No personal data is transferred there, but during the download your device connects to these servers directly, and its IP address becomes visible to them.

Data is disclosed to other parties only upon a request made in accordance with the law — to a court, investigative authorities and other competent authorities, to the extent prescribed by law.

6. How long it is all kept

the account and related information, including the subscription — for as long as your account exists; after deletion it is erased;
the order diary — for as long as your account exists, including after Premium ends: once you renew the subscription, you will find the diary intact. A deleted record stays in the trash for 30 days, where it can be restored, and then its content is erased. Only a service mark of the deletion remains — the record number, its type and time — so that the deletion reaches your other devices. When the account is deleted, the diary is erased from the server entirely;
incomplete registrations — where the email address was never confirmed — are deleted automatically after one week. Accounts transferred from the previous server are kept even without confirmation: the email is confirmed on first sign-in to the new version;
payment and purchase information and consents to automatic charges — for the period established by tax legislation, but not less than 5 years, regardless of account deletion, though no longer linked to it;
records of accepted documents — the revision, the time and the email address at that moment — 3 years after termination of the contract, including after account deletion: this is the limitation period, and throughout it the Operator must be able to show exactly what you agreed to;
the device identifier for notifications — until you sign out of the account on that device or turn notifications off; on sign-out, when notifications are turned off, when the account is deleted, and once the delivery service reports that the identifier is no longer valid, and if the app has not been opened on that device for 90 days, the record is deleted;
notifications — the copy for the desktop app is kept on the server for no more than one day;
server service logs — no more than 30 days;
app crash reports — 90 days, after which Firebase Crashlytics deletes them itself;
correspondence with support — 3 years.

7. Your rights

Under Article 14 of Law No. 152-FZ, you have the right to:

find out whether your data is processed and obtain information about which data, where it came from and to whom it was disclosed;
demand that data be updated, blocked or deleted if it is incomplete, outdated, inaccurate or processed unlawfully;
withdraw your consent to processing;
delete your account together with its data;
appeal against the Operator’s actions to Roskomnadzor (the Russian data protection authority) or in court.

Write to support@jewelercalc.ru from the address registered to your account. You will receive a reply within 10 business days; if the request is complex, this period may be extended by no more than 5 business days with notice of the reasons.

The Operator cannot change or delete data processed by the payment service, the app stores, Yandex and Google as independent operators — please contact them directly with such requests.

If you are a customer of a jeweller who keeps a diary in the Service, your data in it is processed by that jeweller, and requests about it should be sent to them. The Operator cannot find out whose diary you are recorded in without looking through other people’s diaries, and does not do so. A request that reaches the Operator and names the user concerned will be forwarded to that user.

8. Withdrawal of consent

Consent is withdrawn by an email to the same address. Some data is processed not on the basis of consent but in order to perform the contract with you — and without it the account cannot work: there would be no way to recognize you at sign-in or to provide the access you paid for. Therefore, withdrawal of consent also means termination of the contract: the account is deleted and processing stops — except for what is listed in the next paragraph.

After consent is withdrawn, the Operator may continue processing some data without it where the law expressly permits: payment information is retained to meet tax obligations, and records of the contract and accepted documents are retained for the limitation period to protect the parties’ rights in a dispute. Everything else is deleted.

Deleting your account does not cancel a subscription purchased in an app store: its auto-renewal is cancelled in the subscription settings of your store account.

Deleting the app itself from your phone does not delete your account: the account data remains on the server. You can delete your account in the app — “Settings” → “Account” → “Delete account”, in your personal account on the website or by email to the same support address. What is deleted and what the law requires to be retained is described on the Account deletion page.

9. How data is protected

the connection to the server is encrypted; requests over an insecure protocol are rejected;
passwords are stored as irreversible hashes;
the diary is available only with your account’s sign-in key: the server returns records only to their owner;
the account sign-in key is stored on the phone in the system’s secure storage;
access to the database and the admin panel is restricted and protected by separate accounts;
backups are stored in the Russian Federation and protected on a par with the main database;
the Operator keeps records of storage media, determines who has access and assesses the harm that may be caused to data subjects.

No method of transmitting or storing data provides a complete guarantee. If a breach does occur, the Operator will notify Roskomnadzor within the time limits set by Article 21(3.1) of Law No. 152-FZ and will inform the affected users.

10. Website, cookies and local storage

The jewelercalc.ru website does not use third-party trackers, advertising or analytics services. Fonts and styles are loaded from the website itself.

The browser keeps your account sign-in key and email address in local storage so that you are not asked for your password on every page. This is a technical necessity; clearing the website’s data in the browser removes it, but then you will have to sign in again.

11. Age

The Service is intended for persons over 18 years of age and does not knowingly collect data from minors. If it turns out that an account was created by a child, it will be deleted together with its data. If you notice such an account, please let support know.

12. Changes to the Policy

Each revision is published on this page and kept in the archive at a permanent address — you can always see what was in effect previously.

If changes affect the data processed, the purposes of processing or the parties to whom data is disclosed, the app will ask you to accept the new revision. Minor edits — typos, clarifications of wording — do not require consent.

The Russian text of the Policy prevails. This English version is a translation provided for convenience.

13. Contacts

The Operator is Aleksandr Valerievich Pankratov, payer of the professional income tax (self-employed). For any questions about data processing, write to support@jewelercalc.ru.

Revision of October 29, 2026.