Last updated: 1 October 2026
Policy version: 1.5
ALLTHRYV LTD (company number 17076299), trading as THRYV ("THRYV", "we", "our" or "us"), is committed to protecting your privacy.
This Privacy Policy explains how we collect, use, store and share personal data when you use the THRYV mobile application, Apple Watch app, website and related services (together, the Service).
THRYV is a health, fitness and wellbeing service that brings together nutrition, movement, recovery and personalised digital coaching. THRYV is not a medical service and does not provide medical diagnosis or treatment.
This policy is intended to meet the requirements of the UK General Data Protection Regulation (UK GDPR), the Data Protection Act 2018 and applicable Apple platform requirements.
1. Who We Are
ALLTHRYV LTD is the data controller responsible for personal data processed through the Service.
- Company: ALLTHRYV LTD
- Company number: 17076299
- Trading name: THRYV
- Country of establishment: United Kingdom
- Registered office: 24 Hazel Close, Taverham, Norwich, England, NR8 6YE
- Privacy contact: privacy@allthryv.com
If you have questions about this policy or how we handle your data, please contact us using the email address above.
2. Who Can Use THRYV
THRYV is intended for people aged 16 or over. We do not knowingly allow children under 16 to create an account or provide personal data through the Service.
If we learn that we have collected personal data from a child under 16, we will take reasonable steps to delete it.
For people aged 16–17, optional product analytics and remote AI are unavailable. These optional features also stay off until adult eligibility has been confirmed. This restriction does not change the minimum age for THRYV.
3. Personal Data We Collect
The information we collect depends on the features you use, the permissions you grant and whether you use THRYV without an account or create an account.
3.1 Account and profile information
When you create or manage a THRYV account, we may collect:
- first name and surname;
- email address and optional telephone number;
- password credentials, stored as a secure hash or managed by our authentication provider;
- date of birth;
- gender, where provided;p
- country, region, time zone and unit preferences;
- profile image;
- account role, subscription tier and account status;
- Terms acceptance date/version and separate health, remote-AI and analytics consent decisions where applicable, including the purpose, statement/notice version, language, method, decision and time; and
- sign-in provider identifiers where you use Apple or Google sign-in.
For email registration, first name, surname, email address and a password are required to create the account. If you do not provide them, we cannot complete email registration. Apple or Google sign-in uses the information supplied by that provider instead. A telephone number and profile photo are optional. Analytics, optional remote AI, photos and connected-service access are not conditions of account creation.
We do not receive your Apple or Google account password.
3.2 Health, fitness and wellbeing information
THRYV lets you record, import and analyse health, fitness and wellbeing information. Depending on the features you use, this may include:
- height, weight, body measurements and weight goals;
- age, gender, activity level and fitness goals;
- nutrition targets, meals, ingredients, recipes, barcodes, calories, macronutrients, micronutrients, water and caffeine intake;
- meal descriptions and optional meal photographs;
- steps, active energy, exercise minutes, workouts, workout plans, completed exercises, sets, repetitions, weights, duration, distance, pace, cadence, heart rate and personal bests;
- GPS location and route points collected during supported distance-based workouts;
- sleep duration, sleep stages, sleep quality, bedtime and wake-time information;
- resting heart rate, heart-rate variability, respiratory rate, blood oxygen information and other supported health summaries;
- mindfulness activity, mood and recovery information;
- menstrual-cycle information and related insights, where you enable those features;
- equipment, training preferences, dietary preferences, allergies or avoidances; and
- notes, feedback, goals, coaching preferences and other information you choose to provide.
Some of this information is special category health data under UK data protection law. We process it only for the health, fitness and wellbeing purposes described in this policy and, where required, with your explicit consent.
3.3 Apple Health and connected services
If you choose to connect Apple Health, THRYV may read health and fitness data that you specifically permit through Apple's HealthKit permission controls. Depending on the permissions you grant, this may include activity, workout, body measurement, heart, respiratory, sleep, mindfulness and cycle information.
THRYV may also write supported information, such as completed workouts or weight entries, to Apple Health where you grant write permission.
You control HealthKit access at data-type level through Apple Health and iOS Settings. THRYV cannot use HealthKit data for advertising, marketing or sale to data brokers, and we do not do so.
If you connect another service, such as Strava or Garmin where available, we receive only the information covered by the permissions shown during that connection. You can disconnect an external service from THRYV and, where applicable, from the provider's own settings.
3.4 Camera, photo library and files
If you choose to use relevant features, THRYV may access:
- meal photos for nutrition analysis;
- photos, videos or files that you attach to a support request;
- a photo selected as your profile image; and
- live camera frames for supported exercise rep-counting features.
Live camera processing used for exercise rep counting is designed to run on your device. Meal photos, support attachments and profile photos are transmitted only when you choose to submit or upload them.
3.5 AI inputs, outputs and feedback
When you use AI-assisted features, we may process:
- questions, prompts, meal descriptions and refinement instructions;
- meal photos submitted for analysis;
- relevant profile, goal, nutrition, activity, workout, recovery or equipment context;
- generated plans, recommendations, summaries, coaching responses and audio prompts;
- actions you choose to review or confirm; and
- feedback you provide about an AI response.
We limit AI context to information relevant to the feature you are using. Further information about AI processing is provided in section 6.
3.6 Subscription, transaction and referral information
Purchases are processed by Apple through the App Store. We do not receive your payment card details.
We may receive and store:
- App Store product and subscription identifiers;
- subscription status, renewal, expiry, grace-period, refund and restore information;
- transaction identifiers and an account-linking token used to associate an App Store subscription with your THRYV account;
- offer-code and reward status; and
- referral or affiliate codes used during sign-up.
If you sign up using an affiliate referral code, limited information may be shown to the referring affiliate for attribution and commission administration. This is limited to your first name, sign-up date, subscription status and whether the referral remains active. We do not provide the affiliate with your health, fitness, nutrition, location, contact details or payment-card information.
3.7 Support requests and other content
When you contact us or use support and feedback features, we may collect:
- the subject and content of your request;
- messages exchanged with our support team;
- optional screenshots, videos, diagnostic logs or other attachments;
- feature requests and product feedback; and
- identity-verification information where reasonably required to handle a privacy-rights request.
Please avoid including information that is not necessary for us to deal with your request.
3.8 Device, security, analytics and diagnostics information
We may automatically collect limited technical information needed to operate, secure and improve the Service, including:
- device model, operating-system version, app version and build number;
- internal account identifiers and push-notification tokens used for account or diagnostic operations, and random pseudonymous installation or browser identifiers used for optional analytics;
- IP address and request metadata used for security, rate limiting and fraud prevention;
- feature interactions and operational events;
- crash reports, error details, stack traces, performance information and session diagnostics; and
- network and service reliability information.
We use Sentry for crash and limited operational diagnostics. Default personal-information collection is disabled. The iOS integration does not enable session replay or session recordings. The iOS integration clears account-user context rather than attaching your THRYV account ID. Sentry diagnostics are separate from the optional product analytics described below.
#### Optional product analytics
We use PostHog to understand broad use of THRYV and improve the app and public website. Analytics is optional and is not required to use the Service. We do not send analytics events from before you opt in, and we do not replay or backfill those events later.
On iOS, the optional choice appears after Welcome in shared onboarding. It is off if you have not already made a choice, and you can continue with it off. You can change the choice later in Settings > Privacy & Security. For signed-in users, the choice is saved with the THRYV account and applies across the signed-in iOS app and website. For guest users, it stays on the device. When enabled, PostHog receives only app session starts, onboarding start/completion/abandonment, selected feature opens, paywall views, subscription activations, and workout starts/completions. Workout events include only a broad activity type and whether the workout was planned. They do not include workout measurements. Recipe, meal, sleep, plan, workout-discard and individual onboarding-step events remain on the device and are not sent to PostHog.
On the public website, PostHog receives page views as broad page categories, clicks on App Store links with the page category and button placement, and clicks on affiliate contact links with their placement. These events measure a click only; for example, an affiliate contact click does not mean that a lead or purchase was completed. The event data does not include full page URLs, query strings, fragments, referral codes, or text you enter.
Our Backend may send limited subscription lifecycle events after the associated account has opted in, such as a trial starting, a paid subscription starting or renewing, access ending, or a refund being recorded. Events generated before consent are discarded and are not sent later. These events use a single shared service identifier for aggregate counts; they are not attached to an individual PostHog user profile.
All delivered events include the event name and time, source and app environment (development, staging or production). iOS events may also include platform, app version and a coarse subscription tier. Website events include only the broad page category or button placement needed for the event. Backend subscription events include an event-producer label, an allowlisted originating source (or `unknown`), and a coarse subscription tier or monthly/annual billing period where applicable. iOS and website events use a random pseudonymous identifier for the app installation or browser so activity can be grouped on that installation or browser over time. Separate installations and browsers are not joined through your THRYV account. The Backend checks your account's consent internally but does not send your account ID, name or email address to PostHog. We do not send purchase receipts, transaction IDs, recipe or meal contents, sleep measurements, GPS routes, body measurements, AI prompts, or raw workout measurements to PostHog.
This is pseudonymous, not anonymous, analytics: a random installation or browser identifier can distinguish repeated events from the same installation or browser. We do not use your THRYV account ID to identify you in PostHog. Our current PostHog project is configured to anonymise IP addresses. Our app and website integrations send only the named events above; they do not use PostHog session replay, session recording, surveys, or automatic interaction capture.
We do not use this analytics information for cross-app advertising, behavioural advertising, or sale to data brokers.
3.9 Website cookies and local storage
Our public website and portal use cookies or browser storage to maintain a secure signed-in session, remember your cookie and analytics choices, prevent abuse, and maintain service reliability. The cookie preference is kept in your browser for up to 180 days. You can change or withdraw your website analytics choice at any time using Cookie preferences on the website.
PostHog's random browser identifier is stored in browser local storage where available, or kept in memory for the browser session if storage is unavailable. It is created only when analytics is allowed and cleared when you withdraw consent or sign in, sign out, or change the signed-in account. We do not place or access these optional analytics identifiers until you have chosen to allow analytics. For a signed-in website user, both the browser's cookie choice and the account's analytics preference must allow collection. An account choice does not by itself enable analytics in a browser where analytics has not been allowed.
Browser local storage does not give this PostHog identifier a fixed expiry. It remains until it is cleared through the controls described above, you clear your browser storage, or the browser removes it. This is separate from how long PostHog retains events already received.
We do not use health or fitness data for website advertising or behavioural marketing. We do not use advertising cookies or sell analytics information to data brokers.
4. How We Collect Personal Data
We collect personal data:
- directly from you when you create an account, complete onboarding, log information, use a feature, upload content or contact support;
- from your device when you grant a permission, such as HealthKit, location, camera, photo-library or notification access;
- from Apple in connection with App Store subscriptions, Sign in with Apple, Apple Health, push notifications and other Apple services;
- from Google or another sign-in provider when you choose that sign-in method;
- from connected services that you explicitly authorise;
- automatically through security, operational and diagnostic systems; and
- from an affiliate or referral link when you choose to use one.
5. How We Use Personal Data
We use personal data to:
- create, authenticate and manage your account;
- provide guest, free and paid THRYV features;
- calculate and display nutrition, movement, recovery, Daily Energy and THRYV Score information;
- provide workout tracking, plans, reminders, insights and progress information;
- import or write information through Apple Health and other services you connect;
- generate AI-assisted meal estimates, plans, coaching, summaries and audio;
- save and synchronise information across supported devices and services;
- process and verify subscriptions, rewards, referrals and entitlements;
- send transactional, service, support and push-notification messages you have enabled;
- answer support requests and privacy-rights requests;
- detect abuse, secure accounts, enforce limits and prevent fraud;
- diagnose crashes, monitor performance and improve reliability;
- understand how people use the app and public website, measure selected feature and subscription events, and improve the Service using the limited or aggregate product-analytics information described in section 3.8;
- improve existing features and develop new ones using appropriately limited or aggregated information;
- comply with law, regulatory requirements and valid legal requests; and
- establish, exercise or defend legal claims.
We do not sell personal data. We do not use HealthKit, health, fitness or precise-location data for advertising, marketing profiling or sale to data brokers.
6. Artificial Intelligence and Automated Processing
THRYV uses a combination of on-device processing, deterministic calculations and remote AI services.
6.1 On-device AI
Where a compatible Apple device and feature support on-device generation, relevant information may be processed locally using Apple's on-device technologies. Information processed solely on device for that generation is not sent to THRYV or a third-party AI provider for the purpose of generating that response.
6.2 Third-party AI processing
Some features require or may fall back to remote AI processing. For those features, THRYV sends the minimum information reasonably needed to our backend and an AI service provider. Our current remote AI provider is OpenAI.
Depending on the feature, the information sent may include:
- meal text or a meal photograph;
- selected profile, goal, equipment or dietary context;
- bounded summaries of workouts, activity, nutrition, sleep or recovery;
- a question or instruction you submit; and
- information needed to generate a plan, response or audio prompt.
We do not send your THRYV password or payment-card information to an AI provider.
OpenAI states that data submitted through its API is not used to train or improve its models unless the API customer explicitly opts in. We do not opt in to using your content for general model training. OpenAI may retain API abuse-monitoring logs containing prompts, responses or related metadata for up to 30 days by default, unless a shorter retention control applies, longer retention is legally required, or longer retention is reasonably necessary to protect its services or others from harm. Some API features also retain temporary application state. For example, prompt caching may retain encrypted intermediate data for up to 24 hours. This is separate from THRYV's storage of AI outputs that you choose to save.
THRYV may retain operational AI request metadata and, where diagnostic audit logging is enabled, redacted request or response records for up to 90 days to investigate failures, security issues and service quality.
6.3 Consent and control
Terms acceptance is separate from permission to process health information and from optional remote AI. THRYV asks for an explicit health-processing choice before relevant health features can operate. This applies to email, Apple/Google sign-in and guest use, including existing users without a recorded choice. HealthKit and other device permissions remain separate controls.
Remote AI has its own explicit choice identifying OpenAI and the relevant health/fitness context. It starts off, requires health-processing permission and confirmed adult eligibility, and is not required to create an account. Declining it prevents requests or automatic fallbacks that would send your personal or health context to remote AI. Compatible on-device processing can remain available where supported and health processing is permitted.
You can change or withdraw these choices in Settings > Privacy & Security > Privacy choices. Withdrawal stops the relevant new processing locally; an offline account-wide change is queued until it can reach the server. Requests already in transmission may finish. You can also contact privacy@allthryv.com for assistance or deletion of retained information.
Withdrawal does not make earlier lawful processing unlawful. Features that require withdrawn health processing become unavailable, and you can still access account-management and privacy-request routes. Turning a processing permission off is separate from deleting saved records or your account; section 13 explains those choices.
6.4 No significant automated decisions
THRYV's scores, plans, recommendations and AI outputs are intended to support your own decisions. They do not produce legal or similarly significant effects and are not medical diagnoses. Where an AI feature proposes saving or changing information, THRYV is designed to let you review or confirm the result before it is applied.
7. Our Legal Bases for Processing
The basis depends on the purpose for which we use the information:
| Purpose | UK GDPR legal basis | |---|---| | Create/authenticate your account, provide requested account features and synchronisation | Performance of our contract with you, Article 6(1)(b). Health information additionally requires the condition described below. | | Record, import and analyse your health, fitness and wellbeing information for the features you choose | Consent, Article 6(1)(a), and explicit consent under Article 9(2)(a) where the information is special category health data. | | Optional remote AI using your personal or health context | Consent, Article 6(1)(a), and Article 9(2)(a) for health information. | | Optional product and website analytics | Consent, Article 6(1)(a), and applicable consent for storage/access technologies. The limited workout-event scope described in section 3.8 is included in the explicit consent statement where health information is involved. | | Necessary account security, abuse prevention and minimised fault diagnostics | Legitimate interests, Article 6(1)(f): protecting users and keeping the Service secure and reliable. This does not authorise optional session recordings. | | Verify subscriptions and provide requested entitlements | Performance of our contract, Article 6(1)(b). | | Administer voluntarily submitted referral codes and affiliate commissions | Legitimate interests, Article 6(1)(f): attributing referrals and administering the programme, using limited information. | | Answer service support requests | Performance of our contract, Article 6(1)(b), where needed to support the requested Service. Please avoid including unnecessary sensitive information. | | Handle statutory privacy requests/complaints and comply with required accounting or other applicable legal duties | Legal obligation, Article 6(1)(c). | | Establish, exercise or defend legal claims | Legitimate interests, Article 6(1)(f), or a legal obligation where applicable. Article 9(2)(f) applies only where processing health information is necessary for the relevant legal claim. |
We assess the necessity of processing based on legitimate interests and balance those interests against your rights. We do not rely on that basis where your interests or fundamental rights override ours.
Permission in iOS, Apple Health or a connected provider controls technical access; it does not replace a separate explicit consent statement where health-data processing requires one. Optional website analytics is not enabled until you choose Allow analytics. For a signed-in browser, the local browser choice and the account-level analytics choice must both permit collection.
You can refuse or withdraw optional analytics and remote AI without losing access to unrelated features. Withdrawal of health-processing consent prevents features that need that information from processing it further; it does not affect earlier lawful processing. See sections 6 and 13 for controls and deletion choices.
8. Who We Share Personal Data With
We share personal data only where necessary for the purposes described in this policy.
Service providers
Our current service-provider categories and examples include:
- Apple: App Store subscriptions, StoreKit, Sign in with Apple, Apple Health/HealthKit, CloudKit/iCloud where enabled, and Apple Push Notification service;
- Supabase: account authentication and related identity services;
- DigitalOcean: cloud infrastructure and media or attachment storage;
- OpenAI: remote AI generation and generated audio for supported features;
- Sentry: crash and limited operational diagnostics;
- PostHog: optional product analytics from the iOS app and public website, plus limited aggregate subscription lifecycle events from our Backend, as described in section 3.8;
- Google: Google sign-in where you choose to use it;
- connected fitness providers: such as Strava or Garmin where available and authorised by you; and
- communications and support providers: where required to deliver transactional messages or provide support.
Some providers act as processors on our behalf under our instructions and data-protection agreements. Others, including Apple for its own account and App Store activities and sign-in providers for their own services, may act as independent controllers under their own privacy terms. A provider can have different roles for different activities. We require processors acting on our behalf to protect personal data in accordance with applicable law and the relevant agreement.
Affiliates and referral partners
If you voluntarily use an affiliate referral code, we may share the limited referral information described in section 3.6 with the referring affiliate. This is used only to administer attribution, rewards and commission.
Professional advisers and authorities
We may share information with professional advisers, insurers, auditors, regulators, courts, law-enforcement bodies or other authorities where reasonably necessary and lawful.
Business changes
If all or part of our business is reorganised, sold or transferred, personal data may be disclosed to relevant advisers and prospective or actual purchasers, subject to confidentiality and data-protection requirements.
We do not share health, fitness or location data with advertisers or data brokers.
9. Local Storage, Cloud Storage and Synchronisation
Using THRYV without an account
When you continue without an account, supported information is stored locally on your device. It is not linked to a THRYV server account, may not be recoverable if the app is deleted or the device is lost, and can be removed using the Forget account action in THRYV.
Anonymous requests for limited public content or configuration may still include an installation identifier and IP address for rate limiting, security and service delivery.
Using THRYV with an account
When you sign in, information needed for account-backed features may be stored on your device and on THRYV's systems. Depending on your subscription, feature settings and app version, supported records may be synchronised with our backend and across supported devices.
Some app records may also be synchronised using Apple's CloudKit/iCloud services where that capability is enabled. Apple processes that information under your Apple account and Apple's applicable privacy terms. THRYV does not receive your Apple ID password.
10. International Data Transfers
The PostHog integrations are configured to send analytics events to PostHog's EU Cloud endpoint. PostHog describes its EU Cloud as hosted in Frankfurt. Other service providers or their subprocessors may process personal data outside the United Kingdom, including in the European Economic Area or the United States. An EU endpoint does not, by itself, mean that every service operation or subprocessor is located in the EU.
Where a restricted transfer is made, we use an appropriate legal mechanism where required, such as:
- UK adequacy regulations;
- the UK International Data Transfer Agreement;
- the UK Addendum to the European Commission Standard Contractual Clauses; or
- another safeguard permitted by UK data-protection law.
We also consider the nature of the information, the destination and any additional technical or contractual protections that are appropriate.
You can contact privacy@allthryv.com to ask for information about the safeguards applicable to your data and, where relevant, a copy of those safeguards, subject to necessary redactions.
11. How Long We Keep Personal Data
We keep personal data only for as long as reasonably necessary for the purposes described in this policy, including legal, security and dispute-resolution requirements.
Our general retention approach is:
- Guest data: stored on your device until you remove it, use Forget account, delete the app or erase the device;
- Account and profile data: retained while your account is active and removed or anonymised following account deletion, except where limited retention is required by law or for legal claims;
- Health, fitness, nutrition and wellbeing records: retained until you delete the relevant records or delete your account, subject to synchronisation and backup expiry;
- AI provider data: OpenAI API abuse-monitoring logs may be retained for up to 30 days by default, as described in section 6;
- THRYV AI audit records: where enabled, retained for up to 90 days;
- Product analytics in PostHog: PostHog's event-query window is separate from deletion of stored records. Stored events may remain beyond that window unless separately erased. See section 13 for the current withdrawal controls and how to exercise your rights;
- Normal support requests: retained for up to 24 months after closure;
- Diagnostic logs attached to support requests: retained for up to 90 days after closure;
- Support screenshots and videos: retained for up to 12 months after closure;
- Privacy-rights request records: retained for up to six years after completion or closure so that we can demonstrate compliance and handle legal claims;
- Subscription, referral and transaction records: retained as needed for entitlement administration, fraud prevention, accounting, tax and legal obligations;
- Security and diagnostic records: retained for a limited period based on operational need and provider configuration; and
- Backups: deleted or overwritten through our normal backup cycle, unless preservation is legally required.
When information is no longer required, we delete it, anonymise it or securely isolate it until deletion is completed.
12. Data Security
We use technical and organisational measures designed to protect personal data, including:
- encryption in transit;
- secure password hashing and authentication controls;
- access controls based on role and operational need;
- separation of development and production environments;
- logging and monitoring controls;
- private or signed access to protected media where appropriate;
- data minimisation and bounded AI context; and
- processes for account deletion and privacy-rights requests.
No system is completely secure. You should use a strong, unique password, protect your device and contact us promptly if you believe your account has been compromised.
13. Your Rights and Choices
Depending on the circumstances, UK data-protection law gives you the right to:
- ask for access to your personal data;
- ask us to correct inaccurate or incomplete data;
- ask us to delete personal data;
- ask us to restrict processing;
- object to processing based on legitimate interests;
- receive certain data in a portable format;
- withdraw consent at any time;
- complain to the Information Commissioner's Office; and
- obtain information about safeguards used for international transfers.
These rights are not absolute and may be subject to legal exceptions.
Account and local-data deletion
- Signed-in users can request permanent account deletion in THRYV > Settings > Account > Delete Account.
- Users without an account can remove locally stored guest data through THRYV > Settings > Account > Forget account.
- You can also contact privacy@allthryv.com for assistance or to make a privacy-rights request.
We may need to verify your identity before acting on a request. We normally respond within one month, subject to any extension permitted by law.
Permission controls
You can control or revoke device permissions through iOS Settings and Apple Health, including HealthKit, location, camera, photo-library and notification access. You can also disconnect supported external services from THRYV or the provider's settings.
Withdrawing a permission or consent may prevent the affected feature from working, but it does not affect processing that was lawful before withdrawal.
Product analytics and website preferences
You can turn product analytics off at any time in THRYV > Settings > Privacy & Security. On the website, use Cookie preferences to change or withdraw the browser choice. For a signed-in account, the analytics preference is shared with the signed-in iOS app and website, but a browser must also have its own analytics choice set to allow collection. Guest app choices and anonymous website choices remain on the device or browser where you made them.
Turning analytics off immediately stops local event capture. Before clearing local analytics state, the client preserves the known pseudonymous identifiers needed to request erasure of historical events. If offline, the request remains queued locally and is submitted when connectivity returns. An event already in transmission may still reach PostHog.
Erasure requests are handled through our restricted privacy-operations queue. Submission or acknowledgement is not confirmation that PostHog has completed deletion. We confirm deletion of the relevant historical events before treating the request as complete; removing a person profile alone is insufficient. Clearing local storage does not itself erase provider records.
For signed-in users, an offline account-wide preference change may not reach the server until retry succeeds. Other signed-in clients observe changed choices on their next account confirmation, such as login, app launch or browser reload; there is no continuous cross-device refresh.
The installation/browser identifiers are not joined through your THRYV account in PostHog. An account email alone may therefore be insufficient to locate older events, especially identifiers rotated before the erasure record was introduced or on other installations. We assess these requests individually and explain any identification limits or applicable legal exception. You can contact privacy@allthryv.com for assistance with your rights.
14. Complaints
You can make a privacy complaint by emailing privacy@allthryv.com, including if you do not have a THRYV account. Signed-in users can also use the in-app privacy support route.
We acknowledge complaints within 30 calendar days of receiving them. We investigate, keep you informed and explain the outcome without undue delay. This is separate from the usual one-month response period for a privacy-rights request.
You may contact the ICO directly; you do not have to contact THRYV first.
You also have the right to complain to the UK Information Commissioner's Office (ICO):
- Website: https://ico.org.uk/make-a-complaint/
- Telephone: 0303 123 1113
15. Third-Party Links and Services
The Service may contain links to third-party websites, content or services. Their privacy practices are governed by their own policies. We encourage you to read those policies before providing information to them.
16. Changes to This Privacy Policy
We may update this policy to reflect changes to the Service, our providers, the law or our data-protection practices.
We will update the date at the top of the policy. Where a change materially affects how we use personal data or relies on consent, we will provide an appropriate notice and request renewed consent where required.
17. Contact Us
For questions, requests or complaints about privacy, contact:
ALLTHRYV LTD Company number 17076299 24 Hazel Close, Taverham, Norwich, England, NR8 6YE Email: privacy@allthryv.com
