Privacy Policy

The short version

DropPace turns your runs into share-ready images. We process the data we need to make that image — your workout, your route, and (if you choose) your photo — and we hold on to as little as possible. The mobile app uses an account so your runs, drops, purchases, support history, and device entitlements can stay tied together. We do not sell your data, we do not use your health or workout data for advertising, and we do not use any third-party AI service to profile you or advertise to you.

We do advertise DropPace on other apps and sites. The app uses AppsFlyer, an attribution service, to measure which of those ads led to an install. On iPhone, the app reads your device's advertising identifier only if you allow tracking when the app asks. Details are in section 3.

We collect account identifiers such as your email address and display name when you sign in or create an account. If you buy a lifetime offer on our website, we also collect the email address you provide so we can deliver your access link. Details are in section 3 below.

1. Who we are

Nuko Nova Dynamics LLC ("DropPace," "we," "us," or "our"), a Florida limited liability company, operates the DropPace mobile application (the "app") and the websites at droppace.com and droppace.app (together with the app, the "service"). For the purposes of the EU and UK General Data Protection Regulation ("GDPR"), Nuko Nova Dynamics LLC is the data controller for personal data processed through the service.

This Privacy Policy explains what data we process, why, how long we keep it, who we share it with, and the rights you have. For any privacy question or request, contact [email protected].

2. Accounts

The DropPace app requires an account. You can sign in with email and password, Sign in with Apple, or Google. We use the account to keep your app access, support history, purchase state, and device-linked usage records together. Subscriptions and in-app purchases are still processed by Apple or Google where required; we receive only the purchase and entitlement information needed to operate the app.

If you buy a one-time lifetime offer at droppace.com, we collect the email address you provide so we can attach the entitlement to your DropPace account, and our payment processor collects your payment details. See "Website and lifetime purchases" in section 3.

3. Data we process

Workout and route data

With your permission, DropPace reads completed workout records from Apple HealthKit (iOS) or Google Health Connect (Android), which may include workout type, start and end time, distance, duration, pace, heart rate, calories, step count, elevation gain and loss, running and cycling power, running and cycling speed, cycling cadence, running stride length, running ground contact time, running vertical oscillation, VO₂ max, and the GPS polyline of your route. This is health and precise-location data, and we treat it as sensitive. We use it to show your completed workouts, recommend styles for the workout you select, render and validate your share image, and — only if you separately enable Cloud Workout Sync in Settings — keep aggregate workout summaries and simplified routes as DropPace workout records linked to your account, available on your signed-in devices and our authenticated workout-library website. You can also explicitly choose a GPX, FIT, or TCX file either to recover a missing route for a specific workout or to upload a complete workout to your DropPace Cloud library. Our servers read the file, keep its Run Details (see "Run Details" below), and may merge it with matching records of the same workout; we delete the file itself as soon as it has been read. Explicit file uploads may be available on signed-in iOS, Android, and web clients. We do not run continuous or real-time location tracking.

Zepp Connection

If you connect your Zepp account (the app for Amazfit watches) in Settings, Zepp tells our servers about each activity you record, and our servers download that activity's file from Zepp. Right after you connect, we also bring in your activities from the past 365 days. You sign in on Zepp's own page, so DropPace never sees your Zepp password. The Zepp Connection needs a DropPace account and Cloud Workout Sync.

From each activity we read its type, start time and time zone, duration, distance, calories, GPS route, heart rate, pace and speed, altitude, cadence, stride length, running power, running dynamics (ground contact time, vertical oscillation, and vertical ratio), laps and pauses, time in each heart-rate zone, training effect and training load, VO₂ max, and the name of the device that recorded it. We bring in runs, treadmill runs, walks, hikes, and rides. Activities that cannot be one of those, such as strength training, swimming, and team sports, are skipped without being downloaded. We also download activities in general, mixed, interval, multisport, and certain other modes that can record a run or walk, plus activities with no type or a type Zepp does not document. We check the sport in the file; if it is not one of the activities listed above, we discard the file and keep only a short delivery record, deleted after a month. From your Zepp profile we keep only your Zepp user ID. Zepp also returns your nickname, avatar, gender, birthday, height, weight, and country; we do not store them. The access and refresh tokens Zepp issues are stored encrypted on our servers and never sent to your device. A Zepp workout you choose for an image is processed like any other workout, including by our AI provider as described in section 6. DropPace sends nothing to Zepp beyond the requests needed to sign you in, keep access, download your activities, and end access when you disconnect.

Run Details

For a workout that comes from the Zepp Connection or from a workout file you import, we keep its full record with your account ("Run Details"): every reading the file holds, often one per second (GPS position, heart rate, pace and speed, altitude, distance, cadence, stride length, power, and running dynamics), the splits and laps worked out from those readings, and the summary values the file carries, such as heart-rate zone times, training effect, and VO₂ max. We keep them because the source cannot be read again later: Zepp's download links work only once, and an imported file has no source to fetch from. We use Run Details to show the workout, to draw its splits, laps, and charts in the images you make, and to include them when you export your workouts. Run Details are stored only with Cloud Workout Sync on. We never keep the original Zepp file or workout file. Workouts read from Apple Health or Health Connect have no Run Details on our servers; their splits, laps, and charts are read on your device.

Photos you provide

For the photo-led modes, you choose a photo from your camera roll or take a new one with the camera. That photo is uploaded so our servers can recommend styles for it (see section 6) and compose or restyle your share image with the chosen style applied. The original photo may be retained privately for up to 30 days so you can re-roll that Drop, then it is deleted automatically. You can delete it sooner by deleting the Drop or your account. We do not perform facial recognition and we do not use your photos to identify you or anyone else.

Generated images

The share image we create for you has a permanent public link so it can keep working when you re-share it. The image remains on our infrastructure until you delete that Drop. If you separately confirm a public Display Name and leave credit on for that Drop, the link may show that name; changing the name updates prior credited links, and turning credit off makes the link anonymous. Each generated image contains an embedded "Software" metadata tag identifying it as produced with DropPace and marking it as AI-generated. This metadata travels inside the image file you share. A Card carries the same kind of tag naming DropPace, but marks it as AI-generated only when the Card carries an AI-suggested title; a Card without one is drawn entirely by code.

Cards

A Card is drawn by code from a Layout you choose, not by our AI provider. Before you have a DropPace account, a Card never leaves your device: making one and saving it to your library happens locally, with nothing uploaded.

When you ask for a link to a Card, we load the workout record already stored with your account (its stats and route) and redraw the Card on our servers from that record, so the public image can only carry your real numbers. The finished image is then stored and given a permanent public link, like any other Drop (see "Generated images" above). If a Layout has a title, DropPace can suggest one using a summary of the run: its start time and stats (see section 6).

If the Layout draws a map, your device requests the map data for the area around your route from our map data host (see section 7), and our servers request the same area again when they redraw the Card for a link. These requests carry the map area and, like any web request, your device's or our server's IP address; they carry no account identifier or workout stats. Map data is © OpenStreetMap contributors, available under the Open Database License; see openstreetmap.org/copyright.

Device identifier and subscription state

We generate a random, device-scoped identifier so we can attach your trial status, subscription status, credit balance, or lifetime entitlement to your installation, link it to your account, enforce usage limits, and prevent abuse.

Account information

We process the account information you provide or that your sign-in provider shares with us, such as email address, display name, provider account ID, authentication session records, and related security tokens. We use this information to sign you in, protect your account, provide support, and connect purchases and generated content to the right user. Your account profile name is private by default. A separate public Display Name is published only after you confirm it and choose to credit a Drop.

Notifications

If you allow notifications, your device provides a push token so we can send you optional alerts, such as a reminder when a new run is ready to drop. You can turn notifications off at any time in your device settings.

Diagnostics and product analytics

We collect crash reports, performance traces, and anonymized product-usage events (for example, "a render was generated" or "a share was tapped") to find bugs and decide what to build next. These events do not contain your photo, your route, your workout data, or any information that identifies you personally.

Website and lifetime purchases

If you buy a one-time lifetime offer on droppace.com, we and our payment processor process the email address you provide, your purchase and entitlement record, the time and amount of the purchase, and your IP address (used to route the checkout and to help prevent fraud and abuse). We use this information to take payment, attach account access, provide support, keep records, and meet our tax and accounting obligations. Your full payment-card details are handled by our payment processor (Stripe); we do not receive or store your card number.

Cookies and website data

The DropPace app does not use cookies. Our websites use only the strictly necessary cookies and similar technologies needed to load pages, remember your choices, keep the site secure, and complete a purchase — including cookies our payment processor sets during checkout to process your payment securely. We do not use advertising cookies and we do not use cookies to track you across other websites. Because we rely only on essential and payment-related cookies, you can manage them through your browser settings.

Ad measurement (install attribution)

We advertise DropPace on platforms such as Meta (Facebook and Instagram) and TikTok. To learn which ads led to an install, the app includes the AppsFlyer SDK. It sends AppsFlyer an identifier AppsFlyer creates for this install, your device's vendor identifier (IDFV, on iPhone), your IP address, your device model, operating-system and app versions, the time the app was installed and opened, and a small set of in-app events: that an account was created, that the first image was made, and that a trial or subscription started (with its price and currency). Once you sign in, it also sends an internal account ID so these events and your subscription records match. AppsFlyer reports this to the ad platform that showed the ad, so the platform can credit the install and improve where it shows our ads.

On iPhone, the app asks for permission through Apple's App Tracking Transparency prompt before it reads your device's advertising identifier (IDFA). If you allow it, the IDFA goes to AppsFlyer with the data above; if you decline, it is never read, and you can change your answer in Settings → Privacy & Security → Tracking. Apple's SKAdNetwork reports installs to ad platforms in aggregate without an identifier either way. On Android, the app reads the Google Advertising ID; you can reset or delete it in your device settings under Privacy → Ads.

AppsFlyer never receives your health or workout data, your routes, your photos, your email address, or your name.

What we do not collect

Through the app, we do not collect your phone number, mailing address, social-media handle, contacts, calendar, microphone audio, or browsing history. The advertising identifier is used only for the ad measurement described above.

4. Why we process your data, and our legal bases

We process personal data only for the purposes described below. Where the GDPR applies, the legal basis for each purpose is noted in brackets.

• To create your share image — reading the workout, route, and photo you select and sending the route and stats (and, for photo modes, your photo) to our AI provider to generate and validate the image. [Performance of our contract with you and steps taken at your request; and, for health and precise-location data, your explicit consent, which you give through the in-app permission prompts.]
• To create and share a Card: drawing the Card on your device from the Layout and stats you choose; if you ask for a link, loading the workout record stored with your account and redrawing the Card on our servers; and, if a Layout has a title, sending a summary of the run (its start time and stats) to our AI provider to suggest one. [Performance of our contract with you and steps taken at your request; and, for health and precise-location data, your explicit consent, which you give through the in-app permission prompts.]
• To recommend styles for your run: when you open the style grid, sending a summary of the run you selected and, for photo modes, your photo to our AI provider so it can put the styles most likely to suit them first (see section 6). [Performance of our contract with you and steps taken at your request; and, for health and precise-location data, your explicit consent, which you give through the in-app permission prompts.]
• To provide the permanent public link you request - storing the finished image and publishing the optional public Display Name you separately confirm for credited Drops. [Performance of our contract with you and steps taken at your request.]
• To run subscriptions, trials, and purchases — managing entitlements and, for website purchases, taking payment and delivering access. [Performance of a contract; compliance with legal obligations such as tax and accounting.]
• To sync workouts across your devices — if you enable Cloud Workout Sync, storing account-linked aggregate workout summaries and simplified routes, and the Run Details of workouts from Zepp or from an imported file, reconciling bounded observations, and returning the best available record to your signed-in DropPace clients and the authenticated website. [Your explicit consent, given through the Cloud Workout Sync control in Settings.]
• To read your workouts from Zepp: if you connect Zepp, receiving and downloading your Zepp activities, keeping only your Zepp user ID from your Zepp profile, storing the activities and their Run Details with your account, and keeping access with Zepp until you disconnect. [Your explicit consent, given when you connect Zepp in Settings and approve access on Zepp's page.]
• To keep the service working and secure — enforcing usage limits, preventing fraud and abuse, and diagnosing crashes and performance issues. [Our legitimate interests in operating and securing the service; consent where required for analytics.]
• To measure our advertising: telling the ad platforms we advertise on which ads led to an install, a sign-up, a first image, a trial, or a subscription, through AppsFlyer (see section 3). [Your consent, given through the App Tracking Transparency prompt on iPhone, for the advertising identifier; our legitimate interests in measuring our own advertising for the rest, and consent where the law requires it.]
• To improve the product — understanding anonymized usage patterns to decide what to build. [Our legitimate interests; consent where required.]
• To communicate with you — sending optional notifications and responding to your support requests. [Consent for push notifications; our legitimate interests in supporting you.]

You can withdraw consent at any time — for example, by revoking HealthKit or Health Connect access in your device settings, disconnecting Zepp in Settings or removing DropPace's access in the Zepp app, turning off Cloud Workout Sync or notifications, removing cloud workout copies, or deleting your data in the app — without affecting processing that already took place.

5. Health and fitness data: our commitments

Health, workout, and route data is the most sensitive data DropPace touches, and we hold ourselves to the platform health-data rules:

• We use health and fitness data obtained through Apple HealthKit and Google Health Connect only to provide the user-facing features of DropPace — generating your share image and validating its stats, and recommending styles for your run.
• We never use health or fitness data for advertising, marketing, or any use-based data mining, and we never sell it.
• We never use health or fitness data to determine eligibility for employment, insurance, or credit, and we do not share it for those purposes.
• We do not transfer health or fitness data to third parties except the service providers needed to recommend styles for and render your image, draw the map on a Card, and suggest a Card title (see sections 6 and 7), and only for those purposes.
• Workout data we receive from Zepp is held to the same commitments. We write no data back to Zepp, Apple Health, or Health Connect.

DropPace's access to, use, and transfer of information received from Apple HealthKit and Google Health Connect adhere to the Apple Developer Program License Agreement and App Store Review Guidelines and to the Google Play requirements for health and fitness apps, including their Limited Use requirements. Any other use or transfer of Google user data to third parties is prohibited and we do not engage in it.

6. Third-party AI

DropPace uses a third-party artificial-intelligence service to generate the image treatment applied to your run and to validate that the on-image stats match your workout. Specifically, we send your route polyline, the selected workout stats, a style prompt, and — for the photo-led modes — your photo to OpenAI's image and vision APIs, which process that data on our behalf and return a generated image and a validation result. We do not send your name, email address, account provider identifier, or authentication tokens to the AI service.

We also use OpenAI to recommend styles. When you open the style grid for a run, we send the run's start time, distance, duration, and pace; if the run has a GPS route, a single map coordinate averaged from the route's points and simple facts about its shape (whether it is a loop, an out-and-back, or point to point, how many turns it has, and its proportions); the names and prompts of the styles available to you; and, for the photo-led modes, the photo you chose. OpenAI returns only an order for those styles. This happens before you tap Drop, usually once for each run, photo, and mode you view styles for. We do not send your full route to OpenAI for this step. To prepare it, we save the selected run's stats and route with your account, the same workout record a Drop uses. That record is kept, even if you never create a Drop from it, until you remove your cloud workout copies in Settings or delete your account. The photo is kept as described in section 3.

A Layout with a title slot can carry an AI-suggested one. When it does, DropPace sends a short summary of the run, its start time and stats, to OpenAI's API, which returns a few title options. We keep the suggested titles with your account for up to two years so a Card linked later is still marked as containing AI-written text; they are deleted with your account.

When accessed through OpenAI's developer API as we do, that data is not used to train OpenAI's models. OpenAI may retain API inputs and outputs for up to 30 days to provide the service and monitor for abuse, after which they are deleted unless OpenAI is legally required to keep them. We do not use any third-party AI service to profile you, target advertising, or make automated decisions that produce legal or similarly significant effects about you. We ask for your consent to this processing through the in-app disclosure before your first generation.

7. Service providers we rely on

We rely on a small set of vendors to operate the service. Each acts as our processor and handles only the data needed for its role, under contract:

• OpenAI — generates the share image and validates on-image stats, recommends styles for your run, and suggests Card titles, as described in section 6.
• Convex - hosts our backend, our database, permanent generated-image links, and temporary private source-photo storage.
• RevenueCat — manages subscription state and entitlements purchased through Apple or Google.
• Apple App Store and Google Play — process in-app purchases and subscriptions. We do not receive your payment-card details.
• Stripe — processes website purchases of the one-time lifetime offer, including payment details.
• Resend — sends transactional email for website purchases and account access.
• Sentry — receives crash reports and error traces.
• PostHog — receives anonymized product-analytics events.
• AppsFlyer: measures which of our ads led to an install and reports installs and in-app events to the ad platforms we advertise on, as described in section 3.
• Cloudflare and Vercel — host this website, route share links, provide network and DNS services, and, for Cloudflare, host the map data a Map Card draws.

The ad platforms we advertise on, such as Meta and TikTok, receive install and in-app event data about installs their ads led to, from AppsFlyer. They use it under their own terms and privacy policies.

If you connect Zepp, Zepp Health, the company behind the Zepp app, is a source of the workouts we read, not a processor of ours. It holds your Zepp account and data under its own terms and privacy policy. Our servers call Zepp's servers only to sign you in, keep access, download your activities, and end access when you disconnect.

When you choose to share a generated image to a social network, messaging app, or other third-party platform, that platform — not DropPace — controls what happens to the image and your activity there, under its own terms and privacy policy. You are responsible for what you choose to share and where, and we are not responsible for the practices of third-party platforms or destinations you send your images to.

8. How long we keep data

• Original uploaded photos: retained privately for up to 30 days to support re-rolls, then deleted automatically, or deleted sooner when you delete the Drop or your account.
• Workout and route data: data used by a selected share is stored with that share as described above. The stats and route of a workout you open the style grid for are stored with your account until you remove your cloud workout copies in Settings or delete your account. If you enable Cloud Workout Sync, aggregate workout summaries and simplified route polylines are stored with your account until you remove the cloud copies, delete your account, or ask us to delete them. We may retain up to eight simplified source snapshots for one portable workout so later iPhone or Android uploads can repair it. Run Details of workouts from Zepp or from an imported file are kept for the same period, and Zepp's are also deleted when you disconnect Zepp. Raw sensor samples from Apple Health and Health Connect are not stored, and original Zepp files and GPX/FIT/TCX files are deleted as soon as they have been read.
• Zepp Connection: your Zepp user ID and the access tokens Zepp issues are kept while Zepp is connected. When you disconnect Zepp, turn off Cloud Workout Sync, remove your cloud workout copies, or delete your account, we end DropPace's access at Zepp and delete them, together with the workouts that came only from Zepp, and we remove what Zepp added to your other workouts, such as its route and Run Details. Removing DropPace's access inside the Zepp app has the same effect once Zepp confirms it. The images you already shared are not changed.
• Generated share images: retained at their permanent public links until you delete the individual Drop. Confirmed public Display Name credit remains until you turn it off, rename it, or delete your account.
• Device identifier and subscription state: retained while your installation or subscription is active and for a reasonable period afterward to service refunds, disputes, and abuse prevention.
• Website purchase records: retained as long as your entitlement is valid and as required to meet our tax, accounting, and legal obligations.
• Diagnostics and analytics: retained per the standard retention windows of Sentry and PostHog.

9. How we protect your data

We use technical and organizational measures appropriate to the sensitivity of the data, including encryption of data in transit and at rest with our infrastructure providers, access controls that limit who can reach production data, data minimization, and secure development practices. No method of transmission or storage is perfectly secure, but we work to protect your data and to limit how long we hold it.

10. Account and data deletion

• Delete your account and data in the app. Open Settings → Privacy → "Delete account & data". This deletes your DropPace account, authentication sessions, linked device data, workout records and their Run Details, your Zepp Connection (after we end DropPace's access at Zepp), private source photos, subscription mirror, public Display Name credit, and account-linked diagnostics. Permanent generated-image links remain available anonymously and are no longer associated with your account. We otherwise retain only a pseudonymous deletion audit and trial-history hash for compliance and abuse prevention, plus purchase records where tax, accounting, refund, or other legal obligations require retention.
• Request account deletion without the app. Email [email protected] from your account email and ask us to delete your DropPace account and associated data. We may ask for reasonable information to verify account ownership before completing the request.
• Delete individual Drops. In My Drops, open a Drop and choose Delete to remove that generated image and its server record without deleting your account. Delete individual Drops before deleting your account if you also want their permanent public links removed. You can also email the address above with the link to request deletion of a specific Drop or other account data.
• Manage permissions. You control HealthKit / Health Connect access, photo access, camera access, and notifications from your device settings, and can revoke any of them at any time.
• Export or remove cloud workouts. When Cloud Workout Sync is available, Settings → Workouts lets you export the workout data associated with your account, turn future syncing off, or remove cloud workout copies without deleting your account. Turning syncing off or removing cloud workout copies also disconnects Zepp and deletes its data. Existing shared Drops are retained unless you delete them separately. You can also view portable cloud workouts at the authenticated DropPace workout-library website, whose export includes each workout's Run Details where it has them.
• Disconnect Zepp. Settings → Connections → "Disconnect Zepp" stops DropPace from reading from Zepp, ends our access at Zepp, and deletes the workouts that came only from Zepp. On your other workouts, it removes what Zepp added, such as its route and Run Details. Your Apple Health and Health Connect workouts and the Drops you already shared stay. Removing DropPace's access inside the Zepp app has the same effect.
• Skip the photo. You can create a transparent stats-and-route PNG without providing a photo by choosing Overlay.
• Other privacy requests. Email [email protected] for access, correction, deletion, or another privacy request.

11. Your privacy rights

Because the app now uses accounts, we can use your account email to help locate records tied to you. Some workout and render records may also remain tied to your device-scoped identifier, so we may ask for your in-app support ID when needed to complete a request.

California (CCPA / CPRA)

In the past 12 months we have collected the following categories of personal information: identifiers (a random device identifier, the identifiers used for ad measurement described in section 3, and, for website purchases, an email address and IP address); commercial information (purchase and entitlement records); internet or network activity (anonymized product-analytics and crash data); geolocation data (the route of a workout you choose to render, and the routes of workouts you sync, import, or bring in from Zepp); and sensitive personal information (health and precise-location data from your authorized workouts). We collect this information for the business purposes described in section 4, from you, from your device, and, if you connect Zepp, from Zepp.

We do not sell your personal information for money. We make device identifiers and in-app event data available to AppsFlyer and, through it, to the ad platforms we advertise on so they can measure our ads (section 3). California law may treat this as "sharing" for cross-context behavioral advertising. Declining tracking on iPhone (Settings → Privacy & Security → Tracking) or deleting your Android Advertising ID keeps your advertising identifier out of this sharing, though AppsFlyer still receives its own install identifier and the in-app events. To opt out of the rest, email [email protected]. We never make health, workout, or route data available this way. We use and disclose sensitive personal information only to provide the service and for other purposes permitted without a right to limit. You have the right to know, access, delete, and correct your personal information, and not to be discriminated against for exercising these rights. To exercise a right, email [email protected]; you may use an authorized agent. We will verify your request using reasonable measures proportionate to the data involved.

EEA and UK (GDPR)

If you are in the European Economic Area or the United Kingdom, you have the right to access, rectify, erase, restrict, or object to the processing of your personal data, the right to data portability, and the right to withdraw consent at any time. The legal bases for our processing are set out in section 4. To exercise a right, email [email protected]. You also have the right to lodge a complaint with your local data protection supervisory authority, though we hope you will contact us first so we can help.

Washington, Nevada, and other state health-data laws

If you are in Washington, Nevada, or another state with a consumer health data law, our separate Consumer Health Data Privacy Policy describes the consumer health data we collect, the purposes, the third parties that process it, and how to exercise your rights to access, withdraw consent, and delete — including from backups. Where your state treats workout, heart-rate, or precise route data as sensitive data requiring consent (for example, Connecticut), we collect it only with your permission, through the device health permissions, the in-app disclosure, or the Zepp sign-in you approve, and only as necessary to provide the service you request.

Other regions

If you are elsewhere, you may have similar rights under your local law (for example, in Canada, Brazil, or Australia). Contact us and we will honor the rights that apply to you.

12. International data transfers

DropPace is operated from the United States. If you use the service from outside the United States, your data will be processed in the United States and in other countries where our service providers operate. Where we transfer personal data out of the EEA or the UK, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum. Contact us for more information about these safeguards.

13. Children

DropPace is not directed to, and we do not knowingly collect personal data from, children under 13 — or under 16 in the European Economic Area and the United Kingdom (or such other age as your local law sets for digital consent) unless a parent or guardian has provided consent. If you believe a child has provided us data, contact [email protected] and we will delete it.

14. Changes to this policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the "Last updated" date above and, where appropriate, notify you in-app. Your continued use of DropPace after a change takes effect means you accept the updated policy.

15. Contact

Questions or requests about this Privacy Policy or your data? Email [email protected]. You can also review our Terms of Service and our Acceptable Use Policy.