Privacy Policy

Yoked is built to be private by design. We do not operate Yoked accounts or a server that stores your logged workout history or Apple Health records, and we do not sell your information. When you choose to share a program, its plan contents are included as described below. We use RevenueCat for purchase analytics, TelemetryDeck for app-usage analytics, and Apple's AdServices for Apple Ads attribution on iPhone and iPad. Starting with iOS/iPadOS 1.3.1, we also use Meta's automatic app events for app analytics and advertising measurement. These services, Apple's other services, and Open Food Facts requests are described below.

Who is responsible for your information

Yoked is operated by John Gordon Hilley, based in New York, United States. In this policy, “Yoked,” “we,” and “us” refer to that operator. For processing whose purposes and means we determine, John Gordon Hilley is the data controller. This policy covers the Yoked app and yoked.pro. Contact support@yoked.pro with privacy questions or to exercise your rights.

Apple and other providers also handle information under their own terms for their independent services. Having no Yoked account does not mean that no personal information is processed: device information, support messages, and persistent pseudonymous identifiers can be personal data.

Jump to program sharing, website and support, retention, international processing, or European privacy rights.

The short version

• No Yoked account or sign-up. Yoked does not ask for your name, email address, or phone number to use the app. If you email support, we receive your email address and whatever you include in your message.
• Private iCloud synchronization. iPhone, iPad, and Mac keep a local copy of Yoked records and synchronize them through the private CloudKit database associated with your Apple Account. Personal values use fields configured for CloudKit encryption. Readable synchronization metadata—such as opaque record and relationship identifiers, ordering, civil wake-day keys, health-source bundle identifiers, HealthKit item identifiers used for deletion or reconciliation, lifecycle and mirror-refresh timestamps, and other convergence fields—remains available to CloudKit so synchronization can work. We do not describe this as end-to-end encryption.
• Apple Watch communicates with iPhone. The Watch app keeps a local store and exchanges program and workout information with its paired iPhone through WatchConnectivity. It does not connect directly to Yoked's CloudKit database.
• No ads displayed in Yoked. We measure app use, purchases, and campaign effectiveness using the services below. We configure the iPhone/iPad app without IDFA collection or a request for cross-app tracking permission; the Meta configuration is explained below. We do not use your health records for advertising.
• Limited analytics with pseudonymous identifiers. RevenueCat and TelemetryDeck use a persistent Yoked analytics identity. New installations resolve that identity through your private iCloud database before those services start reporting. Meta uses its own app-scoped identifier and can start reporting at app launch. Yoked does not explicitly supply name, email address, or phone number fields to these providers.
• Program sharing is your choice. Shared programs include the exercises, planned targets, notes, and appearance you choose to share, rather than your logged workouts or Apple Health records. See program sharing for how links and previews work.
• We never sell your data.

Information Yoked handles

Health and fitness information

With your permission, the Yoked app on iPhone and iPad can read the following from Apple Health:

• workouts, including the activity name, time, source, distance, and active energy available for a workout;
• body weight and height;
• date of birth and biological sex;
• sleep duration and stages; and
• dietary energy, protein, carbohydrates, total and saturated fat, fiber, sugar, and sodium.

Yoked can save completed Yoked workouts, body weights you manually log, and nutrition from meals you log to Apple Health when you authorize those writes. Readable body-profile values are used only to fill missing profile values; an Apple Health refresh does not replace a value you entered manually. The Apple Watch app can access workout information such as live heart rate and active energy while you run a workout.

To make the health context already shown by Yoked available on Mac, the Yoked app on iPhone or iPad normalizes relevant workout and activity, nutrition, sleep, and body-weight results into Yoked records and synchronizes them through your private iCloud database. Yoked does not copy raw heart-rate streams, workout routes, or unrelated sensor streams into CloudKit. The Mac app does not request or access HealthKit directly. Health information originating outside Yoked is read-only on Mac and includes its source where available.

Apple controls Health authorization, and you choose which data types to allow. Yoked uses health information only to provide app functionality. It is never used for advertising, marketing, data brokerage, credit, or insurance decisions.

Records and content you create

Yoked stores training programs, workout history, body-weight history, meal logs, saved foods and recipes, custom meal types, app settings, weekly missions, and progress photos using Apple's SwiftData framework. On iPhone, iPad, and Mac, these records synchronize through a private CloudKit container (iCloud.pro.yoked.yoked.encrypted-v2). Personal values use fields configured for CloudKit encryption; synchronization metadata remains available to CloudKit as described above. Records are not placed in a public or shared CloudKit database.

Photos you select for Yoked are stored as private app data. Package-label photos may also be sent for community-food review after the confirmation described below. Yoked does not provide public photo sharing.

Programs you choose to share

You can choose to share a program through a link or program file using your device's sharing tools. This includes program and routine names, the program description, exercise names and notes, planned sets, repetitions and weights, rest and progression settings, and icons and colors. It does not automatically include logged workout history, completed sets, completion dates, personal records, body-weight logs, meals, sleep, profile details, or Apple Health records. Information you put in a program name, description, or exercise note is included, even if it contains personal or health information.

Yoked creates the link or file locally. The full plan in a share link is encoded after the # character and decoded by the recipient's browser or Yoked app. That part is not sent in the ordinary website request, and Yoked does not upload the full plan to a program-sharing database. Encoding is not encryption: anyone with the complete link or file can read, copy, or forward its contents. Your chosen messaging, mail, or file-sharing service handles the shared item under its own privacy terms.

To display the website and link preview, the public part of the URL includes the program name, routine and exercise counts, up to three routine names, and the program icon, emoji, and theme tint. Our website host receives these summary details along with ordinary request information described below. Preview images can be cached by the host, browser, or messaging service. The full program description and planned weights are not added to these public preview parameters.

Private challenges you choose to join

When private challenges are available in your app version, creating or joining a challenge asks you to agree to share a chosen name, optional emoji, and weekly counts of completed Yoked workout days. Your phone calculates the counts. The challenge service does not receive your individual workout records, exercises, weights, workout dates, or imported Apple Health records. We do not access your Contacts or read the members or messages of your group chat.

The service is hosted by Vercel, with a separate PostgreSQL database provided by Neon. It stores challenge rules and dates, an opaque installation identifier, a hash of an installation credential, invitation tokens, membership status, chosen names and emoji, and weekly counts. These records are not stored in a shared CloudKit database. They are used to operate the challenge and prevent abuse, not for advertising or marketing.

Approved participants can see their group's leaderboard. The host also sees requests and removed or declined memberships. An invitation reveals challenge rules and the accepted participant count; the host must approve a new participant before they can see the leaderboard. Names do not have to be unique or match your real name. Access uses a credential stored in your device's Keychain, rather than a recoverable Yoked account. Losing that credential can mean losing access to the membership.

Leaving a challenge removes your shared membership name and score. The host can delete the challenge and its member records. A removed or declined membership can remain visible to the host to prevent rejoining through an old invitation. Challenge history otherwise remains until it is removed; opaque identity and abuse-prevention records can remain separately. Rate-limit records use a keyed hash of the network address and expire; a daily task removes expired rate-limit records. Ordinary hosting request information is handled as described under website and support below.

If you explicitly share a standings image, it contains the displayed participant names and scores, and recipients can copy or forward it. Your messaging provider handles shared invitations and images under its own terms. Invitation tokens are carried after the URL's# character; the generic website page does not fetch or display a private leaderboard.

iPhone, iPad, Mac, and Apple Watch communication

CloudKit can queue changes while a device is offline and reconcile them later. An in-app Sync Now action saves pending local work and asks the system to check for CloudKit events; it cannot prove that every offline device is already current.

The iPhone sends program snapshots to its paired Watch. The Watch returns live and completed workout events to the iPhone using stable identifiers, and the iPhone then publishes applicable completed records to the private CloudKit store.

App Store purchases

Apple processes Yoked Pro subscriptions and lifetime purchases. Yoked uses StoreKit's verified transaction state to unlock the app. Yoked does not receive your payment-card information and does not operate a purchase server.

On iPhone and iPad, RevenueCat receives purchase and subscription information, including product and transaction details, trial status, renewals, expiration, and refunds. We use it to understand purchases and campaign performance, choose which available plans to show, and check that purchase reporting agrees with StoreKit. RevenueCat receives a pseudonymous Yoked analytics identifier, app version and platform, the screen a purchase came from, and purchase-status checks. StoreKit remains responsible for whether Yoked Pro is unlocked.

App-usage analytics and shared identity

TelemetryDeck receives a limited set of app-usage events from iPhone and iPad: onboarding steps and completion, onboarding save failures, returning-user paywall exposure, and milestones such as the first workout started, first set logged, second workout completed, and first meal logged. Onboarding events include the step and whether you are setting up Yoked or changing your plan; workout events can indicate whether the action originated on iPhone or Apple Watch. The SDK also includes technical context such as app version, operating-system version, device model, and locale. These events help us understand where people have difficulty and which features they use. They do not include workout exercises, weights, repetitions, meal contents, nutrition values, body measurements, sleep records, progress photos, HealthKit records, or text you enter.

Existing installations retain their random analytics identifier. New installations resolve a random identifier stored in a private CloudKit record associated with your Apple Account before starting RevenueCat and TelemetryDeck reporting, then keep a local Keychain copy. If that identity cannot be resolved, that reporting waits. This helps associate new installations with the same analytics identity across devices; older installations may retain different identifiers. RevenueCat receives the random Yoked identifier. TelemetryDeck receives a hashed version, and Yoked supplies that TelemetryDeck identifier to RevenueCat so purchase events can be associated with the same app-usage history. These records are pseudonymous, rather than anonymous: an identifier connects events over time, even though Yoked does not attach your contact information, Apple Account credentials, or CloudKit's own user identifier. We do not join these events to your private CloudKit fitness records.

RevenueCat and TelemetryDeck SDKs run in the iPhone/iPad app. Mac, Apple Watch, and widgets do not directly include these SDKs. A workout action relayed by Apple Watch can still cause the iPhone app to record one of the milestones above.

The current iPhone/iPad app starts RevenueCat and TelemetryDeck reporting after its analytics identity is available. It does not currently include an in-app analytics opt-out switch. Contact the privacy address above with an objection or other request about this processing.

Apple Ads attribution

On iPhone and iPad, RevenueCat collects an Apple AdServices attribution token and uses it to obtain available Apple Ads attribution information. This can include whether an install came from an ad, campaign, ad-group, keyword, placement and ad identifiers, country or region, and attribution timing where Apple provides it. We use this information with purchase reporting to measure how our Apple Ads campaigns perform. We do not request the device's advertising identifier (IDFA), display ads in Yoked, or use these services to track your activity across other developers' apps and websites.

You can read more about how these providers handle information in RevenueCat's privacy policy, TelemetryDeck's privacy information, and Apple's AdServices explanation.

Meta automatic app events

Starting with iOS/iPadOS 1.3.1, Yoked initializes Meta's SDK at app launch with automatic app events enabled. Meta can receive installation, activation and session events, and automatically reported in-app purchase information. This is not limited to counting installs. We use this reporting to understand app use and measure campaigns promoting Yoked. Yoked does not add custom Meta events or supply Meta with HealthKit records, workout details, meal contents, nutrition values, body measurements, sleep records, progress photos, or AI conversation content.

The SDK includes a persistent, randomly generated app-scoped identifier and basic app and device information, such as app version, operating-system version, device model, and locale. Meta also receives ordinary network request information, including your IP address. The identifier lets Meta associate events from the same app installation over time, so we treat these events as pseudonymous rather than anonymous. It is separate from Yoked's CloudKit-backed analytics identity: Meta does not wait for that identity or receive it from Yoked. The Meta SDK runs only in the iPhone/iPad app, not in the native Mac app, Apple Watch app, or widgets.

Yoked explicitly disables Meta's advertising-identifier (IDFA) collection and does not request tracking authorization. On supported iOS and iPadOS versions, Meta's SDK reads Apple's tracking authorization status and uses its opt-out path when tracking is not authorized. Before initializing the SDK, Yoked also sets Meta's event-data usage limit, which Meta documents as restricting event use to analytics and conversions. These statements describe Yoked's configuration, not an independent audit of Meta's systems. Meta handles information under its Privacy Policy.

This reporting is automatic in iOS/iPadOS 1.3.1 and does not currently have an in-app opt-out switch. Contact the privacy address above with an objection or another request about this processing.

Apple Intelligence features

Yoked uses Apple's Foundation Models framework for personal coaching, meal estimates, and other Apple Intelligence features. Depending on the feature, device, operating system, and availability, processing uses Apple's on-device model or Apple's Private Cloud Compute. The separate, optional community-food contribution service uses Google Gemini through a Yoked-operated server, as described below. Personal coaching and meal-estimation requests are not sent to Gemini.

Private Cloud Compute requests can include your message and relevant conversation history; your fitness profile, goals, and training preferences; workout and lift history; body-weight trends; nutrition and protein summaries; and relevant activity or sleep summaries from Apple Health that you have authorized Yoked to read. This context is used to personalize fitness guidance, summaries, and recommendations. Meal estimation can process a meal description or a selected meal image. Form review can process a selected photo or sampled still frames from a selected video, along with an optional note; form-review audio is not sent.

Supported AI features can use Apple's Private Cloud Compute when it is available, without a separate Yoked-specific permission prompt or cloud AI settings toggle in current releases. Home guidance can refresh automatically when its context is ready and can use Private Cloud Compute when available; cloud processing is not limited to a message you manually send. Apple Health authorization remains separate and optional: you choose which Health data types Yoked can access through Apple's permissions settings. Private iCloud synchronization described above is also separate from AI processing. If you are still using build 142, its earlier Allow Apple Cloud AI prompt and device-level Settings control apply only to that build.

Apple describes the security and privacy of its cloud processing in its Private Cloud Compute overview. AI responses and nutrition estimates may be inaccurate; review and edit an estimate before saving it. Selected media used for form review is not saved in chat history. Saved conversations and other records remain subject to the private iCloud synchronization described above.

On iPhone and iPad, you can optionally dictate that meal description. When you tap Dictate and grant Microphone and Speech Recognition access, Yoked configures Apple's speech recognizer to require on-device transcription. Yoked does not permit Apple's server-based speech recognition as a fallback; if on-device recognition is unavailable for the current language and device, the Dictate control is unavailable and you can type instead. Yoked does not save or synchronize the captured audio. The resulting text remains editable, and any meal you choose to save is handled like the other meal records described above.

Community food contributions

When the community food service is available, contributions are enabled by default, but no label photo is uploaded until you choose Save and contribute at the first eligible save. You can instead choose Save privately. After confirmation, new barcode-linked package labels are contributed automatically until you disable Contribute packaged foods in Settings. Existing food history and photos are not uploaded retroactively. Disabling contributions cancels unsent items; it does not remove product facts already published for other users.

Contributions include the barcode, product name, brand, printed serving size, nutrition values, and package-label photograph. They exclude meal dates, consumed amounts, Health records, workout history, personal notes, and advertising identifiers. Photograph only the product label and name. Yoked removes photo metadata such as GPS before upload. The visible pixels may still contain information you photographed.

A dedicated service hosted through Vercel and Supabase stores submissions and private label images. Google Gemini processes the label image and product information to review accuracy. Paid API processing is used. Under Google's paid API terms, these inputs and responses are not used to improve its products. Google may retain them for a limited period for safety, abuse prevention, and legal requirements. See Google's Gemini API terms. AI review can make mistakes; you can submit a new label to correct a product. Accepted product facts become available to other Yoked users; photos, contributor identifiers, and private review details do not.

Apple App Attest verifies the app without a Yoked login. The food service keeps an installation-specific public key, submission identifiers, and verification counters to prevent replay and abuse. It does not use the advertising or analytics identity. Network providers receive ordinary connection information, including the source IP. Application rate-limit records use a keyed hash of the IP and expire automatically.

Uploaded evidence images become eligible for deletion after 90 days and are removed by the daily cleanup job. Product revisions and structured moderation records are retained to operate and correct the catalog. Images from private uploads that are never submitted become eligible for cleanup after one day. Personal barcode foods remain in your private iCloud library. Contact support@yoked.pro for questions or requests concerning a contribution.

Where European data-protection law applies, we rely on your consent for optional label-photo contributions and on legitimate interests to secure the service and prevent abuse. Turn off contributions to withdraw permission for future uploads; contact support to request removal of previously submitted private evidence. Withdrawal does not affect earlier lawful processing. Public product facts and non-personal revision history may remain available.

Contribution terms

By choosing Save and contribute, you confirm that you may share the package-label image and information. You grant Yoked permission to store and process the image for review, including through Google Gemini, and to use, correct, and redistribute the submitted product facts as part of the food catalog. Submit information from the actual package; do not copy another food database or include personal information. Moderation may decline a submission. Public product facts can remain in the catalog after contributions are turned off. This permission does not cover your meal history.

Food-data lookups

When you explicitly search for a branded food, Yoked sends the search text to the Yoked community catalog and Open Food Facts (openfoodfacts.org). Barcode scans first check personal foods and cached results, then automatically send the barcode to the Yoked catalog and, when needed, Open Food Facts while online. These requests retrieve product names and nutrition facts. Yoked does not intentionally attach a Yoked account identity (Yoked has no account system), health history, or advertising identifier. Open Food Facts necessarily receives the request's network-source IP address and other ordinary network-request information. Yoked cannot independently guarantee whether Open Food Facts retains or links those details; Open Food Facts handles them under its own terms and privacy policy.

The bundled common-food catalog and your private My Foods library do not send search text to Open Food Facts. A network lookup occurs only in the branded-food search or barcode flow.

Permissions Yoked may request

• Apple Health on iPhone and iPad — for the read and write functions described above.
• Apple Health on Apple Watch — for active workout sessions, including live heart rate and active energy.
• Photos and selected files — to choose progress or meal images and export data. Mac uses system file and photo pickers.
• Camera on iPhone and iPad — for barcode scanning and supported photo workflows.
• Microphone and Speech Recognition on iPhone and iPad — for optional meal-description dictation only when you tap Dictate. Transcription is required to run on device; Yoked does not allow server recognition as a fallback.
• Notifications — for rest timers and optional reminders.
• iCloud — to synchronize the private Yoked database across iPhone, iPad, and Mac.

You can change permissions in Apple Settings. Declining Apple Health access does not prevent manual Yoked logging.

Your control over your data

Yoked provides controls to edit and delete user-created records and a versioned JSON export for recovery. Because private iCloud synchronization can retain records for your other devices, deleting the app from one device does not delete all synchronized Yoked data. Delete records within Yoked before uninstalling and review Apple's iCloud storage controls if you want to remove the private cloud copy.

Deleting a Yoked record does not automatically remove information you separately chose to save in Apple Health or Photos unless Yoked explicitly offers and completes that deletion. You can review those system stores in Apple's Health and Photos apps.

Deleting Yoked records or uninstalling the app does not automatically delete purchase or analytics records held by RevenueCat, TelemetryDeck, or Meta. Contact support@yoked.pro with privacy requests about these records. We may need information to locate the relevant pseudonymous records; do not send health records or payment-card details with your request.

Website visits and support messages

Our website is hosted by Vercel. When you visit, the hosting service receives ordinary request information such as your IP address, browser information, requested page, and request time to deliver and secure the website. We have not added advertising pixels, Vercel Web Analytics, or a separate website analytics SDK to this site. The app analytics described above are separate from visits to the website. Links to Apple and other providers take you to services covered by those providers' privacy notices.

The contact page opens your email application; it is not a form that uploads your message to the website. If you contact us, we receive your email address, your message, and any attachments you choose to send. We use that information to respond, investigate the issue, and handle privacy requests. Please send only what is needed and omit sensitive health information, passwords, and payment-card details unless specifically necessary for your request.

Legal bases for website, support, and purchase administration

Where the GDPR applies, we use the following bases for these purposes:

• Providing a service you request (Article 6(1)(b)). We use necessary transaction information to provide or restore purchased access, and support information where necessary to perform our contract with you or take steps you request before entering one. Purchase analytics and advertising measurement are separate purposes from unlocking your purchase.
• Legitimate interests (Article 6(1)(f)). We use ordinary website request information to operate and secure the site, and support correspondence to answer general questions and troubleshoot problems. These interests are providing a reliable service and responding to people who contact us, subject to their rights and interests.
• Legal obligations (Article 6(1)(c)). We process information needed to fulfil applicable GDPR duties, including responding to privacy rights requests.

Health information has additional protection under European law. The Apple permissions described above control access to particular data types; granting a device permission does not waive your privacy rights. Declining Apple Health access still allows manual logging. Revoking Health access stops future reads from Apple Health for those data types, but does not itself erase records already stored in Yoked or private iCloud copies.

How long information is kept

• Private app records. Records are kept on your devices and in your private iCloud database until you delete them using the applicable app or Apple storage controls. Synchronization can keep deletion markers and reconciliation metadata so records are not recreated by an offline device. Separate Apple Health, Photos, and device backups have their own storage and deletion controls.
• Purchase and attribution records. RevenueCat records can remain during our use of its service, including after a subscription ends or the app is uninstalled. There is no app-uninstall deletion trigger. Contact us about records associated with your pseudonymous identifier. Deleting a RevenueCat record does not cancel an Apple subscription; subscription management remains with Apple.
• Usage events. TelemetryDeck's reporting windows do not mean that older events are deleted. Its published retention information says older events can remain in cold storage without a fixed deletion schedule. See TelemetryDeck's retention explanation. Uninstalling Yoked does not itself remove those events.
• Meta app events. Deleting records in Yoked or uninstalling the app does not send Meta a request to delete its event records. Meta's retention and deletion practices are described in its Privacy Policy. Contact us about privacy requests concerning this integration.
• Support correspondence. Retention depends on whether a request remains open, whether the correspondence is needed for follow-up support or to document a privacy request, and whether an applicable legal obligation or dispute requires it. Contact us to request deletion; we will explain any information that must be retained and why.
• Shared programs and previews. Links and files are self-contained copies with no Yoked-managed expiration or revocation. Deleting or editing the original program does not change copies already shared. Copies can remain in recipients' apps, messages, files, or browser history. Website preview images are currently configured for caching for up to one day; hosting request records and other providers' caches follow their own retention and deletion practices.
• Website request information. Vercel's privacy notice describes retention by purpose rather than a single fixed period for all information. Relevant purposes include maintaining its services, meeting legal and contractual requirements, and handling disputes. See Vercel's privacy notice.

Service providers and international processing

We are based in the United States, so information you send directly to us, including support messages, is handled there. Your information is not all stored in the European Economic Area (EEA). The providers described in this policy receive the information needed for their respective functions:

• Apple provides the App Store, private iCloud storage, device services, and available cloud AI processing. Apple's services can involve international processing. See Apple's privacy information and the Private Cloud Compute information linked above.
• RevenueCat uses infrastructure in the United States for purchase, subscription, and attribution processing. Its published Data Processing Addendum provides Standard Contractual Clauses for restricted transfers covered by that agreement.
• TelemetryDeck states that it hosts usage data in the European Union. See its hosting and security information. Yoked's shared analytics identity remains pseudonymous as described above; EU hosting does not make that identity anonymous.
• Meta receives the automatic app events described above, starting with the iPhone/iPad 1.3.1 release. See Meta's Privacy Policy for its handling of information, including international processing.
• Google and Supabase process community-food submissions as described above. Storage is hosted in the United States; Google may process API data in countries where it or its service providers operate. Their terms describe applicable data-protection arrangements. See Google's API terms and Supabase's privacy notice.
• Vercel may process website and food-service request information in the United States and other countries. Its privacy notice describes international processing and safeguards for its services. Open Food Facts separately receives the network requests described in the food-data section.

Contact support@yoked.pro for information about a particular transfer or a copy of applicable safeguards. A provider's published terms do not mean that every processing activity has the same location, role, or transfer arrangement.

Your European privacy rights

If the GDPR applies to your information, you have the following rights, subject to the conditions and exceptions in that law:

• Request access to your personal information and a copy of it.
• Ask for inaccurate information to be corrected or incomplete information completed.
• Request deletion or restriction of processing where the legal conditions apply.
• Receive information you provided in a structured, commonly used, machine-readable format and request transfer to another controller where technically feasible, when automated processing is based on consent or a contract.
• Object, for reasons relating to your situation, to processing based on legitimate interests. If information is used for direct marketing, you can object to that use at any time.
• Withdraw consent at any time where processing relies on it. Withdrawal does not affect the lawfulness of processing before withdrawal. Device permissions can be changed through Apple's settings; contact us about other consent or privacy requests.

Email support@yoked.pro and explain the request. You do not need a Yoked account. We may ask for proportionate information to verify a request or locate pseudonymous records; please do not send identity documents or health records unsolicited. If we cannot identify the records, we will explain that and what additional information could help. Some records are controlled directly through your devices or Apple Account, as explained above.

Under the GDPR, the normal response deadline is one month after receipt. If complexity or the number of requests requires up to two additional months, we will explain the extension within the first month. Requests are normally free. If a request is refused or an exception applies, we will explain the reason and your options.

You can complain directly to a data protection authority, particularly in the EEA country where you live or work, or where an alleged infringement occurred. You do not have to contact us first. Find your authority in the EDPB authority directory.

Age eligibility

Yoked is intended only for adults age 18 or older. If you are under 18, do not use the app.

Changes to this policy

We will update this policy if Yoked's data practices change and revise the Last updated date.

Contact

For privacy questions or support, email support@yoked.pro.