PlopFit Privacy Policy

Effective date: October 8, 2026

1. Controller and contact

PE Matvienko Andrey Kirill, M. Khorenatsi str., bld. 26 a, 201 o, Yerevan, 0018, Armenia, is the controller for the processing described in this Policy. PlopFit is referred to as we or us.

For privacy or legal requests, email info@plopfit.com. For product support, email support@plopfit.com.

2. Scope and age

This Policy covers the PlopFit iOS app and the Marketing site at plopfit.com, including Journal and Partners, and the website subscription portal where offered. The Service is offered worldwide without a geographic eligibility gate and is for people aged 18 or older. We do not request a date of birth solely to enforce this age rule and do not knowingly offer the Service to children.

3. Data we process

Account and identity data. PlopFit supports Sign in with Apple and Google sign-in. We receive the verified issuer and subject needed to map sign-in to an opaque internal user ID. We process account status, locale, timezone, authentication timestamps, required Terms and consent evidence, and privacy-workflow records. We do not use email to merge or link product accounts.

Workout and progress data. We process workout setup choices such as vibe position, space constraints, and disabled workout zones; generated sessions; workout and completion history; session-length feedback; retained XP; counted days; mini-game levels and awards; and badge progress. Some setup and history patterns may reveal health-related or body-limitation signals even though PlopFit does not ask for a diagnosis.

Subscription data. Apple processes in-app purchases and payment details. Where website purchases are offered, Paddle acts as merchant of record and processes checkout, billing, fraud prevention and payment details under its own privacy notice. PlopFit processes the minimum account-bound transaction and subscription references needed to fulfill, verify and support access. RevenueCat processes the internal PlopFit user ID and subscription information needed to fulfill and reconcile access. PlopFit keeps a minimal subscription status and normalized provider references and events. We do not store payment-card details, Apple receipts, or raw RevenueCat payloads in product tables.

App analytics and diagnostics. Optional app analytics is off until you separately agree. In eligible TestFlight and App Store builds, Google Firebase Analytics processes approved app interactions, app and device information, approximate location derived from your network connection, and pseudonymous identifiers, including an account-linked analytics key. Analytics may be exported to Google BigQuery for product reporting. We do not send raw PlopFit account IDs, submitted health-related setup choices, payment identifiers, or free text in custom analytics events. We do not use these analytics for advertising personalization. Firebase Crashlytics separately processes crash and reliability diagnostics and ordinary app or device metadata needed to investigate failures.

Device-local data. The app keeps authentication credentials in protected device storage and may keep account-scoped preferences, workout-resume state, temporary export files, reminder settings, and deletion-confirmation state on the device. PlopFit clears applicable account-scoped local data on sign-out or account lock. Copies you export or share outside PlopFit are controlled by the destination you choose.

Website cookies and optional measurement

Cookiebot by Usercentrics provides the website consent banner and records your choices. Necessary consent, security, sign-in and requested checkout functions operate independently of optional measurement. Payment providers may process data needed for a checkout you request; this does not authorize unrelated analytics or advertising.

Google Tag Manager and Google Analytics load only after you explicitly allow Statistics. We measure visits to Pricing, purchase-button clicks, opening the subscription portal, opening and completing checkout, and backend-confirmed workout access during that checkout. Checkout completion is a browser interaction and does not by itself prove payment. Google also processes ordinary browser, device and network metadata and pseudonymous browser identifiers. We exclude email, account and transaction identifiers, sign-in codes, query strings, article titles, workout data and payment details from these event payloads. We do not connect this website funnel to your app analytics identity.

Declining optional cookies does not prevent sign-in, purchasing or using a subscription. Events before consent are discarded. Use Cookie settings in the footer to change or withdraw your choice at any time. Withdrawal stops future measurement, clears accessible Google Analytics cookies for this site and reloads the page to stop loaded measurement scripts. The Marketing category does not activate an advertising destination in this configuration.

Support and operations. We process correspondence you send to our privacy, legal, or support addresses. We also process short-lived request information and minimized operational logs needed to secure and operate the Service. Marketing abuse controls use an IP address transiently without adding it to the waitlist record.

4. Why we process data

We process account, workout, subscription, and support data to provide the Service, perform our contract, respond to requests, and meet legal obligations. Required account-data consent records the user's direction to store the data needed to operate the account; withdrawing it starts account deletion because the account service cannot run without that data.

We rely on separate optional consent for app analytics and website Statistics measurement. Refusing or withdrawing app analytics does not affect your account, subscription, or workouts. We use legitimate interests for minimal security, abuse prevention, reliability, service operations, and crash diagnostics where those interests are not overridden by your rights. We do not sell personal data or use these data for third-party advertising.

5. Who processes data

Current external providers are Apple and Google for sign-in; Apple, Paddle where website purchases are offered, and RevenueCat for subscriptions; Google Firebase Analytics, BigQuery, and Crashlytics for consented app analytics and reliability; SMTP2GO for approved email delivery; Usercentrics Cookiebot for website consent management; and Google Tag Manager and Google Analytics for consent-gated website measurement.

These providers process data under their own infrastructure, terms, and security controls. Some processing may occur outside Armenia or the country where you live. Where required, we use applicable contractual or legal transfer safeguards and assess provider terms and access controls.

6. Retention and deletion

Account, workout, and progress data are kept while the account is active. An account-deletion request locks access during a 30-day grace period. When deletion processing runs, PlopFit deletes app-owned account, identity linkage, workout, progression, consent, and subscription-mirror data, asks current identity and subscription providers to delete the applicable user records, and keeps only narrowly required legal, dispute, security, or no-resurrection records. Non-statutory minimized subscription-event references may be kept for up to 24 months after account deletion or the last provider event, whichever is later.

The website waitlist and optional waitlist research are retired. Historical records remain subject to applicable withdrawal, deletion and prior retention commitments. Minimized Marketing logs are kept for seven days unless an incident hold applies. Closed privacy and support correspondence is kept for 90 days unless a legal hold applies.

Cookiebot keeps the website choice in your browser for up to 12 months, unless you change or withdraw it earlier or your browser clears it. The choice lifetime is separate from provider consent-proof and analytics retention. You can request information about, or deletion of, previously collected website measurement and consent records through info@plopfit.com; withdrawal does not automatically erase data already collected. For website analytics, GA4 user-level and event-level data retention is two months, with reset on new activity disabled. This setting does not limit most aggregated standard reports. For app analytics, GA4 event-level retention is two months and user-level retention is fourteen months, with reset on new activity disabled. BigQuery export tables expire 180 days after creation; provider recovery windows may retain deleted copies for a limited additional period. These retention settings do not replace handling an individual deletion request. App analytics choices retain the notice version, text hash, source, and server receipt time in the account consent journal. An off preference is also retained on the device to prevent collection after a failed save or sign-out. Crash diagnostics are kept only as long as needed to investigate and prevent recurring failures under the configured Firebase retention controls. Backups are protected and allowed to age deleted data out rather than restore it as active data.

7. Your choices and rights

Depending on applicable law, you may ask for access, a copy, correction, deletion, restriction, or objection, and you may withdraw consent. Withdrawing consent does not affect processing already performed lawfully.

Use the Account area in the app for account export, required-consent withdrawal, and account deletion. Turn optional app analytics off in Settings or Account without deleting the account or cancelling your subscription. Withdrawal stops future collection on the device; if saving the choice fails, it stays off there while saving is retried. Other installations apply the saved choice when they next check it. To request deletion of previously collected analytics, email info@plopfit.com; these requests are currently handled manually. Deleting a PlopFit account does not cancel an Apple subscription or delete information Apple or Google keeps independently; manage Apple billing through Apple. Email info@plopfit.com for other privacy requests concerning the app or Marketing site, including historical waitlist deletion or withdrawal. Use Cookie settings on the website to withdraw optional website measurement consent.

We may need to verify that a request concerns you, but we do not request identity documents by default. You may complain to the data-protection authority that applies where you live or to the competent authority in Armenia.

8. Security

We use appropriate technical and organizational safeguards, including access restrictions, encrypted transport, data minimization, and secret-safe logging. We review and update these safeguards as the Service evolves.

9. Changes to this Policy

We may update this Policy. A material change to data, purpose, provider, retention, or rights receives a new version and, where required, notice and fresh consent. The effective date above identifies this version.

10. Contact details