Цифровий підпис Українська

Privacy policy

The Android app «Цифровий підпис» (com.stalkersoft.digitalsignature), version 0.1.0 and later until this version of the policy is replaced. Version of 16 November 2026. The Ukrainian text is the original; this is a translation.

In short. Your documents and keys never leave your phone. There are no accounts, ads or analytics. Only after you allow it, the app sends technical requests: certificate serial numbers to certificate status services, key identifiers to a certificate lookup service (over HTTPS), a hash derived from the document to a time-stamping service, and trust data requests to czo.gov.ua. These requests go to trust service providers and czo.gov.ua, not to us. We only receive e-mails that you choose to send to support.

1. Who we are

The app is developed by StalkerSoft (“we”). We decide which data the app processes and where it sends it, so we are the controller (володілець) of personal data under the Law of Ukraine No. 2297-VI “On Personal Data Protection”.

Controller
Serhii Soroka, trading as StalkerSoft
Privacy and rights
support@stalkersoft.com
Security
security@stalkersoft.com

2. What stays on your phone

The app works with your files on the phone. We have no server it could send them to.

Biometrics (fingerprint or face) are handled by Android; the app only learns whether the check passed. When you share a file, open it in another app, or upload it to the ЦЗО portal through a link in the app, that app or site handles the file under its own rules. If you print a PDF report, your selected Android print service receives it; the report contains signer and verification data but not the document itself.

3. What is sent over the network, and to whom

The consent screen with “Allow” and “Don’t allow” («Дозволити» / «Не дозволяти») opens before an online action for which the app has no current answer, rather than simply at first launch. Automatic requests do not run before an answer. After denial, you can allow one specific action without changing the stored choice. Without your permission the app sends nothing (the update check through Google Play is described in section 5). Documents, keys and passwords are never sent.

Certificate status check

What
The certificate’s serial number and data about its issuer (hashes of the issuer’s name and key). For a certificate revocation list (CRL), the issuer’s whole list is downloaded.
When
When signatures in an opened file are verified (as set under “Verification and network”); before every signature; and after the time stamp, to add long-term validation data to the signature. This includes certificates of other people whose signatures you verify.
To whom
The OCSP and CRL services of whoever issued the certificate: the qualified trust service provider (КНЕДП), or the Central Certification Authority (ЦЗО, czo.gov.ua) for the providers’ own certificates. For test certificates, the test services of the ЦЗО.
How
HTTPS where the service supports it; otherwise HTTP, not encrypted (section 4).
Why
To learn whether the certificate is valid. The status must be checked before signing; if it cannot be obtained, the app does not sign.

Looking up your certificate

What
Identifiers of your key. They are computed from the public key; the private key is never sent.
When
When you import a key whose file contains no certificate.
To whom
The certificate lookup service of the provider that issued your certificate.
How
HTTPS only. The answer contains your certificate (including your name and tax number) and also arrives encrypted. If the provider does not support HTTPS, the app offers to download the certificate from the provider’s website manually.
Why
To get the certificate for your key so that you can sign with it.

Time stamp

What
A hash (digital fingerprint) derived from your document and its signature. The document cannot be recovered from the hash.
When
Every time you sign.
To whom
A qualified time-stamping service: first the one named in your certificate, then your provider’s service, then other qualified services from the trust lists. For test certificates, the test service of the ЦЗО.
How
HTTPS where the service supports it; otherwise HTTP, not encrypted (section 4).
Why
To certify when the signature was made. The time stamp becomes part of the signature.

Trust data

What
A request for public files, with no data about you. The server sees only your IP address.
When
At your request, or automatically at process start and then daily while the app process runs, under “Always” and an allowed network. An unmetered-network wait does not survive the process ending.
To whom
czo.gov.ua, the Central Certification Authority of Ukraine.
How
HTTPS.
Why
To know the current providers, their certificates and service addresses.

Every recipient also sees the IP address of your connection and the time of the request; that is how any internet request works. None of these requests reach us. Trust service providers and czo.gov.ua process the requests they receive as separate controllers, independent of us, under their own rules.

How to control this

Settings → “Verification and network” offers online checks “Always”, “Ask” or “Never”, and mobile data on or off. If you have not chosen a mode, the default is “Always” with current recorded consent allowed, and “Ask” otherwise. Automatic checks and trust updates run only under “Always”. Under “Ask”, a manual action runs on its tap when stored consent and the network allow it. Under “Never”, after denial or on a blocked metered network, one specific action can be allowed separately. Signing always needs a status check and a time stamp; the online-checks mode does not remove that requirement. “Withdraw permission” stops current requests at once and keeps saved results.

4. What is not encrypted in transit, and why

Some OCSP, CRL and time-stamping services work over plain HTTP only, and the app contacts them that way. That is how these providers publish their services and how these protocols are normally used: their answers are signed objects, so the app checks the signature of every answer whatever the channel. These requests contain a certificate’s serial number and issuer data, or a hash derived from the document. They contain no name, tax number or document content. Where a service answers over HTTPS, the app uses HTTPS only.

Someone who can watch your network (for example, the operator of a public Wi-Fi network) could see which service you contact, which certificate’s status is checked, and the hash. They cannot recover a document from this, and they cannot alter an answer unnoticed, because the app checks its signature. Certificate lookups, trust data and anything that contains a name or tax number travel over HTTPS only. This is why the Data safety section on Google Play says that not all data is encrypted in transit.

5. What we do not do

The app is installed and updated through Google Play. To learn whether an update is available, it asks the Google Play app on the phone, which asks Google’s servers and passes on the app version and technical data about the device. If your phone is set to share usage and diagnostics data with Google, Google may show us aggregated crash statistics in Play Console, without documents, keys or names. Google handles that data under its own privacy policy.

6. Support e-mails

When you write to support@stalkersoft.com or security@stalkersoft.com, we receive your e-mail address, the message and any attachments; you send the e-mail with your own mail app. The diagnostics file you can share from Help in the app contains the app and Android versions, the device model and error codes, and no documents, names or keys. You choose its receiving app and recipient in the system share sheet. Nothing is sent to us automatically.

We use e-mails only to reply and to fix defects. We keep them for 12 months after the last message in the conversation and then delete them. Our mail is handled by e-mail services that process it on our behalf and may store it on servers outside Ukraine. Please do not send us key files, passwords or documents.

7. Legal basis

Under Article 11 of the Law of Ukraine “On Personal Data Protection”:

8. How long data is kept

9. How to delete data

We have no copies of the data the app sends to providers and czo.gov.ua, so the app has no separate way to request its deletion. For a provider’s records, contact that provider; the list of providers and their contacts is on czo.gov.ua.

10. How data is protected

11. Your rights

Article 8 of the Law of Ukraine “On Personal Data Protection” gives you, among others, the right to:

Write to support@stalkersoft.com. Most data is kept only on your phone, so you control it yourself (section 9).

12. People in the EU and EEA (GDPR)

Today the app is distributed in Ukraine only. This section takes effect when the app becomes available in EU and EEA countries; the EU General Data Protection Regulation (GDPR) then applies to your data.

13. Children

The app is meant for people aged 18 and over. We do not knowingly process children’s data. If a child has sent us an e-mail, tell us and we will delete it.

14. This website

digitalsignature.stalkersoft.com uses no cookies, analytics, scripts or external resources. It is hosted on Cloudflare Pages (Cloudflare, Inc.), which logs visitors’ IP addresses for security purposes.

15. Changes to this policy

A new version appears on this page with a new date. We will announce significant changes, such as new kinds of data or new recipients (for example, cloud keys in later versions), in the release notes on Google Play and in the app. If a change needs new consent, the app will ask for it.

16. Contact

Questions about data and rights: support@stalkersoft.com. Vulnerabilities: security@stalkersoft.com. We reply within 3 working days, and to requests about your rights within 30 calendar days at the latest.