Privacy Policy
Version 45. Last Updated: 12 November 2026.
Flair Health is a product of Regal Pines Pte. Ltd., a company incorporated in Singapore. References to "Flair," "we," "us," or "our" refer to Regal Pines Pte. Ltd.
Flair is a local-first wellness app, privacy-first until we can verifiably be more. This policy explains what data leaves your device, when, and why.
1. No Cloud, No Accounts, No Tracking
Flair is offline-first: it keeps your data on your device and works without a connection, except for the features that need one: the AI features, Local Conditions and route maps.
- We never require an account, email, or phone number to use Flair.
- Your journal entries, habits, scores, and AI insights live only on your device.
- We do not have a backend database for your personal data.
- We do not sell your information, rent it, or use it for advertising.
- One exception is when you explicitly invoke an AI feature (Refresh Insights, Magic Lens, Eat Now, Document Scanner, Daily Quests, Do Now, or Ask Flair). Each feature requires your explicit approval via an in-app consent prompt before any data is transmitted. See Section 5. Flair makes no network request on app launch, with two exceptions you control. If you have turned on Local Conditions, opening Today refreshes the weather and air quality for your area through Flair's server, as that agreement says. If you took a Magic Lens photo while offline, Flair sends it, as you approved, when the app next has a connection. Otherwise the first server contact occurs when you use an AI feature you have approved.
- A pseudonymous identifier, generated on your device and rotating daily, is included with AI requests. It is not derived from any device or account identifier, and it is never forwarded to an AI provider. Section 5 describes what it is used for and what is retained alongside it.
Smart Habits: Flair learns your recurring wellness patterns (such as meals, supplements, or workouts) by analysing the timing and content of your journal entries. This analysis is performed entirely on your device. No habit data, patterns or predictions are transmitted to any server, except that Ask Flair sends today's habits if you tap Share, as section 5 describes. You can confirm or dismiss any predicted entry, and patterns that are consistently dismissed are automatically deactivated.
Voice Input: Flair offers optional speech-to-text input for journal entries. Speech recognition is performed entirely on your device by the operating system (Apple Speech Recognition). Flair requires on-device recognition and does not permit a fallback that would send your audio elsewhere for processing. Where your device or selected language cannot support on-device recognition, voice input does not work. Voice input does not record, store or transmit your audio.
Sleep timer: The sleep timer measures no movement. If Listen for snoring is on, Flair asks before it first listens, then uses your phone's microphone during the sleep timer to listen for snoring. The sound is analysed on your phone. Flair keeps only the times and counts of snoring it heard, in your journal, and no audio is stored or sent. Snoring figures stay on your phone and are not sent to any AI feature.
Siri Shortcuts: Flair supports Siri Shortcuts for hands-free journal entry logging. Siri interactions are processed by your device's operating system (Apple Siri). Flair does not access Siri audio or transcripts beyond the text content you choose to log as a journal entry.
2. Your Control Over Your Data
No data leaves your device without your explicit, per-feature consent.
- Each AI feature requires individual consent before activation. You decide which features may transmit data, and which may not.
- Before any AI feature you initiate sends data, Flair displays a consent form showing every specific data field that will be shared. This field-level transparency lets you see exactly what is being transmitted and why. In supported features (currently Eat Now), you can additionally view the exact minimised payload before it is sent, rendered from the same code that builds the real request. Standing context you've enabled, such as weather and environmental data (see Section 9), runs on a simpler permission toggle rather than a per-send preview.
- If data requirements for a feature change in a future update, Flair shows you exactly what changed (a diff of the previous and updated data fields) and requires you to re-approve before any data is sent under the new terms.
- You can revoke consent for any feature at any time in Settings → Privacy & Security → Data Sharing Agreements. Revoking consent immediately stops that feature from transmitting data.
- An "Always show this prompt" option is available if you prefer to review and approve data sharing every time you use a feature, rather than granting standing consent.
3. Local Encryption & Ownership ("The Sovereign")
If you enable "The Sovereign" in Settings → Data Ownership:
- We generate a 12-word backup phrase that only you control.
- This phrase derives the encryption key that protects your entire journal on disk.
- Your data is stored within the Health Passport, an encrypted container on your device (previously referred to as "The Vault" in earlier versions of Flair).
- We never see, store, or back up your phrase or key.
- If you lose your phrase or device, your encrypted data cannot be recovered, even by us.
4. Biometric Lock
If you enable biometric locking (Face ID / Touch ID / device passcode) in Settings → Privacy & Security:
- Authentication is handled entirely by your device's operating system.
- Flair never accesses or stores your biometric data.
5. Artificial Intelligence & Third-Party API Processing
Flair includes several AI-powered features. Each feature requires your explicit in-app consent before any data leaves your device.
- Refresh Insights sends a structured summary of your day's journal entries, your health profile in broad bands (age range, sex, BMI category), your stated health objective, active wellness protocol targets, medical conditions (such as diabetes, hypertension, thyroid, kidney, or liver conditions), Fitzpatrick skin type, behavioural patterns (7-day activity breakdown), and, if available from scanned documents, lab biomarker values to our serverless routing layer over HTTPS. No names, exact biometrics, or account identifiers are transmitted.
- Magic Lens sends a compressed copy of your photo for analysis. What is analysed depends on the mode you select: meal photos are analysed for nutritional content; life moments (books, rooms, objects, scenes) are analysed to write a short journal entry; and photos of medical-device readings (glucose meters, blood-pressure monitors, scales) are analysed to extract the numeric values. No metadata, location, or identifying information from the photo is transmitted.
- Eat Now sends the restaurant or venue you name, its area and country and, if you gave one, an approximate position; what you feel like eating and drinking; your stated health objective, your food allergies, your dietary preferences, whether you are fasting, your medical conditions (kidney, liver, diabetes and its type, thyroid, whether your blood pressure readings are above the general 130/80 guideline, asthma and high cholesterol) and your age group; a summary of today's food entries; your 7-day nutrient averages; and any active food quests, to generate meal suggestions. No name, sex, weight, exact biometrics or account identifier is sent.
- Document Scanner processes your health report photo entirely on your device using optical character recognition (OCR). The text recognition is Google's ML Kit, which runs on your phone (see section 10). Personal identifiers (names, dates of birth, ID numbers, phone numbers, email addresses and national IDs) are detected and removed on your phone by pattern matching. Before sending, Flair shows you the items it found and removed, and asks for your approval. Only the redacted text is then sent to our routing layer, with the request details described below, for biomarker extraction. That text is about your health, and nothing in it names you, but a medical report can still be recognisable from what it says, which is why you see what was removed before anything is sent. The original photo is never stored by Flair and never transmitted to any server.
- Daily Quests sends your stated health objective, your injuries, your food allergies, your medical conditions and whether you are fasting, with the version of the quest rules, to generate your quests. No age, sex, name or account identifier is sent.
- Do Now sends your stated health objective, your age group, your current energy level, medical conditions (including whether your blood pressure readings are above a general guideline threshold of 130/80, whether you have declared asthma, and whether you have declared high cholesterol), injuries, today's journal entries, recent journal context, and any active health concerns to help you choose between options you are weighing. No names, exact biometrics, or account identifiers are transmitted.
- Ask Flair is a chat with Flair, answered by Anthropic's Claude through Flair's server. With every message it sends what you write and Flair's replies, the last 8 turns of that chat, never your other chats; your age group (never your age), your units, and the date and hour; and the allergies and way of eating you declared, as you typed them, whether you are fasting today, and your goal. Flair may ask for more in the chat. Each of these is sent only after you tap Share, for that one answer: what you have eaten today; last night's sleep; today's activity; what you have drunk today; your workouts this week; today's habits, done or not, with times; Flair's energy estimate for today; the air quality, UV and heat readings near you, if Local Conditions is on; your health conditions; and your sex, height and weight. If you say no, the request says what you said no to, and nothing more. Flair's server reads which country your network address is in, to offer Ask Flair where it is available, and keeps no record of it. Flair keeps no copy of your chat; it stays on your phone until you delete it. Anthropic deletes requests and answers within 30 days; flagged content may be kept for up to two years (Anthropic's Privacy Center, updated 1 July 2026).
- Blood Pressure Threshold Flag: Where you have entered blood pressure readings, Do Now and Eat Now also receive a flag for whether those readings sit above the general guideline threshold (130/80). This is a comparison against a published threshold, not a diagnosis, and it is not a substitute for assessment by a healthcare professional.
- These requests carry no name, email address or account identifier, and the daily code that reaches Flair's server is never forwarded to any AI provider. The data is about you, but nothing in it names you.
- If you used Body Age, Weekly Wrapped, Inspire Me or Health Wallet in an earlier build, what they produced, and the agreements you approved for them, stay on your phone and in any backup you made, until you delete them. Nothing more is sent for them, and Health Wallet never sent anything.
- AI Providers: AI inference is performed by Google Gemini on Google Cloud Vertex AI, except for Ask Flair, which uses Anthropic's Claude API. Other models (OpenAI's GPT-4.1-mini and GPT-4.1, and Anthropic's Claude) are available only for Flair's own team. All providers process data for inference only, under their respective API terms of service. We do not share personally identifiable information with any provider. Flair uses Google Cloud Vertex AI's Singapore region for inference processing. Google keeps a short-lived copy of each request to speed up answers, deleted within one day; for Eat Now, which uses Google Search grounding, Google also keeps the search queries and the pages it drew on for up to three days, and there is no way to switch that off. Either may be kept longer if flagged for misuse. Google does not use your data to train its models.
- No Content Persistence: Our routing layer processes the content of your request in memory and does not log, store, or retain it after the request is complete. Journal entries, health data, photos, and any other content you send are never written to storage on our servers. We do keep an operational record of each request, described under Pseudonymous Telemetry below. AI providers process your data under their own API terms. For reference: Google Cloud Vertex AI, OpenAI GPT-4.1-mini and GPT-4.1, Anthropic Claude.
- IP Address: AI providers never see your IP address; requests are routed through our server. Our server sees your IP address in transit, as every server does. The only application-layer use is a one-way cryptographic hash of it, held for about two minutes, solely to prevent abuse (rate limiting): never the raw IP, never linked to your identity beyond that window, never used to profile you, and never stored in any database. Our hosting provider's own infrastructure logs are bounded by their published retention policy, which we do not control and cannot shorten.
- No Training: Your data is not used by our routing layer or by any AI provider to train models.
- Pseudonymous Telemetry: Your device generates a pseudonymous identifier by hashing a random per-install value with the current date, and includes it in requests to Flair's routing layer. Document Scanner's requests also carry your time zone offset. It is never forwarded to any AI provider. The providers that process your request receive no identifier of any kind. We use it to enforce rate limits, and we retain it alongside an operational record of each request covering which feature was called, when, how long it took, how many tokens were used, and which model answered. These records contain no journal content, no health values, and no IP address. They do show which features a given day's identifier used, so they are a record of activity rather than an anonymous count. Because the identifier changes every day, that activity cannot be linked from one day to the next. The random value it derives from never leaves your device. Each of these records is deleted from our own store after 30 days. Daily totals with no identifier of any kind are kept longer, as counts: the number of requests per feature for 12 months, and each day's overall totals with no set limit. Separately, our hosting provider retains short-lived runtime logs of each request. These carry the same operational fields, without the pseudonymous identifier, and no content. They are held for the period our hosting provider applies to the plan we are on, currently one day. From Body Age in earlier builds, our server keeps a weekly count of results and their average change, with nothing that identifies anyone. Weeks with fewer than five results are deleted after 30 days; the rest stay as counts. It carries no identifier and is not linked to the record described above.
- Sensitive Medical Context: If you optionally provide medical conditions (such as diabetes, hypertension, kidney or liver conditions, or injuries) or fasting states, this information is transmitted to the AI provider for inference and is not stored by Flair. It is used solely to ensure that generated recommendations do not suggest activities that could be harmful to you. This data is never stored on our servers, never retained after your request is processed, and is treated as sensitive health data under applicable law.
- In-App Consent: Before any AI feature transmits data for the first time, Flair displays a consent prompt disclosing the service, purpose, active AI provider, and every specific data field involved (field-level transparency). If the data fields required by a feature change in a future update, Flair displays a diff showing exactly what changed and requires you to re-approve before proceeding. You may approve or reject each feature independently. Your preference is stored locally and can be revoked at any time in Settings → Privacy & Security → Data Sharing Agreements.
6. Apple Health & Google Health Connect
To power automated tracking, Flair requests read-only access to the following data categories:
Vitals:
- Heart Rate
- Resting Heart Rate
- Heart Rate Variability (HRV / SDNN)
- Blood Oxygen Saturation (SpO₂)
- Respiratory Rate
- VO₂ Max
Activity:
- Daily Step Count
- Workouts
- Workout GPS Routes
Sleep:
- Sleep Sessions (including sleep stage breakdowns)
Environment:
- Time in Daylight (iOS 17+)
- Environmental Audio Exposure
Wellness:
- Mindful Minutes
This data is pulled directly into your local journal and stored on your device. We do not transmit raw health data to any server. Flair writes your weight, height and mindful minutes to Apple Health, if you allow it in Apple Health's settings, and nothing else. It writes nothing to Google Health Connect. Workout route data (GPS), if synced, is stored only on your device and is never transmitted to our servers.
With your permission, Flair imports the data categories listed above from Apple Health. This data is stored locally on your device and is never transmitted to any server unless you explicitly invoke an AI feature that includes it (such as Refresh Insights, as section 5 lists). Flair also reads which apps or wearable devices have written data to Apple Health (for example, Garmin Connect or Oura) to detect your connected devices. This information is stored locally and only the brand category (e.g. "Garmin", "Oura"), not the device model or firmware version, is included in Refresh Insights requests with your explicit consent.
7. (This section described Health Wallet, which is switched off in the app. See What Changed, Version 45.)
8. Flair Services
The app connects to api.flairhealth.app for certain non-AI functions:
- Latency Estimates: The endpoint
api.flairhealth.app/api/statsprovides latency estimates used for progress bars during AI requests. This endpoint receives only a feature identifier. It is stateless: no user data is sent, retained, or logged. - IP Address: AI providers never see your IP address; requests are routed through our server. Our server sees your IP address in transit, as every server does. The only application-layer use is a one-way cryptographic hash of it, held for about two minutes, solely to prevent abuse (rate limiting): never the raw IP, never linked to your identity beyond that window, never used to profile you, and never stored in any database. Our hosting provider's own infrastructure logs are bounded by their published retention policy, which we do not control and cannot shorten.
9. Location & Environment Data
With your permission, Flair uses your approximate location to request local weather, air quality (AQI), and UV index data from third-party environment services. The providers currently in use are:
- OpenWeatherMap: weather conditions and air quality data (Privacy Policy)
- Singapore National Environment Agency (NEA) via data.gov.sg: UV index and Pollutant Standards Index for Singapore users (Privacy Policy)
- Open-Meteo: a UV forecast for your area, and current UV outside Singapore (Privacy Policy)
Your coordinates are coarsened to approximately 1 km on your device before transmission. The coarsened location is sent to Flair's server, which requests environmental data from the providers listed above and caches the result for 30 minutes. Your exact location is never transmitted to these providers. No health data is included in these requests. Your coordinates are not stored beyond the cache period and are never linked to any identity. You can disable environment data in Settings.
Flair asks for location access only while you use the app. It uses your location to tailor Local Conditions to your area and, when you choose to record a route, to draw your route and measure its distance while a timer session runs, including when your screen is locked. Route data is stored only on your device and is never sent to Flair's servers. When you open a route map, your phone downloads map images from the OpenStreetMap Foundation, which receives your network address and the area the map shows, under its own privacy policy. No health data is sent.
Route maps load map images from:
- OpenStreetMap Foundation (United Kingdom): map images for route maps; it receives your network address and the area the map shows (Privacy Policy)
To name the place you are in, for your profile's city, a travel check-in or the location tag on an outdoor photo, your phone asks Apple's location service, for a position rounded to about 1 km, under Apple's own privacy policy.
10. Crash Reports
Flair ships no third-party analytics, tracking or crash-reporting SDKs. Document Scanner reads text with Google's ML Kit, on your phone. ML Kit sends Google information about its own performance and use (device and app details, an identifier for this installation, timings and error codes), never your image or its text. To maintain stability, Flair may collect first-party crash logs (stack traces only), which contain no health data, no journal content, and no personally identifiable information. If we ever integrate a third-party crash-reporting tool, we will name it here and update this policy first.
11. Your Rights & Data Deletion
You have full control:
- Delete everything at any time via Settings → Reset App.
- Or delete Flair from your phone. Your journal, your Health Passport and the backups in Flair's own folder go with it. A few items Flair keeps in your phone's secure storage (the Keychain) can stay after the app is deleted: your 12-word key, your security settings and an encryption key. They stay so that you can restore a backup if you reinstall Flair. If you chose to protect your backups with your Apple ID, that key is also kept in your iCloud Keychain and reaches your other Apple devices; we have no access to it. To remove all of these too, use Delete All Data in Flair before you delete it. Backups you saved elsewhere, such as in iCloud Drive, stay where you saved them.
- Note: Data that originates from Apple Health or Google Health Connect, and the weight, height and mindful minutes Flair saved to Apple Health, are managed through those platforms and are not deleted when you delete Flair.
12. Data Ownership & Portability
- You own all of your health data. Flair makes no claim to any data stored on your device.
- You can export your data as an encrypted
.flairfile at any time. .flairfiles are encrypted using AES-256-GCM.- Flair cannot recover your data if your seed phrase is lost; no server-side backup exists. There is no password reset mechanism.
13. Regulatory Positioning
Flair Health is positioned as a general wellness product, not a medical device. Flair Health is operated by Regal Pines Pte. Ltd., a company registered in Singapore, and we align our practices with Singapore's Personal Data Protection Act 2012 (PDPA) and, where applicable, the EU General Data Protection Regulation (GDPR).
- For data protection enquiries, contact: support@flairhealth.app
- Data Protection Officer: Regal Pines Pte. Ltd.
- Right to Complain: You may lodge a complaint with the Personal Data Protection Commission (PDPC) if you believe your personal data has not been handled in accordance with the PDPA. Contact: https://www.pdpc.gov.sg/
14. Children's Privacy
Flair Health is not directed at children under the age of 13 (or the applicable minimum age in your jurisdiction). We do not knowingly collect personal information from children under 13 in the United States or under the relevant minimum age elsewhere.
Our App Store age rating is 13+ in most markets. We do not require account creation, and the app collects no names, email addresses or other identifying information.
If we become aware that we have inadvertently received personal information from a child under the applicable minimum age, we will promptly delete that information and, where required by law, notify the child's parent or guardian.
If you are a parent or guardian and believe your child has provided personal information to Flair Health, please contact us at support@flairhealth.app. We will investigate and delete the data promptly.
Flair asks for your birth year during setup. It is stored on your device and is never transmitted as a date. It is used to check that you are 18 or over for the features that need it (every AI feature, and the journal training export), and, when you use an AI feature whose agreement lists your age group, to work out that group on your phone before it is sent; section 5 says which features send it.
15. Contact Us
Questions? Reach out at support@flairhealth.app.
16. Where Your Data Is Processed
Some of the services Flair uses are outside Singapore. When your data goes to them, we protect it as follows.
Our processors (our hosting, database, cache and AI providers) handle your data only to provide Flair to you. The table below shows, for each one we have confirmed, where it processes your data and the agreement that governs it. Our database (Supabase) and cache (Upstash) providers, the hosting of Flair's own server (Vercel), Google Cloud Vertex AI and OpenAI are not yet in the table; we will add them in the next version.
Services that receive data because you asked for a feature (weather and map images) receive only what that feature needs, as each feature's agreement in the app shows, under their own privacy policies.
| Recipient | What it receives | Country | Basis |
|---|---|---|---|
| Anthropic (Claude) | For Ask Flair, what section 5 lists for it; for Flair's own team only, the data fields each AI feature's agreement lists. No names or account identifiers. Anthropic deletes requests and answers within 30 days; flagged content may be kept for up to two years. | United States (stored); processing may be routed to the United States, Europe, Asia or Australia | Data processing agreement, incorporated into Anthropic's Commercial Terms |
| OpenWeather Ltd (OpenWeatherMap) | Your position rounded to about 1 km, sent from Flair's server | United Kingdom | No identifier: the position is rounded on your phone and sent from Flair's server, so OpenWeather cannot tell whose it is. OpenWeather is bound by UK data protection law. |
| OpenMeteo GmbH (Open-Meteo) | Your position rounded to about 1 km, sent from Flair's server | Switzerland | No identifier: the position is rounded on your phone and sent from Flair's server, so Open-Meteo cannot tell whose it is. Open-Meteo is bound by Swiss data protection law. |
| OpenStreetMap Foundation | Your network address and the area a route map shows | United Kingdom | The OpenStreetMap Foundation is bound by UK data protection law and its own privacy policy. |
| Apple | A position rounded to about 1 km, to name the place you are in | United States | Your phone's own location service, under Apple's privacy policy with you. Flair's server sends Apple nothing. |
What Changed
Version 43, November 2026. Section 5: our hosting provider now keeps its runtime logs for one day, not one hour, because we moved to a paid plan. The logs still hold no content.
Version 44, November 2026. Removed "fully" from "offline-first" and named the features that need a connection: the AI features, Local Conditions and route maps.
Version 44, November 2026. Section 1: "no network request on app launch" did not hold in two cases you control. With Local Conditions on, opening Today refreshes your area's readings through Flair's server, as the Local Conditions agreement in the app has always said. A Magic Lens photo taken offline is sent, as you approved, when the app next has a connection. The sentence now names both, and Ask Flair is added to the list of AI features.
Version 44, November 2026. Section 1: "The only exception" for the AI features now reads "One exception", because Local Conditions is another.
Version 45, November 2026. A correction. In builds up to 49, four paths could request local weather and air quality data using your approximate location without the Local Conditions consent: an outdoor workout imported from Apple Health, that same import run by a background task, a pass back over workouts already on the phone, and the Outdoors answer on a workout. The statements in sections 1, 2, 5 and 9 that no data leaves your device without your per-feature consent did not hold for those paths. The fix checks that consent at a single point and fails closed if it cannot be read. No data beyond your position rounded to about a kilometre was involved, and nothing identifying you was sent to the weather services. The fix reached testers in build 50 on 24 October 2026.
Version 45, November 2026. Section 2: removed the interim exception for the stated health objective. The fix, which puts the objective on the Refresh Insights, Inspire Me and Weekly Wrapped consent forms, reached testers in build 48 in September 2026; the exception should have come out then and stayed up until this version.
Version 45, November 2026. Section 5: "anonymous health profile" is replaced by a description of what each feature sends (profile bands, or for Body Age the figures themselves). That data carried no name or identifier, but it was about you, so "anonymous" was the wrong word; the section now says what goes.
Version 45, November 2026. Removed Body Age, Weekly Wrapped, Inspire Me and Health Wallet from sections 1, 5, 6, 7, 8 and 14: they are switched off in the app and nobody can use them. What each sent while it was available is in the earlier versions of this policy, which stay in the history below. Their text, and their agreements in the app, return together before any of them returns.
Version 45, November 2026. Closing paragraph: removed the promise that material changes are announced in the app on your next launch, which the app does not do. The version history on this page, and the app's own agreements for what it sends, are the record. Terms section 11: removed the promise of an in-app notice on your next launch, which the App does not give; the version date and this history are the record. Terms section 8: the names and logo are described as belonging to Regal Pines; the earlier text called them trademarks or pending trademarks, and none is registered or filed.
Version 45, November 2026. Section 14: the birth year's uses are now stated in full. It also sets the age group that Refresh Insights, Eat Now and Do Now send, and it gates the journal training export; the earlier text named only AI availability and Body Age. The agreements in the app listed the age group throughout.
Version 45, November 2026. Section 5: telemetry retention corrected from 90 to 30 days, the 12-month daily count per feature named, and the daily overall totals, which are kept as counts with no set limit, named.
Version 45, November 2026. Section 5, Daily Quests: the list of what it sends was wrong both ways. It named a health profile that is not sent, and it omitted injuries, food allergies, medical conditions and fasting mode, which are. The agreement shown in the app listed them correctly throughout; the policy now matches it.
Version 45, November 2026. Section 5, Document Scanner: 'anonymised' removed. The redacted text is about you with your identifiers removed on the phone; it was never anonymous, and the sentence now says what leaves and why you see the redactions first.
Version 45, November 2026. Section 5: Google's retention for AI requests is now stated (a copy for up to one day; Eat Now's grounding queries for up to three days), as the agreements in the app have said since 12 October 2026, on testers' phones from build 50.
Version 45, November 2026. Section 5, Eat Now: the list of what it sends was incomplete and named a profile that is not sent. It now lists the venue and area, your drinks preference, your age group, the medical conditions by name, today's food summary and active food quests, as the agreement shown in the app has listed them.
Version 45, November 2026. Route maps load map images from OpenStreetMap, which receives your network address and the area shown; the earlier text said route data was never transmitted to any server.
Version 45, November 2026. Added: to name the place you are in, for your profile's city, a travel check-in or the location tag on an outdoor photo, your phone asks Apple's location service, for a position rounded to about 1 km, under Apple's own privacy policy.
Version 45, November 2026. Removed the statement that Flair may request 'Always' location access; Flair asks only while you use the app.
Version 45, November 2026. Added to section 9: when you choose to record a route, it is recorded while a timer session runs, including when your screen is locked.
Version 45, November 2026. Added section 16, Where Your Data Is Processed: the services outside Singapore that receive your data, what each receives, its country and the basis that protects it. Our database and cache providers and the hosting of Flair's own server are not yet in its table; the section says so.
Version 45, November 2026. Removed the Eat Now and section 9 text about venue lookup, and Foursquare and Recruit with it. That lookup is switched off; the text, the table rows and its own agreement in the app return together when it is switched on.
Version 45, November 2026. In section 1, "We do not sell, share, or monetize your information" is replaced by "We do not sell your information, rent it, or use it for advertising": the word "share" was inaccurate, because sections 5 and 9 of this policy have always described data going to AI providers and environment services with your consent.
Version 45, November 2026. Section 5 now names the AI providers as they are. Google Gemini on Google Cloud Vertex AI answers every AI request the app sends, except Ask Flair's, which Anthropic's Claude answers. Other models are available only for Flair's own team. The earlier text said a provider was selected automatically based on availability. Until 2 November 2026, when Google could not answer, some requests went to OpenAI's GPT-4.1-mini instead; that backup has ended. The sentence saying Eat Now needs a search only Google offers is removed. The Terms, section 4, say the same.
Version 45, November 2026. Section 5 now describes Ask Flair, a chat that Anthropic's Claude answers as its only provider: what it sends with every message, what it sends only when you tap Share, the country check, and how long Anthropic keeps requests. Section 16's Anthropic row now names Ask Flair. Ask Flair reached testers in build 51, and its agreement in the app listed all of this from the start; this policy had not yet described it.
Version 45, November 2026. Section 1: "Phone Sleep Tracking" is replaced by the sleep timer, which measures no movement; if you turn on Listen for snoring, it listens on your phone and keeps only the times and counts of snoring, which are never sent. The earlier text described Focus Mode's motion sensing, which was removed in October 2026, and said snoring figures could go to an AI feature, which they no longer do. Voice Input's sentence about audio now covers voice input only, and Smart Habits notes that Ask Flair sends today's habits if you tap Share. Section 6 now says Flair writes your weight, height and mindful minutes to Apple Health, if you allow it; the earlier text wrongly said it wrote nothing. Section 9 adds Open-Meteo, already named in section 16. Section 10 and section 5's Document Scanner paragraph now disclose Google's ML Kit, which reads documents on your phone and sends Google information about its own use, never your image or its text. Section 16 names Google Cloud Vertex AI and OpenAI as not yet in its table, and states the basis for OpenWeather, Open-Meteo, the OpenStreetMap Foundation and Apple. Terms, section 8: exercise drawings shared by their artists under a Creative Commons licence follow that licence, not these Terms.
Version 45, November 2026. Section 11 and Terms section 9: deleting Flair did not remove everything, as both said. Your journal, your Health Passport and the backups in Flair's own folder go with the app, but a few items in your phone's secure storage (the Keychain) can stay: your 12-word key, your security settings and an encryption key, and, if you chose the Apple ID option, the backup key in your iCloud Keychain. They stay so that you can restore a backup if you reinstall. Delete All Data in the app removes them too. The section 11 note now also names the weight, height and mindful minutes Flair saved to Apple Health, which stay there.
Version 45, November 2026. Terms: removed Body Age and Health Wallet from section 2, and section 6, which described Health Wallet, now says so; both are switched off in the app, and their text returns with them.
We may update this policy. The version and date at the top of this page change with every update, and the history below records each one. A change to what the app sends is shown to you in the app's own agreement before anything is sent under the new terms.