Privacy policy
Updated 7 November 2026. This policy covers the April mobile app, watch experience, trainwithapril.com and related support services worldwide. Some features depend on your app version, subscription, device and release availability.
Who is responsible for your information
April is operated from the United Kingdom under the project name April Technologies. The operator of April is the controller of personal information handled through April, except where another provider acts as an independent controller for its own service.
Business and correspondence address: 27 Old Gloucester St, Holborn, London WC1N 3AX, United Kingdom.
Privacy questions and rights requests can be sent to privacy@trainwithapril.com.
1.1 When this policy applies
This policy applies worldwide when you create an April account, use training, nutrition, progress, watch or AI features, contact support, or visit the website. Country-specific sections explain additional rights in selected jurisdictions but do not limit where April is available. It does not replace the privacy terms of Apple, Google, a connected health platform, an AI provider, the April Food Database infrastructure, or another service you choose to use.
“Personal information” includes information that identifies you, relates to you, can reasonably be linked to you, or is treated as personal data under applicable law. Health, biometric, body, wellbeing and some profile information may receive additional protection as sensitive or special category information.
1.2 Information April collects and processes
The information April processes depends on the features you use, what you enter and the permissions you grant.
| Category | Examples | Main use |
| Account and identity | Email address, authentication identifier, name or nickname, date of birth, age band, sign-in provider | Create, secure and recover your account; confirm eligibility |
| Profile and goals | Height, weight, target weight, goals, experience, schedule, equipment, training location, preferences | Personalise and update your plan |
| Health and safety context | Injury or care areas, pregnancy status, eating-disorder or clinician-led nutrition flags, relevant medication and safety answers | Apply safety checks and avoid unsuitable suggestions |
| Training and progress | Plans, workouts, exercises, sets, loads, repetitions, rest, adherence, body trends and check-ins | Run your plan, record activity and show progress |
| Optional location and outdoor activities | Approximate or precise device location; route searches, starts and stops; recorded GPS points, timestamps, accuracy, altitude, speed, distance and saved routes | Show your position, find nearby places, plan routes, record runs, rides, walks and hikes, and show your history |
| Nutrition | Food searches, barcode numbers, meals, portions, calories, macros, ingredients, allergies, saved foods and Cabinet items | Log food, estimate nutrition and check compatibility |
| Connected health | Steps, active and total energy, distance, heart rate, resting heart rate, sleep, weight, exercise and workout data | Show trends and provide optional recent context |
| AI content | Prompts, responses, selected model, limited April context, saved chats, memories, feedback and web-search requests | Answer requests, maintain chats you save and enforce safety |
| Files, images and voice | Photos, files, barcode camera frames, attachment descriptions and speech transcripts | Analyse an attachment, scan food, or turn speech into text |
| Purchases | Product, store, entitlement, renewal state and pseudonymous transaction or subscriber identifiers | Recognise, restore and protect paid access |
| Friend referrals | Invite codes and attribution, onboarding and meal-log qualification, reward activation and expiry, account and installation signals, device-integrity evidence, and keyed digests of relevant sign-in and device identifiers | Count genuine referrals, deliver the inviter’s reward, prevent duplicate or self-referral claims and investigate abuse |
| History exports | Selected date range and time zone, export status, dated food and actual workout records, and private download metadata | Prepare and deliver the history file you request |
| Technical and support | App version, platform, device capability, integrity signals, timestamps, IP address in network logs, map usage, battery and connectivity information, map performance diagnostics, pseudonymous map billing or session identifiers, error details, support messages and screenshots you send | Operate, secure, troubleshoot and support April; measure map usage and improve map services |
| Website request data | Requested page, time, browser and IP address in ordinary hosting or security logs | Deliver and protect the website |
Friend referrals and abuse prevention
If you use an invitation or participate in the reward programme, April links the invitation to the invited account and checks completion of onboarding and a qualifying food log. The inviter sees progress and reward status, not the friend’s meal contents, workout details, email address or health records.
The programme permits one device per person and one lifetime reward. April uses account, installation and device-integrity signals, together with protected identifier digests and server-side audit records, to detect self-referrals, reused identities, shared-device claims and duplicate rewards. These digests are pseudonymous personal information, not anonymous data. Some claim and anti-abuse records remain after account deletion so deleting and recreating an account does not reset eligibility. April does not currently require SMS phone verification for referral rewards.
History files you request
Supported app versions let you request a readable food and workout history file for the last 7 days, last month, last year or full history. April prepares it privately on its servers and provides an authenticated, time-limited download. The file records saved food and actual workout activity, including partial sessions where recorded; it is not a record of every planned workout or a copy of your raw connected-health history. A file saved on your device or shared elsewhere is then under your control.
Maps, outdoor recording and nearby AI
Location access is optional. You can use April's other features without granting it, and can change it in your device settings. Map browsing can use approximate location; recording an outdoor activity requires precise location. You can also search for a named place or choose a route start on the map.
Map requests can send the viewed area, route coordinates, selected stops, search text and your location when relevant directly to Mapbox. This includes route thumbnails shown in chat. These requests are not confined to your phone. Mapbox also receives ordinary request metadata, including IP addresses and pseudonymous identifiers.
Outdoor recording starts when you choose to start an activity. On Android, a location foreground service supports recording while you use another screen or lock your phone, with an ongoing system notification or active-app indicator depending on your notification settings. Pause stops adding recorded GPS points; finish ends the recording. The unfinished or unsaved recording stays in app-private storage on your device so it can recover after an interruption. Saving uploads the recorded GPS trail and activity statistics to April's Firebase infrastructure; saving a planned route uploads its geometry and directions. Discarding removes the local recording. Deleting a saved activity or route removes its stored geometry; deleting your account removes these records too, subject to the retention exceptions below.
If you explicitly ask AI about your current surroundings or choose “Use current area”, April sends a fresh device fix to its authenticated server for that reply. The server reduces its precision to an area of about a kilometre before querying the nearby-search provider. This is still location information, not anonymous data. The answer model receives selected place information and sources rather than the device coordinates. The device fix is not saved in chat history, profile fields or AI memories. Ordinary questions and opening saved chats do not request GPS. When AI uses your logged outdoor activities, it receives limited activity summaries such as sport, time, duration and distance, not the recorded GPS trail.
1.3 Where information comes from
- Directly from you: account details, onboarding answers, logs, chats, uploads, choices and support messages.
- From your device: app and device information, permissions, camera or microphone input, local health platform data and watch signals.
- From services you choose: Apple, Google, sign-in providers, connected health platforms, app stores and subscription services.
- From April Food Database: food, product, barcode, ingredient and nutrition records used to provide food results.
- From April's operation: derived plan settings, safety flags, trend summaries, entitlement state, security events and service diagnostics.
1.4 Why April uses your information
| Purpose | UK + EU legal basis | Additional condition |
| Create accounts, deliver requested features, sync records and manage subscriptions | Performance of a contract | Explicit consent where the feature needs special category health data |
| Read connected health and use optional health or safety context | Consent | Explicit consent for special category data; permission can be withdrawn |
| Personalise training, nutrition, progress and AI context | Contract and, where appropriate, legitimate interests | Explicit consent where health data is involved |
| Secure accounts, prevent fraud, enforce limits and investigate abuse | Legitimate interests and legal obligation | Use or defence of legal claims where applicable |
| Provide support, debug failures and measure service reliability | Contract and legitimate interests | Health details are not required for ordinary support |
| Keep accounting, dispute and compliance records | Legal obligation and legitimate interests | Only the limited record needed for that purpose |
| Send optional marketing in the future | Consent where required | April does not currently send third-party advertising |
For people in the European Economic Area, these legal bases are interpreted under the EU GDPR. For people in the United Kingdom, they are interpreted under the UK GDPR and Data Protection Act 2018. Elsewhere, April relies on consent, contract, legitimate interests, legal obligation or another authority permitted by applicable local law. You are not required to grant optional device permissions or supply optional health context, but the related feature may be less tailored or unavailable without it.
1.5 Connected health data
01Health platformApple Health or Health Connect holds the source record.
→
02April on deviceApril reads only the data types you authorise.
→
03Requested featureTrends appear in Progress. A limited summary of recent data may be included in an AI request when relevant.
The connected-health view in April's phone app requests read-only access to Apple Health or Health Connect. The Apple Watch companion separately asks for permission to save workouts to Apple Health. When you use a workout session on Apple Watch, HealthKit may collect and save associated sensor measurements, such as heart rate and active energy. When you complete the workout on your watch or paired phone, or end it early on your watch, April can save the workout's timing, duration and available HealthKit session data to Apple Health, subject to your permissions. Raw connected-health samples are not copied into a server-side April health-history database. If you ask AI to use health context, a limited summary needed for that request can be processed by April's server and the selected providers. You can revoke access in your operating-system settings.
1.6 How AI requests are processed
- 01
You send a request.April receives the prompt, your selected model, any attachment, and only the enabled April context relevant to the request.
- 02
Safety checks run.April uses rule-based safety checks on messages and answers. The selected AI provider may also apply its own safety checks.
- 03
Attachments are described.A raw image or file is first analysed using OpenAI. The resulting limited description, not the raw attachment, is then sent to the selected answer model. Supported saved chats keep original images privately for later viewing; other raw file payloads are not retained by April after processing.
- 04
The selected model responds.The prompt and limited context are sent only to the AI service needed to return the response. When a web-enabled feature is used, supporting tools receive only the query or page needed for that request.
- 05
Chats are saved according to your choice.Saved chats and memories remain until you delete them. Temporary Chat is kept out of your history and does not use saved memory or past chats. An encrypted copy of the result may be kept for no more than 24 hours to recover interrupted delivery.
On supported app versions, images sent in saved chats stay private to your April account so you can reopen them on your devices. Viewing requires authentication; April does not create public image links. Deleting the last saved chat or branch that uses an image removes its stored original; the image can remain while another saved chat or branch still references it. Deleting your account also removes these originals. Temporary Chat does not keep image originals on April's servers; temporary copies on your device are cleared on session or account changes and expire automatically. Images already discarded by older app versions cannot be recovered.
How April uses automated decisions
April uses rules and AI to tailor workouts, food tools, trends and responses. These processes do not make decisions that produce legal or similarly significant effects. They can still be wrong, so you should review suggestions and use professional advice where the consequences matter.
1.7 Service providers
April shares information only for a described purpose, at your direction, to complete a transaction, to protect the service or people, or where law requires it. Current provider categories include:
Google Firebase and Google Cloud
CORE
Authentication, user data, storage, server functions, security and app-integrity checks.
Mapbox
MAPS + ROUTES
Map display, place search, directions and route thumbnails use relevant map areas, coordinates and searches. The mobile Maps SDK sends location and usage telemetry by default to support and improve Mapbox's services. You can opt out through the attribution or information control on the full map; requests needed for the maps, searches or routes you use still occur. Mapbox may process data as April's processor or as an independent controller under its Product Privacy Policy, depending on the processing.
Supabase and the April Food Database
FOOD INFRASTRUCTURE
Private database infrastructure used to search food, product, barcode, ingredient and nutrition records.
Apple and Google
PLATFORM
Sign-in, distribution, device permissions, health-platform access and store purchases, depending on your device.
Subscription services
BILLING
Subscription entitlement, purchase transport and restoration using store and pseudonymous subscriber identifiers.
OpenAI
AI + ATTACHMENTS
Attachment analysis, selected answer models and specialist nutrition or progress features where used.
Model providers and routing services
SELECTED AI
OpenAI and DeepSeek process your message and limited app information when you use the relevant model or feature. Routing services such as OpenRouter may deliver these requests to the selected provider. Qwen and Z.ai’s GLM appeared in earlier versions and are no longer selectable. OpenAI also processes supported attachments and safety checks as explained above.
Search and content tools
WEB
April can choose to search when an answer needs current public information, or you can request a search. The public-topic query and selected source URLs are sent to our search and page-retrieval providers; your full conversation is not sent to those services. An explicitly requested current-area lookup also sends the reduced-precision area described above to the nearby-search provider.
Cloudflare and Zoho Mail
WEBSITE + SUPPORT
Website delivery, security, aggregate website analytics and support communications.
EU Rep, advisers, authorities and successors
LEGAL + OTHER
Privacy representation, professional advice, lawful requests, safety, legal claims, or a properly managed business transfer.
A provider may act as April's processor, service provider, or independent controller depending on the service. April does not authorise providers to use health information for advertising. If April adds a provider that materially changes the data path, this policy and any required consent will be updated first.
1.8 Where information is processed
April is operated from the United Kingdom under the project name April Technologies and uses providers that may process information in the United Kingdom, United States, European Economic Area and other countries where they or their approved subprocessors operate. Privacy protections can differ between countries.
Where UK law requires a transfer safeguard, April will use an applicable adequacy regulation, the UK International Data Transfer Agreement, or the UK Addendum to approved standard contractual clauses, together with a transfer-risk assessment and technical or organisational protections. For transfers governed by EU law, including transfers involving people in Ireland, April will use an EU adequacy decision, approved Standard Contractual Clauses or another valid EU GDPR transfer mechanism, with supplementary protections where required. Where other regional transfer rules apply, April will use the locally required consent, contract, assessment or comparable protection.
1.9 How long information is kept
| Record | Current retention rule |
| Account, plan, workout and nutrition records | While the account is active, then deleted or de-identified after account deletion unless a narrow legal, security or dispute record must remain. |
| Saved outdoor activities and routes | GPS trails, route geometry, directions and statistics remain until you delete the record or your account. Deletion removes the geometry; a random deleted-record identifier can remain to prevent a delayed upload restoring it. An unsaved local recording remains until you save or discard it. |
| Current-area device fix for an AI reply | Used for the current request and not saved in April's chat history, profile or memories. Saved replies can retain the public place information and sources returned for that request. |
| Mapbox data | Mapbox applies its own retention and de-identification rules. Its Product Privacy Policy describes IP-address deletion normally within 30 days and breaking the location-to-session association within 24 hours; these are not a promise that every map record is deleted within 24 hours. See the linked policy for exceptions and rights. |
| Saved AI chats and memories | Until you delete the item or your account. |
| Temporary Chat recovery result | No more than 24 hours. It is unlisted and not used as later model context. |
| Supported saved-chat original images | Stored privately until the last saved chat or branch that references the image is deleted, or you delete your account. Temporary Chat does not retain image originals on April's servers. |
| Other raw AI attachments | Not retained by April after processing. Saved history keeps attachment metadata, not these original payloads; attach the file again to use its contents. |
| Raw connected-health history | Read for the requested task and not stored in an April server-side health-history database. |
| Prepared history downloads | Ready exports expire after 24 hours. Background cleanup removes expired files and temporary working data; a two-day storage lifecycle rule provides an additional cleanup safeguard. Account deletion also removes associated server-side export data. Copies you saved or shared outside April are not removed by account deletion. |
| Referral claim and anti-abuse records | Limited account, identity, installation and device claim digests can remain for the lifetime of the referral programme to enforce its once-only eligibility. Fraud and security audit evidence is retained only for the relevant prevention, investigation or dispute purpose. Deletion removes the active reward and user-scoped referral data, but does not reset a prior claim. |
| AI request, retry, window and webhook metadata | Up to 35 days. Raw account identifiers in the billing path are erased on account deletion. |
| Scheduled AI report outcomes | A limited completed, held or failed outcome record can remain with the account until removed or the account is deleted. It links the outcome to usage accounting without storing prompts, attachments or health-report content. |
| Pseudonymous billing and AI usage evidence | Up to 400 days after the relevant period. It excludes prompts, outputs, attachments, health data and raw account identifiers. |
| Deleted-user billing barrier | A domain-separated account digest and deletion time for up to 400 days to prevent erased billing data being recreated by a provider sync. |
| Support, legal and security records | For the time reasonably necessary to resolve the issue, meet a legal duty, enforce rights or defend a claim. |
| Encrypted backups | Until overwritten on the normal restricted backup cycle, unless a lawful preservation duty applies. |
These are April’s retention rules. An expiry marker stops access or reuse where specified; physical cleanup can complete afterwards. April may remove information sooner and can retain a narrowly scoped record longer where law, a court order, fraud prevention, safety, accounting or a live dispute requires it.
1.10 How April protects information
April uses encryption during transfer and provider encryption for stored data. Access rules limit data to the right account, servers check permissions, and app-integrity checks help detect tampering. Service credentials and retention periods are limited. Logs are designed to exclude prompts, answers and health information where they are unnecessary. Only people and systems with an authorised need can access the data.
No online service is risk-free. Keep your phone, watch, email account and sign-in methods secure. If April confirms a breach that requires notification, April will notify affected people and regulators within the deadlines that apply, including the US Federal Trade Commission Health Breach Notification Rule where applicable.
1.11 Website analytics and cookies
trainwithapril.com does not set advertising cookies or build advertising profiles. It uses Cloudflare Web Analytics for aggregated page-view, referral, device and performance information. Cloudflare states that this service does not collect or use visitors' personal data and does not track individual visitors across customers' websites. Hosting and security systems can still create ordinary request and security logs. If non-essential cookies or similar technologies are added, April will update this notice and provide consent controls before using them where the law requires.
1.12 Age requirements
April is not directed to, and does not permit accounts from, children under 13. The onboarding flow blocks a date of birth showing an age below 13. If April learns that an ineligible child supplied personal information, April will close the account and delete the information, subject to the narrow retention exceptions above.
If you are 13 to 17, a parent or guardian should review April, these documents, any subscription and material training or nutrition changes with you. April may require adult permission where local law or the nature of the information requires it. April does not sell young people's personal information or use it for targeted advertising.
In Ireland, where April relies on consent to process a child's personal information for an online service, a user under 16 may need consent or authorisation from a parent or guardian. Other lawful bases and child-safety rules may apply depending on the feature and context.
1.13 Your privacy rights
Depending on where you live and which law applies, you can ask April to confirm processing, provide access or a portable copy, correct information, delete it, restrict processing, withdraw consent, object to some uses, limit sensitive-data use, or explain a significant automated decision. April does not discriminate against you for using a privacy right.
Send a request to privacy@trainwithapril.com. State your country or US state and the right you want to use. April may request limited information to verify your identity and authority. If April denies a request, the response will explain why and how to appeal where an appeal right applies.
IRELAND + EEARights can include access, rectification, erasure, restriction, portability, objection and withdrawal of consent. People in Ireland may complain to the Data Protection Commission. People elsewhere in the EEA can contact their local supervisory authority.
UNITED KINGDOMRights can include access, rectification, erasure, restriction, portability, objection and withdrawal of consent. UK complaints can be made to the Information Commissioner's Office.
UNITED STATESApplicable state law can provide rights to know, access, correct, delete, obtain a copy, opt out of sale or targeted advertising, limit some sensitive-data uses and appeal. April does not sell personal information or use it for targeted advertising.
CANADAYou can request access and correction, withdraw consent subject to lawful limits, and challenge compliance. You can complain to the Office of the Privacy Commissioner of Canada or the relevant provincial commissioner.
AUSTRALIAYou can request access or correction and complain to April. If the issue is not resolved, you may complain to the Office of the Australian Information Commissioner. Statutory consumer guarantees remain unaffected.
NEW ZEALANDYou can request access or correction and raise a privacy complaint. You may contact the Office of the Privacy Commissioner if the issue is not resolved.
How to make a privacy complaint
Email privacy@trainwithapril.com with the subject “Privacy complaint.” April will acknowledge it, review the facts and relevant systems, involve a provider where needed, and send a reasoned response within the period required by applicable law. The response will identify any correction or other action and the regulator or appeal route available if you remain dissatisfied.
European Representative under Article 27 of GDPR
We have appointed EU Rep as our Representative under Article 27 of the EU General Data Protection Regulation (“GDPR”). All GDPR queries from EU Data Subjects or Data Protection authorities should be submitted to eurep.ie via their dedicated form. BizLegal Ltd trading as EU Rep have their registered office at 27 Cork Road, Midleton Co. Cork, Ireland. Company number 635921.
1.14 Changes to this policy
April may update this policy when the product, providers or law changes. The updated date will appear at the top. If a change materially affects your choices or requires consent, April will provide additional notice in the app or ask for consent before the new processing starts.