PLIVEX · Version 2026-09-16
Privacy Notice
Information about Plivex’s website, training diary, cloud account and support.
1. Who is responsible
Plivex is operated by Igor Svyatoslavovich Ulanov (Уланов Игорь Святославович), an individual in Russia, who determines how the service processes personal information. Contact: plivexapp@gmail.com. Correspondence: Igor Svyatoslavovich Ulanov, Post Office 192077, 29 Slavyanskaya Street, Ust-Slavyanka, Saint Petersburg, 192077, Russian Federation. This is a correspondence address, not a statement of residence or a company registered office.
This notice explains processing; it is not blanket consent or a waiver of rights. Applicable regional requirements take priority regardless of the language you choose.
2. Creating an account
Email registration requires accepting the Terms and acknowledging the Privacy Notice. When you use Apple, Google or another available sign-in provider, a new account is created only after you choose Create account alongside the same links. Until confirmation, no account is created and guest records are not synced. Existing-account sign-in does not ask you to accept again. We record the date, registration method and document versions; this is not blanket consent to any processing.
3. Guest mode and cloud use
Guest entries are stored on your device. Signing in enables cloud synchronisation and associates existing guest entries on that device with your account. Changes are uploaded when synchronisation is available. Entries not yet synchronised from another device are not held in the cloud snapshot.
Technical requests, such as checking available sign-in methods or downloading compatible updates, can occur in guest mode. The website remembers your selected theme; it does not use optional advertising or analytics trackers.
4. Information, sources and purposes
| Information and source | Purpose |
|---|---|
| Your email, account and selected sign-in provider identifiers, email verification, password hash where relevant, protected session credentials | Create and secure your account, sign you in and recover access. |
| Your workouts, plans, templates, exercises, sets, repetitions, resistance weight, distance, duration, dates, planned and actual results, fatigue rating, notes and settings | Provide the diary, your training progress displays, saving and synchronisation. |
| Your chosen nickname and photo, file metadata | Provide and manage your nickname and optional profile photo. |
| Connection and device information, IP address, session information, country inferred from IP | Operate connections, secure access and determine regional sign-in availability; this is not precise GPS location. |
| Displayed notice version and time, actual operations and acknowledgements | Record information shown and execute requests reliably without duplication; not blanket consent records. |
| Your support email, message and chosen attachments | Handle the specific enquiry, rights request or reported violation. |
| Technical event counts, failures and timings | Diagnose operation and aggregate feature demand without using diary contents. |
5. Purposes and legal grounds
Where GDPR or UK GDPR applies, necessary ordinary account, diary and requested profile processing is based on providing the requested contract; specific legal duties support the corresponding compliance processing. Proportionate security and service reliability may rely on legitimate interests, subject to your rights. Required consent is used for processing that cannot lawfully proceed on another ground.
Special-category information needs an additional applicable condition. General acceptance of the Terms does not supply every required consent. We do not use workout notes for advertising profiles, medical inferences or model training, and do not make decisions producing legal or similarly significant effects solely by automated processing.
6. Your public profile
A neutral nickname is generated at registration. You can change it to a name of 1–50 characters; your legal name is not required. Adding a photo is optional, and you can replace or remove it. Your email address and authentication information are not public profile names. Signing in with Google or Apple does not automatically select their name or image for a new public profile.
Your chosen nickname and photo are public profile elements and may appear beside your publications when those features are used. Profile images have public URLs accessible without signing in, even without a shared workout link. An unlisted or hard-to-guess address is not private access control.
Removal queues the image for deletion from our storage, with retries during outages. A previously loaded browser image may remain until its cache expires; our normal image cache lifetime is up to five minutes. We cannot recall independent copies others have already saved.
We use ordinary profile information to provide the public profile you request, within applicable law. This does not license unrelated advertising, facial recognition or unrestricted reuse of your image or identity.
7. Recipients and service providers
Timeweb hosts our application servers, database, S3 objects and backups in Russia. Yandex 360 delivers account emails and codes. Google Gmail handles support correspondence. Technical providers and the operator access information only within the necessary task.
Apple and Google participate in your selected authentication method and app distribution. They also operate their own services under their respective notices. Expo delivers compatible application updates and processes related connection requests; the training diary is not sent as part of an update download.
We may disclose the minimum information required by a valid legal demand, to address a specific rights claim or as otherwise required by law. Chosen profile photos are readable through public URLs. Export archives require owner authentication.
We do not sell personal information or share it for cross-context behavioural advertising. We do not use diary contents for insurance, employment screening or unrelated AI training.
Where a configured interface offers Telegram sign-in and you choose it, Telegram supplies an identifier and sign-in verification information. Names and photos from social sign-in are not automatically published.
Igor Ulanov alone administers the Plivex infrastructure, database and support mailbox; there are no other Plivex support staff or database administrators. Timeweb, Yandex 360, Google Play and Expo accounts are held by the operator. This does not exclude processing by providers under their own service arrangements.
8. Locations and international processing
Our hosted diary infrastructure is in Russia. Apple, Google, Gmail, Expo and their service providers may process information in other countries under their own arrangements. We do not represent that all processing occurs in Russia or that Russia has an EU adequacy decision.
International disclosures subject to applicable transfer restrictions require an available legal mechanism and any required supplementary safeguards. You can contact the operator for the recipients, processing locations and safeguard information applicable to your request. A provider’s brand name or a general policy is not itself a transfer safeguard.
9. Retention
| Information | Retention |
|---|---|
| Cloud account and diary | While the account is used, until deletion or another lawful end to processing. |
| Registration confirmation | The date, registration method and document versions are kept with the account and erased when it is deleted. |
| Pending provider registration | Verified sign-in information is temporarily stored encrypted. A request is valid for 10 minutes; cancellation deletes a pending request. After completion, an encrypted result is available for up to 2 minutes to recover from a lost response. Expired records are removed by a cleanup task scheduled every minute; backups follow the periods below. |
| Ready export archives | 24 hours after completion; access then ends and cleanup removes the files. |
| Ordinary diagnostic logs | No more than 30 days, sometimes less through rotation. Synchronisation queues and operation acknowledgements are separate operational records. |
| Ordinary backups | No more than 90 days. A shorter applicable erasure deadline takes precedence; 90 days is not a blanket delay for rights requests. |
| Minimum deletion records | Account identifier and request date for up to 100 days to reapply deletion to backups no older than 90 days, without diary contents. The retry receipt is retained for 24 hours. |
| Support or specific dispute records | For the enquiry and an applicable mandatory period or documented need to address the particular claim; unnecessary attachments are removed. |
| Website theme | 180 days after your last change, or until you reset it. |
10. Export and deletion
Settings provides an export of a consistent cloud snapshot as ZIP archives containing CSV, JSONL and a contents description. Download every displayed part for the complete export. Preparation continues while the app is closed. Unsynchronised device changes are not included.
Account deletion removes owned active records and sessions, cancels export preparation and queues external image cleanup and Apple access revocation with retries. Other people’s independent records are not erased merely because the deleted user was the original author.
The requesting app clears that account’s local records after confirmed deletion. Ordinary sign-out, an expired session or a network error does not delete records. Other devices, downloaded files and phone backups need separate management. Before restoring service from a server backup, earlier deletions must be reapplied.
11. Fitness and health-related information
Do not use Plivex to store or publish diagnoses, medical records, test results or prescriptions. Normal training notes and supported fitness fields remain available. This restriction does not change how information is classified under applicable law or remove our duties concerning information actually received.
Apple Health and Health Connect are not integrated in this version. Some consumer-health laws nevertheless cover ordinary fitness activity or related inferences. The separate policy describes those categories and rights. We review specific violation reports without routinely reading every note or automatically removing medical keywords.
12. Your rights and requests
Contact plivexapp@gmail.com for access, correction, a copy, deletion, restriction, objection, portability or withdrawal of applicable consent. Rights and permitted exceptions depend on the law covering your processing. Withdrawal does not undo earlier lawful processing.
Identify your account and the requested action. You need not be able to sign in to contact us. We verify identity and an agent’s authority proportionately; do not send passwords, codes or unnecessary identity or medical documents. We explain a refusal or permitted extension and respond within the applicable deadline. You can complain directly to a competent regulator or court.
13. Security and incidents
We use protected connections, access controls, owner checks for private data, protected authentication credentials and limits on sensitive information in logs. Profile photos are intentionally public for reading, while modification requires authority. Where required, we notify relevant authorities and affected people of incidents within the applicable deadlines.
14. Young people and parents
Plivex serves a general audience, primarily adults and teenagers, and is not specifically directed to children. We do not set a single minimum age for all countries. Applicable law determines when a person may independently create an account and the safeguards required for processing a minor’s information. Store content ratings do not replace those requirements.
Ordinary use does not ask for a birth date, identity document or age checkbox. We do not claim this verifies age or obtains parental consent. If local law requires verified parental authorisation for your use, do not register or upload a photo before contacting plivexapp@gmail.com. We must establish a lawful route first; an unverified email from someone claiming to be a parent is not sufficient where verification is required. There is currently no built-in family account or automated parental-consent service.
You can keep the generated nickname and leave your photo empty. Choose a nickname without your school, address or contact details. Uploaded photos have public URLs; use a neutral picture if you do not want to show your face. Your diary is not automatically published. We do not sell your information, display advertising or profile you for advertising.
You or a parent or guardian may contact Igor Ulanov, who handles requests personally, about access, correction, deletion or unsafe disclosure. We verify the request and authority proportionately, respect a young person’s own rights, and do not disclose a diary merely because someone says they are a parent. If we establish that a child’s information is being processed without a required basis, we stop that processing and delete the affected information within applicable deadlines. Information about the request is limited to resolving it.
15. Version and changes
Version 2026-09-16 applies when published with the corresponding service release. We communicate material changes before new processing where required. An updated notice does not retrospectively create consent. Contact us for an earlier applicable version.