Skip to content
Dozdatlift Support
English Español (Latinoamérica) Português (Brasil) Français Deutsch Italiano Bahasa Indonesia Tagalog

Dozdatlift Privacy Policy

Effective date: November 10, 2026

1. Who is responsible

I1I1 Group LLC ("we," "us," or "our") operates Dozdatlift. This policy covers personal information processed in connection with the Dozdatlift app, dozdatlift.com and its related app-opening pages, and Dozdatlift support. The informational company website at i1i1group.com has a separate privacy notice. This policy does not cover unrelated services merely because they link to Dozdatlift. Our separate Consumer Health Data Privacy Policy explains consumer health data within the scope of Washington's My Health My Data Act, including categories, sources, purposes, recipients, and rights. Its specific health-data protections apply alongside this general policy; the general retention and disclosure descriptions here do not override them.

For information whose purposes and means we determine, we are the responsible business or controller where those terms apply. Stores and other providers can have their own responsibilities for processing they determine independently. Calling a service a provider does not mean all its processing is solely on our instructions.

2. The local app and external services

Dozdatlift does not require an app username, password, or company-hosted account, and does not provide cloud workout sync. Workout tools primarily use information stored on your device. This does not mean that everything you do remains on the device: store purchases, media loading, website requests, support email, and sharing destinations involve other services.

We do not automatically receive your complete local workout database merely because you create or complete a workout. We cannot remotely retrieve purely local records that you have never sent to us. Device or operating-system backups may create copies under your settings and the relevant provider's practices.

3. Information categories, sources, and purposes

Workout names, programs copied into workouts, exercises, sets, repetitions, loads, timing and completion information, notes, ratings, and history

Source and processing location: Entered or generated through use of the app; held locally unless you choose to share it or your device backup copies it

Purpose: Plan, perform, save, display, and compare supported workouts and calculate app estimates

Custom exercises, app language and other preferences, current workout/navigation state

Source and processing location: Your selections and app operation; principally local

Purpose: Remember choices and restore supported app/workout state

Legal acceptance events and exact document copies

Source and processing location: Your affirmative acceptance action and device/app information; stored locally

Purpose: Record which documents and statements were accepted and show acceptance history

Purchase and access information

Source and processing location: Apple or Google purchase/restore processes, RevenueCat purchase-management services, local validated access records, and information you supply in a support request

Purpose: Determine paid access, restore eligible purchases, handle transaction issues, and respond to refunds or revocations

Connection and resource-request information

Source and processing location: Requests from your device to website hosts, media/image hosts, player dependencies, and stores

Purpose: Deliver requested pages/content, operate the providers' services, and protect those services

Support and privacy correspondence

Source and processing location: Your email address, name if supplied, message, attachments, and associated mail information; received through Proton Mail

Purpose: Respond to your request, investigate issues, administer rights, and maintain necessary correspondence records

Information in a file you import or export

Source and processing location: The file and destination you select

Purpose: Carry out the requested local workout transfer or handoff to your chosen service

Workout records, notes, support messages, and requests for particular content can reveal sensitive information in context. Avoid entering or sending unnecessary medical details. A workout entry is not necessarily a verified statement about your health, and we do not use it to create a medical diagnosis.

The app does not request identity documents, medical-clearance certificates, insurance records, or a date of birth to complete legal acceptance. The launch design does not include a HealthKit or Health Connect connection, precise-location collection, a contact-list upload, or a company advertising profile. Technical requests can nevertheless reveal an IP address and an approximate location inferred by the receiving provider.

4. Local acceptance history

Each completed acceptance event stores an event identifier and sequence, the time reported by your device, app/build information, reading language, required revision and document editions, the exact accepted document snapshots in the reading language and English, and the exact four confirmation statements and affirmative responses: agreement to the Terms and the 18+ declaration, acknowledgement of the Privacy Policy, agreement to the Release, and acknowledgement of the Consumer Health Data Privacy Policy.

Unfinished confirmations and pending actions are temporary. Only successful durable saving completes acceptance. The normal app interface lets you view earlier events and their exact documents; it does not let you edit or selectively delete an acceptance event. Normal updates and workout deletion/import preserve those records. Workout exports do not include them.

The app does not send acceptance receipts to a company receipt server, verify your identity or age, or obtain an independent timestamp. Records can be affected by device deletion, tampering, backup, or restoration. A local record is not described as permanent or conclusive proof of who operated the device. Clearing app storage can remove it along with other local data; a valid device backup may restore it.

5. Store purchases and RevenueCat

Apple or Google processes store checkout and the payment details you provide to it. Dozdatlift does not ask for payment-card details in the app. The store account is separate from Dozdatlift, which has no app-account login.

Purchase validation and restore can process product identifiers, transaction or purchase-token information, subscription/access status and relevant dates, and verification results, depending on the store. The app keeps the access information needed to apply its paid-feature rules. We may also receive the transaction, financial, and reporting information the store makes available to developers, and any receipt or order details you choose to send to support. Store reports do not automatically give us your entire store profile or workout history.

We may retain store financial reports and relevant transaction details for accounting, tax compliance, refunds, and purchase support. We do not use these records to build marketing profiles.

We use RevenueCat to help validate purchases, maintain subscription and entitlement status, and restore eligible access. Its SDK creates an app-user identifier without requiring a Dozdatlift account. Purchase records can associate that identifier with products, transaction or purchase-token information, purchase and expiration times, store, and access status. Technical service requests also involve information needed to deliver and secure the service. We can view purchase and access records through the RevenueCat dashboard.

We do not deliberately supply your name, email address, workout history, or notes to RevenueCat as customer attributes. An identifier described as anonymous by the SDK is still a persistent identifier associated with purchase activity; this is not a promise that the records cannot be linked to a person. Optional RevenueCat integrations with advertising, marketing, or other analytics services are not enabled for launch.

We use purchase information to fulfill the purchase, restore eligible access, account for transactions where required, and investigate purchase problems or misuse. Purchase verification is separate from video delivery; no separate company video-token service is used. RevenueCat processing is described further in its privacy policy (https://www.revenuecat.com/privacy-policy).

Store processing is also explained in Apple's privacy policy (https://www.apple.com/legal/privacy/) and Google's privacy policy (https://policies.google.com/privacy). Contacting us can help with information we control; it does not let us erase the store's independently maintained records or cancel a subscription outside its processes.

6. Video, posters, images, and player dependencies

Videos and remote images are delivered by external providers. A request can disclose your IP address, the requested content or resource, request time, and device/browser information. Players can make additional requests needed for playback and their operation. A poster or thumbnail may load before you press Play. Not playing a video does not necessarily prevent all media-related requests.

App-owned exercise tutorials and help videos use the Company's YouTube account for their free app placements. When the same videos are included in paywalled coach content, those placements use separately hosted copies with different URLs on the Company's Mux account. The provider delivering each version processes the technical information associated with that playback. Coach videos included in any paid placement use company Mux hosting across their app placements. Free-only coach videos ordinarily use the coach's YouTube channel, with company hosting possible by agreement. These arrangements do not upload your entire local workout database to a coach or video provider.

We use YouTube's privacy-enhanced embedding configuration. That setting changes aspects of YouTube's handling; it is not a promise that Google receives no information or that playback involves no storage or other processing. Google determines aspects of its platform processing under its own policies. Opening a video directly on another website can involve that site's additional practices and your settings with it.

For Mux playback, we configure optional Mux Data analytics and its analytics cookies off, and we do not supply a custom viewer identifier. Necessary video delivery and provider operational processing still occur. Disabling optional analytics is not a promise of anonymous playback, no logs, or no storage. Mux's handling of customer-controlled data is also governed by the applicable customer processing arrangements; its public website privacy notice does not establish all retention rules for our video traffic.

The hosted Mux player can request software or fonts from jsDelivr and Google, whose servers receive the technical information accompanying those requests. Other remote images, such as coach portraits, can similarly contact their image host. Providers do not become subject to our correspondence-retention period simply because the app loads their resources.

Relevant provider information includes Google's privacy policy (https://policies.google.com/privacy), Mux's privacy information (https://www.mux.com/privacy), and jsDelivr's privacy policy (https://www.jsdelivr.com/terms/privacy-policy). These links supplement this notice; they do not replace our responsibility to explain processing we control.

7. Website hosting, cookies, and analytics

Cloudflare provides the selected hosting infrastructure for the Dozdatlift website. Serving and protecting pages involves technical requests, including IP addresses, requested URLs, timestamps, browser details, and security information. Information available to us through hosting controls depends on the enabled services and configuration. Cloudflare's privacy policy (https://www.cloudflare.com/policies/privacy/) explains its processing roles and practices.

At its initial launch, the Dozdatlift website provides product information, images, legal documents, and contact or external links. It has no embedded videos or public coach pages. We do not operate a website account system, newsletter signup, or advertising-audience program. Email links open your email service rather than submitting a website contact form. App-download links become available when the store listings are available.

After the app launches, individual coach pages may be added as real coaches join. Those pages provide app-download links and a coach-specific link that opens the app. Initial app use requires the language and legal-acceptance steps described in the Terms before proceeding to the selected coach. Opening a website page does not itself create an app acceptance record. The app video processing described in section 6 does not occur merely because you visit the initial informational website.

The launch website does not use optional advertising or visitor-analytics tools and does not embed third-party media. We do not set optional tracking cookies through the website code. Cloudflare may process technical requests and use security-related cookies or similar technologies to deliver and protect the site.

Where law requires a choice or consent before nonessential storage or processing, it must be obtained before that activity or the activity must remain disabled. This paragraph does not claim a cookie-consent interface already exists. Browser/device controls and provider settings can help manage storage, although blocking resources can affect playback or site functions. App language and preference storage is distinct from third-party tracking.

8. Support, privacy requests, and sensitive reports

When you contact support, we receive what you send through Proton Mail. Authorized company management and employees may access relevant correspondence for support, administration, and privacy requests. Access is limited to work needs, and company email accounts use two-factor authentication.

For privacy questions, requests, or appeals, contact support@dozdatlift.com, or write to I1I1 Group LLC, 6903 NE 142nd Street, Vancouver, WA 98686, United States. Authorized company personnel handle requests; individual employees' names are not needed to use this contact route.

Correspondence stays in Proton under the adopted operating policy: no routine forwarding, separate company email backups, or routine copying into unrelated helpdesk or AI services. This does not prevent a necessary, limited disclosure described in section 11, such as to obtain legal assistance with a claim. It also does not describe Proton's own backups, your sender-side copies, or copies you independently share.

Please do not send medical records, injury photographs, identity documents, or other sensitive information that is unnecessary to explain your issue. Support does not provide individualized medical, dietary, or clinical care. If you report a safety issue, identify the relevant content and explain the issue with as little sensitive detail as reasonably necessary. We do not require a medical history or an insurance declaration to receive an ordinary support request.

Information you volunteer is not permission for unrelated use. We limit access to sensitive reports, remove unnecessary sensitive attachments sooner than ordinary correspondence, and apply any additional legal requirements to necessary processing. A report may need appropriate preservation or disclosure for a legal or safety matter; it is not automatically forwarded in full to a coach.

9. Imports, exports, sharing, and device backups

Import reads the supported file you select and processes its workout data on the device. Export prepares supported completed-workout history, associated lane information, and the committed custom-exercise catalog, including catalog items not yet used in a workout. It excludes unfinished workouts, settings, purchase entitlements, and legal acceptance history. Files can include your notes and other sensitive details. Transfers are not full app backups.

You select the sharing destination or storage service. We do not automatically receive a copy just because you export. The selected recipient or service handles its copy under its own practices. Temporary export-file cleanup is best effort and cannot erase copies already saved, backed up, or forwarded elsewhere.

Your device or operating system may back up app data or restore it, depending on your configuration. We do not control those independent backups. Removing the app or local information may not remove them. Manage those copies with the relevant device or provider controls.

10. Purposes and legal grounds

Where a lawful basis is required, we use the basis appropriate to the particular processing and applicable law:

- Requested services and purchases: processing necessary to provide the app functions, deliver content, fulfill or restore purchases, or take steps you request before a contract. - Support and security: our legitimate interests in responding to inquiries, resolving defects, safeguarding the Service, and addressing misuse, where those interests are not overridden by your rights. Contract necessity may instead apply to support needed to fulfill a purchase. - Legal duties: processing required to meet applicable accounting, legal-disclosure, or privacy-request obligations. - Disputes and claims: necessary records and limited disclosures for establishing, exercising, or defending legal claims, using an applicable lawful basis and any additional sensitive-data condition. - Consent-required activity: separate, specific consent where law requires it, such as certain nonessential tracking or sensitive-data processing. We do not substitute acceptance of the Terms for that consent.

The contract or legitimate-interests basis alone does not establish every additional condition needed for health or other specially protected data. For consumer health data within the scope of the Consumer Health Data Privacy Policy, we process data to the extent necessary to provide a product or service you request, or obtain the specific consent required for the activity. Where separate consent is required for sharing, we obtain it separately from collection consent. Local processing is not automatically outside privacy law. We must satisfy applicable conditions for the actual activity, and cannot expand collection simply by listing a possible purpose here.

Providing optional correspondence details is voluntary, although we may be unable to resolve a request without enough information. The relevant local inputs or purchase information are needed for the functions that use them. We do not use workout data for advertising profiles, clinical decisions, employment screening, or insurance decisions. App calculations and access checks do not represent an individual medical assessment.

11. Who receives information

Information is disclosed only as relevant to the purposes described above:

- Service providers: hosting, media delivery, player dependencies, and email providers receive the information needed for their services, subject to their applicable roles and arrangements. The named launch providers are Cloudflare, YouTube/Google, Mux, jsDelivr where loaded by the player, RevenueCat for purchase management, and Proton Mail. - Stores: Apple or Google handles transactions and related validation/reporting. Their independent processing is governed by their own obligations and notices. - Your selected recipients: destinations you choose for exports, email, or external links receive what your action sends. - Professional assistance and legal recipients: lawyers, accountants, insurers if applicable, competent authorities, or other necessary recipients may receive limited information where required or permitted for a specific legal obligation, claim, security incident, or rights/safety issue. This does not claim an insurance policy is already in place or allow unrestricted sharing of sensitive reports. - Business successors: information may be transferred in a sale, reorganization, or similar transaction where lawful and subject to the existing privacy commitments and required safeguards. Any materially different use must satisfy applicable notice and consent requirements.

Coaches do not receive general access to your workout database, support inbox, purchase records, or health information. If a content issue needs a coach's assistance, we prefer a content identifier and a minimized, nonidentifying explanation. Any necessary identifiable disclosure must have an appropriate legal basis and satisfy additional sensitive-data restrictions.

We do not sell customer information for money, operate a targeted-advertising audience program, or send promotional newsletters at launch. We disclose information for the service, transaction, support, security, and legal purposes described in this policy. The restrictions and rights that apply to a particular disclosure depend on the information, the recipient's role, and applicable law; providing a service to us does not by itself make every disclosure exempt.

12. Retention and deletion

For consumer health data covered by the Consumer Health Data Privacy Policy, its deletion requirements apply, including notification to relevant recipients and the stated backup/archive limits. General support or accounting retention criteria do not automatically create an exception to those requirements.

We limit company-controlled retention to the relevant purpose, considering the information's sensitivity, the duration of the service or request, applicable legal duties, and the need to resolve an actual dispute. Different categories have different retention boundaries:

Local workouts, catalog, preferences, and workout state

Retention and deletion approach: Remain subject to app controls and device storage. Deleting a workout removes that record but does not necessarily remove every other category. Device backups or shared copies may persist separately.

Local legal acceptance history

Retention and deletion approach: Remains with app data through ordinary updates and workout deletion/import; no selective event-deletion feature. Removing app storage can remove it, and valid device backups may restore it. We do not keep a company receipt-server copy.

Ordinary support correspondence

Retention and deletion approach: Up to 12 months after resolution, with monthly deletion-deadline reviews. Unnecessary sensitive attachments are removed sooner. Necessary legal, security, or dispute exceptions are limited, documented, and periodically reviewed. Relevant company-controlled replies and copies are included in the procedure.

Purchase/accounting information received by the Company

Retention and deletion approach: Retained only as necessary to fulfill and evidence purchases, address actual disputes, and meet applicable accounting/legal duties. This can include exported store financial reports and relevant transaction details. Retention is based on the applicable recordkeeping obligation, continuing purchase or refund issue, or actual dispute; records are not retained indefinitely merely because they might be useful.

RevenueCat purchase and entitlement records

Retention and deletion approach: Records support purchase validation, restoration, subscription history, and dispute handling. Deleting local app data does not by itself delete RevenueCat records. Contact us about records processed for us; requests are assessed against continuing purchase rights, legal duties, and the provider's deletion processes. We do not promise that provider records disappear immediately or that the support-mail retention period applies to them.

Website/media operational and security information

Retention and deletion approach: We limit company-controlled operational and security records to the time needed to deliver and secure the relevant service, investigate a specific issue, respond to a request, or meet an applicable legal duty. Provider-held delivery and security records follow the applicable processing arrangements and retention criteria, including service operation, abuse prevention, security, and legal requirements. These criteria vary by provider and record type; our support-correspondence deadline does not apply to every hosting, media, CDN, or security record. Where a provider processes records on our behalf, we handle deletion requests through the applicable provider process.

Provider, device, and recipient copies

Retention and deletion approach: Governed by the relevant provider's role, your settings, and applicable law. Our support-mail deadline is not a promise that all copies everywhere disappear on that date.

Deleting local workouts or uninstalling the app does not cancel subscriptions, delete store transaction records, recall exported files, or remove every backup. Where we never received local information, we cannot remotely retrieve or erase it; we can explain the applicable device/app controls.

Proton maintains its own service backups separately from our no-separate-company-backup practice. Its Mail privacy policy (https://proton.me/mail/privacy-policy) describes provider retention. Moving a message into Trash is not necessarily final deletion; our company procedure must address permanent deletion of selected expired correspondence. Deletion may remain subject to lawful preservation requirements and provider backup lifecycles.

13. Your rights, choices, and requests

The Consumer Health Data Privacy Policy provides the specific health-data request and appeal process, deadlines, recipient information, and deletion provisions under Washington's My Health My Data Act. You may use the same support address for those requests.

Depending on the law that applies, you may have rights to confirm processing; obtain access or a copy; correct or delete information; restrict or object to processing; receive portable information; withdraw consent; opt out of specified uses; or appeal a request decision. Rights have applicable conditions and exceptions. Consent withdrawal does not make earlier lawful processing unlawful. You may also complain to the competent privacy authority.

Contact support@dozdatlift.com with your request and enough information to identify the relevant interaction. You do not need a Dozdatlift account to ask. We use proportionate authentication, avoiding unnecessary identity or medical documents. An authorized representative may act where applicable law permits, subject to appropriate authority and verification. We respond within applicable legal deadlines, explain lawful denials or limitations, and do not unlawfully discriminate for exercising privacy rights.

To appeal our decision where applicable, reply to the decision or email the same address with "Privacy appeal" and the relevant details. We will review the appeal and explain the outcome and applicable further complaint routes. This is not a waiver of a right to contact a regulator directly.

We distinguish information we control from independent store, device-backup, and recipient records. Where a provider acts for us, we address applicable provider-assistance obligations; where it acts independently, we explain that boundary and relevant contact options rather than claiming to control every record. Request handling itself creates a limited correspondence record, subject to the retention principles above.

Where applicable law requires recognition of a browser/device privacy signal, we must honor it for the processing to which it applies. This notice does not imply that a universal opt-out or optional-cookie system has already been implemented. Any required operational controls must be in place before the relevant processing launches.

14. International processing

We are based in the United States. Providers may process information in the United States and other countries where they and their authorized service providers operate. Your own sharing choices may also send information elsewhere. Another country may have different privacy laws.

Applicable provider data-processing agreements describe safeguards for international transfers of information processed on our behalf. Depending on the provider, transfer, and applicable law, these arrangements may include standard contractual clauses, transfers to a recipient covered by an applicable adequacy decision, or another lawful mechanism. Coverage is specific to the recipient and processing; a provider's published certification does not mean every transfer is covered. Contact support@dozdatlift.com for information about the safeguards relevant to information we control.

15. Adults-only service and information about minors

Dozdatlift is intended for adults aged 18 or older and offers no under-18 enrollment or parental-permission route. We do not knowingly invite children to submit personal information to support or create an app account. The age statement is self-attestation, not identity verification.

If you believe a minor has provided personal information to us, contact support with the minimum information needed to identify the issue. We will assess it and take appropriate steps under applicable law, including deletion where required. We do not ask you to send a child's full medical history or unnecessary identity documents. A store content rating does not change the app's adult-only eligibility.

16. Security

We use safeguards appropriate to the information and processing, including limiting employee access by work need and two-factor authentication for company email. These controls reduce risk but cannot guarantee that transmission, storage, or access is completely secure.

Protect your device, store account, email account, and chosen backups. Local app records rely on device/operating-system protections; the app does not add a separate application-level encryption layer to its stored workout and acceptance data. This is not a statement that all devices have identical storage security or that all providers use one uniform security model.

Public video delivery is not an access-controlled repository for customer information. The app does not upload your personal workout records into publicly delivered video files. We do not promise DRM, anonymous playback, tamper-proof local records, or immediate erasure of every provider copy.

17. Changes and language

We identify the version and effective date of this policy and provide notice of material changes as required by law. We obtain separate permission before new processing where law requires it. Updating a policy or its translation does not itself mean that you consented to every new practice.

The app's legal acceptance process and local records are described in section 4 and the Terms. Acknowledgement of either privacy notice confirms receipt of that notice, not unrestricted authorization to collect or share information. App updates carry revised bundled documents; website publication does not silently replace documents inside an offline or older installation.

Translations are provided to help you understand the policy. To the extent law permits, English controls an inconsistency, without limiting mandatory local-language notice requirements or privacy rights. Contact support about an unclear or inaccurate translation.

dozdatlift-privacy-1-0

© Dozdatlift

Support Company Terms of service Privacy policy Agreement and release of liability Consumer health data privacy policy