Privacy Policy

This policy explains what personal data CertifyQR collects, why, where it is kept and for how long, and what you can do about it. It covers the CertifyQR app for iOS and Android and this website, certifyqr.app.

The English and Russian versions of this policy are equivalent versions of one document.

Who is responsible

CertifyQR is run by Yury Hryshchanka, a private individual in Belarus, who decides how the data described here is used. You can reach him at yu.hryshchanka@gmail.com or on Telegram at @GrishchenkoYuriy.

What we collect

When you use the app:

• Your account. The name, email address and profile picture that Google or Apple share when you sign in, and the identifier Firebase Authentication assigns to you. If you use Apple's Hide My Email, we receive a relay address instead of your real one.
• Your organisations. The organisations you create or join, your role in each, and a record of who joined, left or was removed and when.
• Certificates. Every certificate created in an organisation you belong to, with its title, validity dates and status, and a history of every change with who made it and when.
• Purchases. Which plan or pack was bought, until when it is valid, whether it renews, and the transaction identifiers Apple or Google send us. We never receive card details.
• A purchase identifier. A random identifier we create for your account and pass to Apple or Google with each purchase, so the purchase can be matched to your account. It says nothing about you.

Data you enter about other people. A certificate's title is free text written by the organisation that issues it. If it includes a client's name or phone number, that information is stored with the certificate. The issuing organisation decides what goes into it and is responsible for having the right to record it.

When you visit this website, our server records each request in an access log: your IP address, the page requested, the time, and the headers your browser sends with it, such as its user agent, its language and the page you came from. The website sets no cookies and runs no analytics or advertising scripts.

Why we use it

• To sign you in and keep your account and organisations working. This is needed to provide the service you signed up for.
• To create, show and check certificates, and to keep their history, so an organisation can see who did what. This is needed to provide the service.
• To check your purchases with Apple or Google and apply what you paid for. This is needed to provide the service.
• To keep the service secure, investigate faults and prevent abuse. This is our legitimate interest in running a reliable service.
• To meet legal obligations, for example around refunds and accounting.

We do not sell personal data, use it for advertising or build profiles of you.

Services that process data for us

• Google Firebase Authentication handles sign-in. Google uses your IP address and device or browser details to protect sign-in against abuse.
• Sign in with Google and Sign in with Apple are run by Google and Apple under their own privacy policies.
• The App Store and Google Play process payments and subscriptions under Apple's and Google's own privacy policies. We receive the outcome of a purchase, never your payment details.
• The QR scanner. On Android it uses Google's ML Kit: scanning happens on your device and camera images are not uploaded, but ML Kit sends Google technical diagnostics such as the device model, the system and app versions and performance figures. On iOS, scanning uses Apple's frameworks on the device.
• A hosting provider runs the server that the app and this website use, and a storage provider keeps copies of the database.

These providers may process data outside your country, including outside Belarus and the European Economic Area. Where that happens, we rely on the safeguards the provider offers for such transfers, such as the European Commission's standard contractual clauses.

Where it is kept and for how long

Your data is stored on a server we rent and operate.

• Account, organisation, certificate and purchase data: for as long as your account exists. After a deletion request, see the next section.
• Copies of the database are made before every update of the service and once a day. On the server we keep the most recent copies of each kind, ten at the moment, plus any copy not yet sent to the separate storage. Copies in the separate storage are deleted after 90 days. When updates are rare, a copy made before an update can be older than 90 days.
• The website's access log: 14 days.
• The app server's logs record events such as the result of checking a purchase, with its transaction identifier. They contain no IP addresses and are overwritten as they fill up.
• Firebase Authentication keeps the IP addresses it records for a few weeks.

Deleting your account

The app does not have a delete button yet. Until it does, send a request as described on the contact page. We first confirm that the request comes from you, then within 15 days we:

• delete your sign-in account in Firebase Authentication;
• erase your name, email address and profile picture from our database;
• remove you from the organisations you are a member of, and close the ones you own.

What we keep, and why. Certificates and their history stay, because they belong to the organisations that issued them and clients may still hold them; they stop being linked to you by name. The record of who joined or left an organisation stays for the same reason, and the organisations you owned stay in our database, closed, under the names you gave them. Purchase records and your purchase identifier stay for refunds and accounting, linked to an account that no longer carries your name, email address or picture; Apple and Google keep their own records of the purchase, with the same identifier. If you are the owner of an organisation that still has members or active certificates, close it in the app first with the Delete organisation button: what happens to the certificates its clients hold is your decision, not ours. Your request waits until you do, and the 15 days start then.

Deleting your account does not cancel a subscription. Cancel it first in the App Store or on Google Play, otherwise the store keeps charging you.

Copies of the database are not edited. Deleted data disappears from them as they are replaced, as described above, and if we ever restore a copy, we apply every deletion made since it was taken.

Your rights

You can ask us what data we hold about you, ask us to correct it or delete it, object to how we use it, or withdraw your consent where we rely on it. Write to yu.hryshchanka@gmail.com. We answer within 15 days.

If you think we handle your data unlawfully, you can complain to a data protection authority: in Belarus, the National Personal Data Protection Center; in the European Union, the supervisory authority of your country.

Children

CertifyQR is a tool for businesses and is not meant for anyone under 16. We do not knowingly collect their data.

Changes to this policy

When this policy changes, the new version appears on this page with a new date. If a change significantly affects how we use your data, we will also tell you by email in advance, if we have your address.