FORMWISE
Privacy Policy
For the Formwise iOS and Android apps, Formwise services, and Aerel website
EFFECTIVE DATE | DOCUMENT VERSION | CONTROLLER / PROVIDER |
|---|---|---|
21 August 2026 | 1.0 | AEREL LTD · No. 17389393 |
Contents
1 | 7 | ||
2 | 8 | ||
3 | 9 | ||
4 | 10 | ||
5 | 11 | ||
6 | 12 |
1. Who we are and scope
AEREL LTD (company number 17389393), trading as Formwise, is the controller of personal data covered by this policy. Our registered office is 66 Paul Street, London, England, United Kingdom, EC2A 4NA. In this policy, “Formwise”, “Aerel”, “we”, “us” and “our” refer to AEREL LTD.
This policy applies when a person uses the Formwise mobile applications for iOS or Android, related Formwise online services, or the Aerel website pages that link to this policy (together, the “Services”). It also applies to support and privacy enquiries about Formwise. It does not replace the privacy terms of Apple, Google or another third party when that party independently controls data through its own service.
Privacy enquiries and rights requests may be sent to contact@aerel.co.uk or by post to the registered office above. Please write “Privacy request” in the subject line. We may ask for proportionate information to verify identity before acting on a request.
2. Information we collect
The exact information depends on the features a user chooses. Formwise may collect or generate the following categories.
Category | Examples |
|---|---|
Account and identity | Email address; display name, first and last name; account identifier; authentication records; email-verification status; and information returned by Apple or Google sign-in, such as an account identifier and verified email. Passwords are handled by our authentication provider and are not available to us in readable form. |
Profile and health/fitness data | Age, sex, height, weight, body-fat estimate, waist, neck and hip measurements, activity level, training experience, focus areas, goals, target weight or body fat, target pace, training schedule and similar wellness information. Some of this is health data and may be special category data under UK data-protection law. |
Nutrition and training records | Diet preferences, allergies, meal frequency, budget preference, calorie and macro targets, food searches, barcodes, meal descriptions and logs, hydration entries, diet plans, equipment, workouts, exercise sets/repetitions/weights, workout notes and completion history. |
Photos and derived information | Optional meal photographs, body-scan photographs and progress photographs; image references; quality checks; AI-derived meal estimates; and estimated body-fat range, confidence and explanatory notes. |
AI interactions | Coach messages, recent conversation context supplied to a response, plan-change requests, and relevant profile, goal, nutrition, meal, body-metric or workout context needed to generate a requested answer or plan. |
Preferences and notifications | Unit settings, training and nutrition preferences, chosen reminder types, notification-permission status, device platform, app version and an Expo push token where remote notifications are enabled. |
Subscription and transaction metadata | Formwise user identifier, store platform, product purchased, entitlement status, transaction status, purchase, renewal and expiry dates, and whether the transaction is a test or production transaction. We do not receive full payment-card details from Apple or Google. |
Technical, security and usage data | IP address and request metadata processed by hosting providers, app version, device/operating-system information, session and authentication data, error details, security events, AI-feature usage counters and records required to enforce feature limits or investigate abuse. |
Communications | Support emails, privacy requests, feedback and any information voluntarily provided when contacting us. |
2.1 Sources of information
- Directly from the user, including information entered during registration, onboarding, logging, support or an AI request.
- From the user’s device, when the user grants permission or uses a feature such as camera, photo library or notifications.
- Generated by Formwise, including plans, targets, estimates, reminders, usage limits and progress summaries.
- From Apple, Google and RevenueCat in connection with sign-in, distribution, purchases and subscription entitlements.
- Automatically from infrastructure and security systems when the Services are accessed.
3. How and why we use information
UK data-protection law requires a lawful basis for processing personal data and, where health data is involved, an additional condition. The principal purposes and bases are below. The applicable basis may vary with the context and the user’s location.
Purpose | Information used | UK GDPR basis |
|---|---|---|
Create and secure an account | Account, identity, authentication and security data | Contract: Article 6(1)(b). Legitimate interests in account and service security: Article 6(1)(f). |
Deliver core fitness, nutrition, progress and planning features | Profile, goals, preferences, logs and related content | Contract: Article 6(1)(b). For health data, explicit consent: Article 9(2)(a). |
Provide optional AI coach, meal, plan and body-scan features | The request, relevant context, optional images and resulting estimates | Contract: Article 6(1)(b), where needed to provide the requested feature. For health data and body imagery used for health estimates, explicit consent: Article 9(2)(a). |
Purposes and lawful bases — continued
Purpose | Information used | UK GDPR basis |
|---|---|---|
Provide notifications and reminders | Reminder choices, device platform, app version and push token | Consent: Article 6(1)(a). A user can refuse or withdraw notification permission in device settings. |
Manage subscriptions and feature access | Account ID and purchase/entitlement metadata | Contract: Article 6(1)(b); legal obligations for tax, accounting or consumer records: Article 6(1)(c). |
Maintain, troubleshoot and protect the Services | Technical, security, error and usage data | Legitimate interests in reliable and secure operation: Article 6(1)(f); legal obligation where applicable: Article 6(1)(c). |
Respond to support and legal requests | Contact details, communications, account and relevant service data | Contract: Article 6(1)(b); legitimate interests in support and dispute handling: Article 6(1)(f); legal obligation: Article 6(1)(c). |
Improve safety and functionality | Aggregated or de-identified usage information and limited error context | Legitimate interests in improving the Services: Article 6(1)(f). We do not use identifiable health data or photos for advertising. |
Where we rely on legitimate interests, we balance those interests against the user’s rights and expectations. Where we rely on consent, consent can be withdrawn at any time for future processing. Withdrawal does not make earlier lawful processing unlawful, but an affected optional feature may no longer work.
4. Health data, photos and AI
4.1 Health and fitness information
Formwise uses health and fitness information to calculate targets, personalise workouts and nutrition guidance, track progress and answer user requests. We rely on explicit consent to process special category health data for these purposes. A user is free not to provide optional information, although results may be less personalised. Formwise does not use health or fitness information for targeted advertising, marketing profiles, credit, employment, insurance or eligibility decisions.
4.2 Camera, photo library and images
Camera or photo-library access is requested only when a user chooses a feature that needs it, such as barcode scanning, meal scanning, progress photos or a body scan. The operating system controls permission. A user can deny or revoke permission in device settings and continue using features that do not require images.
- Meal photos may be transmitted for AI analysis to identify likely foods and estimate portions and nutrients.
- Front and side body photos may be transmitted for image-quality checks and an approximate body-composition estimate. These are not biometric identification templates and are not used to identify a person.
- Progress photos may remain on the device and, where cloud upload is enabled, may be stored in a private user folder. Formwise does not make user images public.
- Users must upload only their own images, must not upload images of children or other people, and should avoid including unnecessary faces, documents or background information.
4.3 AI processing and human review
For AI features, Formwise sends the minimum reasonably necessary input to an authenticated server function, which submits it to OpenAI’s API. Depending on the feature, the input may include a prompt, recent conversation context, selected profile or goal information, meal or workout data, measurements, or an image. Requests use a setting that does not create persistent response application state. OpenAI does not use API inputs or outputs to train its models by default; its standard abuse-monitoring logs may retain inputs, outputs and related metadata for up to 30 days, unless a longer period is legally required or enhanced retention controls apply.
AI output may be wrong, incomplete or unsuitable. Formwise does not use AI to make decisions that produce legal or similarly significant effects. Users can ignore, edit or replace a generated plan or estimate. Authorised personnel may review limited data where reasonably necessary to investigate a user-reported problem, a safety concern, fraud, misuse or a legal obligation, subject to confidentiality and access controls.
5. Sharing and service providers
We disclose personal data only as needed to operate the Services, follow a user’s instructions, comply with law or protect rights and safety. We do not sell personal data and do not share health data with advertisers or data brokers.
Recipient | Role and information involved |
|---|---|
Supabase | Cloud authentication, database, private file storage and server functions. It may process account details, health/fitness records, user content, image files or references, push tokens, subscription entitlements and technical logs as our processor. |
OpenAI | AI generation and image analysis. It receives only the content and context needed for the requested AI feature, which may include health data or an optional meal/body image. |
RevenueCat | Subscription orchestration and entitlement status. It receives a Formwise app user ID and store purchase/product metadata. Automatic device-identifier collection and RevenueCat diagnostics are disabled in the Formwise configuration. |
Apple and Google | App distribution, optional social sign-in, in-app purchases, refunds and subscription management. These providers independently process store account, device, payment and transaction data under their own privacy terms. |
Expo | Push-notification token creation and notification delivery when enabled. It may process a device token, platform/app metadata, message content and delivery metadata. |
Open Food Facts | Barcode and food search. It receives a barcode or search term and standard network request metadata; Formwise does not intentionally send the user’s account identifier. |
Pixabay | Optional meal-image search. It receives meal-related search words and standard network request metadata; Formwise does not intentionally send the user’s account identifier. |
Professional advisers and authorities | Lawyers, accountants, insurers, auditors, courts, regulators or law-enforcement bodies where reasonably necessary and legally permitted. |
Corporate transaction recipients | A buyer, investor or successor if Aerel is involved in a reorganisation, financing, sale or transfer, subject to confidentiality and applicable data-protection law. |
Service providers may change as the Services develop. We require processors to act on documented instructions, protect information and provide data-protection commitments appropriate to their role. Independent providers, including Apple and Google, determine their own purposes for some processing.
6. International transfers
Some providers and their infrastructure are located outside the United Kingdom, including in the European Economic Area and the United States. When personal data is transferred from the UK to a country without applicable UK adequacy regulations, we use safeguards required by law, such as the UK International Data Transfer Agreement, the UK Addendum to the EU Standard Contractual Clauses, or another lawful mechanism. We also assess supplementary technical and organisational measures where appropriate. A user may contact us for further information about the relevant safeguards.
7. Retention and deletion
We keep personal data only for as long as reasonably necessary for the purposes described in this policy, including providing an active account, meeting legal duties, maintaining security and resolving disputes. The following schedule states our standard periods or criteria; a shorter or longer period may apply where law, an active dispute or a valid preservation request requires it.
Information | Standard retention approach |
|---|---|
Account, profile, goals, preferences, logs and plans | For the life of the account. After a verified in-app deletion, live account records are deleted or de-identified without undue delay and normally within 30 days. |
Stored user photos | For the life of the account or until the user removes them, whichever is earlier. Private cloud files are included in the account-deletion process. |
AI request content held by OpenAI | Formwise does not request persistent response storage. OpenAI’s standard abuse-monitoring retention may be up to 30 days, subject to legal exceptions or any enhanced controls in force. |
Push tokens and reminder settings | Until notifications are disabled, the token is replaced, the user signs out/unregisters the device, or the account is deleted. Local reminder settings remain on the device until cleared or the app data is removed. |
Subscription, transaction and accounting records | For the account period and then up to six years where reasonably needed for tax, accounting, fraud prevention or legal claims. Payment-card details remain with the platform provider. |
Security, service and AI-usage records | Normally up to 24 months, unless needed longer to investigate abuse, protect the Services or establish, exercise or defend legal claims. |
Support and rights-request correspondence | Normally up to 24 months after closure, or up to six years where the correspondence concerns a contract, complaint or legal claim. |
Backups | Deleted information may persist in restricted, rotating backups for up to 90 days before being overwritten, unless law requires longer preservation. Backups are not restored for ordinary business use except disaster recovery. |
8. Security
We use technical and organisational measures designed to protect personal data, including authenticated access, encrypted network connections, role-based database controls, private storage buckets, separation of server secrets from the app, restricted administrative access, provider due diligence and account-deletion tooling. No internet or storage system is completely secure, so absolute security cannot be guaranteed. Users should use a strong, unique password, protect access to their device and notify us promptly of suspected unauthorised access.
If a personal-data breach is likely to create a risk to individuals, we will assess, contain and notify the UK Information Commissioner’s Office and affected users where applicable law requires it.
9. Your choices and rights
Depending on the circumstances and applicable law, a user may have the right to:
- request access to personal data and information about its processing;
- request correction of inaccurate or incomplete data;
- request deletion of personal data;
- request restriction of processing;
- object to processing based on legitimate interests;
- receive certain data in a structured, commonly used and machine-readable format and transmit it to another controller;
- withdraw consent at any time for future processing; and
- complain to a data-protection regulator and, where applicable, seek a judicial remedy.
9.1 In-app and device controls
- Account deletion: Settings → Delete account. This deletes the authenticated Formwise account, associated database records and user files covered by the deletion process.
- Web deletion route: if the app cannot be accessed, email contact@aerel.co.uk from the account email with the subject “Delete my Formwise account”. We will verify the request before deleting the account and associated data.
- Notifications: change reminder selections in Formwise and notification permission in iOS or Android settings.
- Camera and photo library: revoke access in device settings; the related scan/photo features will then be unavailable.
- Subscription: manage or cancel through Apple App Store or Google Play subscription settings. Deleting Formwise does not cancel the subscription.
9.2 Contacting us and the ICO
To exercise a right, email contact@aerel.co.uk. We normally respond within one month, subject to lawful extensions. We do not charge a fee unless a request is manifestly unfounded or excessive and law permits a reasonable fee. If dissatisfied, a user may complain to the UK Information Commissioner’s Office.
ICO: ico.org.uk/make-a-complaint · Telephone 0303 123 1113 · Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF, United Kingdom.
10. Children and age restriction
Formwise is intended only for adults aged 18 or over. We do not knowingly collect personal data from anyone under 18 and users must not create an account or submit information for a child. If we learn that a person under 18 has provided personal data, we will take reasonable steps to disable the account and delete the information. A parent or guardian who believes a child has used Formwise should contact us promptly.
11. Website cookies and technical data
The Aerel website may process essential technical data such as IP address, browser type, requested page, referring page, timestamps and security logs to deliver and protect the site. Strictly necessary cookies may be used for security, session continuity or saved privacy choices. Non-essential analytics, advertising or similar cookies will not be placed where consent is required unless the visitor first chooses to allow them, and the website’s cookie control will identify the current cookies and providers. A visitor can also control cookies through browser settings, although blocking essential cookies may affect functionality.
12. Changes and contact
We may update this policy when the Services, providers or law change. The current version will be published at the public privacy-policy URL and in or through the apps, with a revised effective date. We will provide additional notice where a change materially affects users’ rights or requires renewed consent. Earlier versions may be requested from us.
Controller contact
Controller | AEREL LTD, trading as Formwise |
Company number | 17389393 |
Registered office | 66 Paul Street, London, England, United Kingdom, EC2A 4NA |
contact@aerel.co.uk |

