Alex. Privacy Policy
Version 1.4 · Last updated: 19 November 2026
This policy explains how GWB Technologies Ltd collects and uses your personal data when you use the Alex app and website, whether as a member, as the client of a personal trainer, or as a personal trainer using Alex PT. It is written to meet our duties under the UK GDPR, the Data Protection Act 2018 and the Privacy and Electronic Communications Regulations (PECR) and, for people who live in Ireland or France, the EU GDPR.
1. The short version
- We use your data to coach you. We never sell it and never use your health data for advertising.
- Health information (such as training, nutrition, sleep, weight, cycle, glucose and injury information) is special category data. We only process it with your explicit consent, which you give on separate screens in the app and can withdraw at any time.
- Your coaching chats are processed by AI providers (Anthropic, and OpenAI for search and as a backup). You agree to this separately, and can switch it off at any time. They act on our instructions and may not train their models on your data.
- No AI model is being trained on anyone's data today. If that ever changes, we will only include your data if you switch on Use my anonymised data to help improve Alex. It is off by default, it is only for people aged 18 or over, and you can withdraw it at any time.
- If you have a personal trainer, they only see what is described in section 9. They cannot see your screening answers, cycle data, pregnancy status or private AI chats.
- You can download or delete your data at any time, including on the web at www.getalex.app/delete-account.
2. Who we are and how to contact us
GWB Technologies Ltd (trading as "Alex."), company number 17278675, registered office 167–169 Great Portland Street, 5th Floor, London, W1W 5PF, is the controller of your personal data except where section 9 says otherwise. ICO registration number: ZC252989.
Privacy questions and requests: hello@getalex.app (subject "Privacy"), or Profile, then Privacy and data (/profile/privacy) in the app.
Data protection lead: our founder, George Bradbury, is responsible for data protection. We have assessed whether the law requires us to appoint a Data Protection Officer (DPO). Although we process health data, our processing is not currently on a scale that requires one. We will review this as Alex grows and will update this policy if we appoint a DPO.
Alex is currently available only to people aged 18 or over who live in the UK, Ireland or France.
3. What we collect
Information you give us
- Account details: name, email, password (stored hashed by our database provider; there is none if you sign in with Google or Apple), date of birth, phone number (if you choose SMS/WhatsApp messages), country.
- Profile and goals: sex, height, weight, experience level, goals, available equipment, schedule and preferences.
- Your city: the town or city you can add to your profile. We use it to show the local weather on your Home screen and to make Alex's advice weather-aware. To do that, our servers send the place name to our weather provider, Open-Meteo (section 10), which sends back the weather. We do not ask for your device's precise location. You can change or remove your city in your profile, or hide the weather there, at any time.
- Health screening (PAR-Q style): answers about heart conditions, chest pain, dizziness, blood pressure, pregnancy, injuries, medication (whether you take any, not the details), eating disorders and similar questions.
- Logs: workouts, food and drink, weight and body measurements, sleep, mood and energy, soreness and injuries, and (if you choose) menstrual cycle information.
- Pregnancy or birth status (optional): only if you choose to tell Alex that you are pregnant or have had a baby, we keep that and one date you choose (your due date, or the birth date). This is special category health data. We keep it only with your separate, explicit consent, use it only to keep your plans, food targets and messages safe, and never show it to your coach. You can change the date or delete it at any time in Profile, then Your health, then Pregnancy and after birth (/profile/health), or by telling Alex. Deleting it removes it for good, and it is also deleted with your account (section 12).
- Photos and videos: food photos (sent to our AI provider to estimate nutrition and not stored permanently), progress photos (stored privately in your account), and exercise technique videos you share with a coach (private, not analysed by AI, and automatically deleted after 90 days).
- Messages: your chats with the AI coach, and messages with your personal trainer (if you have one).
- What Alex remembers: facts you tell Alex, saved so that later replies can be personal to you. You can see each fact and delete it in Profile, then Privacy and data, then What Alex remembers (/profile/privacy). These facts are deleted with your account (section 12).
- Workout facts: simple facts about your workouts (whether a session was done, skipped or cut short, and how hard it felt), kept so later plans can fit you better. This is on unless you switch it off. It never includes your chats, heart-rate traces, calories or body weight. You can switch it off in Profile, then Privacy and data, then Workout facts for better plans (/profile/privacy), which deletes the stored facts. Facts older than 24 months are deleted, and they are deleted with your account (section 12).
- Support and complaints: what you tell us when you contact us.
Information from services you connect (only if you connect them)
- Apple Health (HealthKit): workouts (with average and maximum heart rate), sleep (including sleep stages and the times you went to bed and woke up), steps, distance (walking, running and cycling), exercise minutes, flights climbed, weight, body fat percentage, lean body mass, waist, heart rate (including your lowest, average and highest through each day), heart rate variability, resting heart rate, VO2 max, blood oxygen, breathing rate, and the energy you burn (active and resting), depending on what you allow. We only read from Apple Health. We never write to it.
- Health Connect (Android): workouts (with average and maximum heart rate), sleep, steps, distance (walking, running and cycling), exercise minutes, flights climbed, weight, body fat percentage, heart rate (including your lowest, average and highest through each day), resting heart rate, heart rate variability, VO2 max, blood oxygen, breathing rate, and the energy you burn (active and resting), depending on what you allow. If you allow it, Alex also reads new Health Connect data in the background, about once an hour, so your Home and Stats stay up to date. You can turn this off at any time in Health Connect or by disconnecting it in Alex. We never write to it.
- Garmin: activities, heart rate, sleep, stress and similar data. If you ask us to, we also send workouts to Garmin.
- Dexcom or FreeStyle Libre (LibreView/LibreLinkUp): glucose readings and trends. To retrieve them, we store the login details you give us for that account, encrypted, and use them only to fetch your readings (section 8).
Information from others
- Google or Apple, if you choose to sign in with them: we ask for your name and email address and nothing else (no contacts, calendar or photos, and no location). Apple lets you hide your real email: if you do, we receive a private address that Apple forwards to your own inbox, and Apple sends your name only the first time you use it with Alex. We use these to create or find your account, as we would the details you type in. Their reply also carries an account ID and, from Google, a link to your profile picture. Our database provider (Supabase) keeps these with your sign-in record. We do not use them. Google and Apple tell us nothing about what you do in Alex, and we do not tell them. If you sign in with Apple, we also keep an Apple refresh token. It is stored encrypted. We use it only to ask Apple to revoke Alex's access when you delete your account, and we delete the token at that point.
- Your personal trainer: if you join a coach using their code, the programmes, notes and check-in feedback they give you.
- Stripe: confirmation of your subscription status and payments. We never see your full card details.
Information collected automatically
- Device and app information (device model, operating system, app version, language, time zone), IP address, log and security data, crash and error reports, and how you use features. See section 13 and our Cookie Policy.
We do not use HealthKit, Health Connect, Garmin or glucose data for advertising or marketing, we do not share it with advertisers or data brokers, and we do not store it in iCloud.
4. Your consent choices
We ask for these separately, with a clear on/off choice, and never pre-ticked. There are six. Each is its own choice: none is bundled with another or with our Terms, and you can switch any one off without affecting the others.
| Consent | What it allows | Can I use Alex without it? |
|---|---|---|
| Health data | Using the health information you enter or connect (section 3) to set your calorie and protein targets and to keep Alex's advice safe and personal | You need this for personalised coaching. Without it the AI coach still answers, but only with general suggestions based on your goals and preferences and none of your health information, and you can only use non-personalised content and your account settings |
| AI services | Sending your messages, and the details Alex needs to reply, to our AI providers, Anthropic and OpenAI (section 6), so that Alex can write your replies and insights. This includes your health information only if you have also agreed to Health data | You need this for Alex's chat replies and AI insights. Without it you can still log food and workouts by hand |
| Cycle tracking | Using menstrual cycle information to adapt coaching | Yes |
| Connected apps and devices | Importing data from the services you choose to connect (Apple Health, Garmin, Dexcom, LibreView) and, for Garmin, sending workouts to it. This is one switch for all of them, and nothing is read until you connect a service | Yes |
| Use my anonymised data to help improve Alex (off by default, 18 and over only) | Using a copy of your data with your name, email and other identifiers removed to improve Alex, and to train and evaluate AI models of our own (section 7). Nothing is being trained on anyone's data today | Yes. It is never a condition of any plan |
| Marketing emails | Sending you news and offers by email. This is opt-in only: it stays off until you switch it on | Yes |
You can withdraw any of them at any time, or by emailing us. Each one has its own switch.
Pregnancy and after birth is one more optional agreement, asked only if you choose to tell Alex. It keeps your pregnancy or birth status and its date so that Alex keeps your plans, food targets and messages safe for pregnancy and the weeks after birth. You can use Alex fully without it.
- Health data: Profile, then Your health, then Health-data consent (/profile/health).
- Cycle tracking: Profile, then Your health, then Sex and cycle (/profile/health).
- Pregnancy and after birth: Profile, then Your health, then Pregnancy and after birth (/profile/health), or tell Alex.
- AI services: Profile, then Privacy and data, then AI services, connected apps and marketing (/profile/privacy).
- Connected apps and devices: Profile, then Privacy and data, then AI services, connected apps and marketing (/profile/privacy).
- Marketing emails: Profile, then Privacy and data, then AI services, connected apps and marketing (/profile/privacy).
- Use my anonymised data to help improve Alex: Profile, then Privacy and data, then Help improve Alex (/profile/privacy).
Withdrawing consent does not affect processing we carried out before you withdrew it. If you withdraw your health data consent, the features that depend on it will stop working, but we will not stop you cancelling or downloading your data. Withdrawing marketing consent stops marketing only: account and security emails are not marketing and still arrive.
5. What we use your data for, and our lawful bases
| Purpose | Data | Lawful basis (UK GDPR Art 6) | Condition for health data (Art 9) |
|---|---|---|---|
| Creating and running your account, providing the plan you chose | Account, profile (including the name and email from Google or Apple, if you sign in with them) | Contract | — |
| Personalised coaching, plans, AI chat, progress insights | Health data, logs, connected-service data, and facts you tell Alex that we save (section 3) | Contract | Explicit consent (Art 9(2)(a)) |
| Safety checks: health screening, stopping or limiting coaching and pointing you to medical help | Screening answers, messages that mention warning signs | Contract and legitimate interests (keeping you safe) | Explicit consent; and for keeping a record of screening outcomes after you leave, legal claims (Art 9(2)(f)) |
| Sharing data with your personal trainer (if you connect one) | Section 9 | Contract (at your request) | Explicit consent |
| Payments and subscriptions | Account, subscription and payment records | Contract; legal obligation (tax records) | — |
| Service emails, SMS and WhatsApp (e.g. reminders you set, renewal notices, security alerts) | Contact details | Contract; legal obligation (subscription notices) | — |
| Security, fraud and abuse prevention, error monitoring | Device, log and error data (section 10). Health information written as ordinary words in an error message can be included | Legitimate interests (keeping Alex secure and working) | Explicit consent (Art 9(2)(a)) |
| Improving the Service using de-identified usage statistics | Usage data | Legitimate interests (improving Alex) | Where health data is involved: explicit consent |
| Training and evaluating AI models of our own | Section 7 | Consent | Explicit consent (Art 9(2)(a)) |
| Marketing emails, SMS, WhatsApp; Meta Pixel on our marketing website | Contact details; cookie data | Consent (PECR) | — (never health data) |
| Complaints, legal claims and compliance | Relevant records | Legal obligation; legitimate interests (defending claims) | Legal claims (Art 9(2)(f)) |
Where we rely on legitimate interests, we have balanced our interests against yours. You can ask us for details and you have the right to object (section 12).
6. The AI coach and AI providers
- You agree to this as AI services (section 4), separately from your health data consent. If you switch it off, Alex stops sending your messages to Anthropic and OpenAI, and chat replies and AI insights stop.
- Anthropic (Claude) generates most coaching responses. When you use the coach we send your message and the relevant context it needs (for example your goals, recent logs and screening-based safety limits) to Anthropic.
- OpenAI is used in two limited ways: (1) to turn your message into a numerical "embedding" so we can find relevant research in our knowledge base; and (2) as a backup (GPT-4o mini) that answers with the same context if Anthropic is unavailable.
- We send only what is needed to answer you and we do not send your name or email address with the context.
- Under our contracts, Anthropic and OpenAI process this data only to provide their service to us. They are not permitted to train their models on it. They may keep it for a short time (currently up to 30 days) to detect misuse, and longer only if content is flagged for breaking their usage policies (Anthropic may keep flagged content for up to 2 years), or if the law requires it.
- Both providers are based in the USA. See section 11 for how your data is protected.
- Automated decisions. Alex's AI personalises your plan and our safety rules may automatically limit certain programmes (for example restricting high-intensity training or calorie deficits based on your screening). These decisions do not have a legal effect on you, but because they use health data, you can ask for a human to review any such decision, express your view, and challenge it by contacting us. We will respond within one month.
7. Training our own AI models (optional)
If, and only if, you switch on Use my anonymised data to help improve Alex in Profile, then Privacy and data, then Help improve Alex (/profile/privacy), we may use your coaching conversations, logs and related health data to train, fine-tune and evaluate AI models built and controlled by GWB Technologies Ltd, to make Alex's coaching safer and more accurate.
No model is being trained on anyone's data today. The switch records your choice now, so that nobody's data is ever included without them having said yes first.
- This is off by default, is based on your explicit consent (UK GDPR Art 9(2)(a)), and is never a condition of any plan. We keep a record of when you switched it on or off and the wording you saw.
- It is only for people aged 18 or over. Alex is 18 and over everywhere, and we never include anyone under 18.
- Before any training, we remove direct identifiers such as your name, email and contact details, and we apply measures to minimise personal information in training data and to stop models reproducing it.
- We will not share your training data with anyone else to train their models, and we will not sell it.
- You can switch it off at any time. From then on, we will exclude your data from any future training or evaluation. Please be aware that it is not technically possible to remove the influence of your data from a model that has already been trained. This is why we ask for your consent separately and in advance.
Separately, we may create anonymised, aggregated statistics (for example "average weekly training volume across members") that cannot identify you, to improve the Service. Anonymised data is not personal data.
8. Connected services
- Apple Health (iPhone). When you first connect Apple Health, we show you what we read and why before Apple's own permission screen, and we ask for your agreement to Connected apps and devices (section 4) and for your health data consent if you have not already given them. You then choose which data types to share, and you can change this at any time in Settings > Health > Data Access & Devices > Alex on your iPhone. We read only the types you allow. Data from HealthKit is used only to provide and improve your coaching and is never used for advertising or sold.
- Health Connect (Android). When you first connect Health Connect, we show you what we read and why before Health Connect's own permission screen, and we ask for your agreement to Connected apps and devices (section 4) and for your health data consent if you have not already given them. We ask to read twelve things only: steps, distance, active energy, resting energy, heart rate, resting heart rate, heart rate variability, VO2 max, weight, body fat, sleep and workouts. We use them to coach you with your real numbers. You choose which of them to allow, and we read only the ones you allow. We never write to Health Connect. Data from Health Connect is never used for advertising and never sold. To switch it off, open Health Connect on your phone and remove Alex.'s access, or tap Disconnect under Connected apps in Alex. What was already imported stays in your history until you delete it or your account.
- Garmin. You connect through Garmin's own authorisation screen. Garmin is an independent controller of the data it holds. When we send workouts to Garmin at your request, Garmin's terms and privacy policy apply to that data.
- Dexcom and LibreView (glucose monitors). To retrieve your readings, you give us your Dexcom Share or LibreLinkUp login. We store it encrypted, use it only to fetch your glucose data, never share it, and delete it immediately when you disconnect or delete your account. Dexcom and Abbott are independent controllers of the data they hold. Glucose information in Alex is for general wellness insight only and must not be used for diabetes management or treatment decisions.
- Calendar (coaches only). A personal trainer can connect their Google or Microsoft calendar so client bookings appear there. Google and Microsoft are independent controllers of the coach's calendar data.
You can disconnect any service in Profile, then Connected apps (/profile/apps). Data already imported stays in your account until you delete it or your account.
9. Personal trainers and coaches
If you are a client. If you join a coach using their code:
- Your coach can see: your name and profile, goals, training logs and programme progress, food and nutrition logs, weight trend, check-ins, progress photos you choose to share, technique videos you send, and messages between you.
- Your coach cannot see: your health screening answers, cycle data, pregnancy status, glucose data, or your private chats with the AI coach. Instead they may see a general flag, such as "modified programming advised", so they can coach safely.
- Roles. We are the controller of your Alex account and app data. When you connect a coach, we share the information above with them at your request, and the coach becomes an independent controller of the information they receive and the records they keep about coaching you. The coach must give you their own privacy information. Where a coach keeps their own records in Alex PT (for example private coaching notes), we store them on the coach's behalf as their processor.
- You can disconnect your coach at any time in Profile, then My Trainer, then Go solo. They will then stop receiving new data. Records the coach already holds are their responsibility, and you can ask them for access or deletion.
If you are a coach. We are the controller of your coach account, profile, directory listing, verification documents (qualifications and insurance), subscription and platform fee records. Our Coach Terms explain how we act as your processor for your client records.
10. Who we share your data with
- Service providers (processors) who help us run Alex, under contracts requiring them to protect your data and act only on our instructions. The current list is at www.getalex.app/subprocessors and includes Supabase (database and storage), Vercel (hosting), Anthropic and OpenAI (AI), Stripe (payments), Resend (email), Twilio (SMS and WhatsApp), Sentry (error monitoring) and Open-Meteo (weather, sent only the city on your profile) and Meta (Pixel, on marketing pages only, if you accept cookies).
- Independent controllers who make their own decisions about data under their own privacy policies: Apple and Google (app stores, push notifications and, if you choose them, Sign in with Apple and Sign in with Google), Stripe (for its own fraud prevention and legal duties, and for coach payments), Garmin, Dexcom, Abbott, Google/Microsoft calendars (for coaches), your personal trainer (section 9), and HM Revenue & Customs (we must report certain information about coaches' platform income to HMRC).
- Professional advisers (lawyers, accountants, insurers) under a duty of confidentiality.
- Law enforcement, regulators or courts, where the law requires it or it is necessary to protect someone's life or safety.
- A buyer or investor if our business is sold or restructured, under confidentiality terms. They must use your data in line with this policy.
We do not sell your personal data and do not share it for cross-context behavioural advertising.
Error reports (Sentry). We send error and performance reports to Sentry (Functional Software, Inc.) so we can find and fix faults. A report can include the type of error, the file and line in our code, the page or route, the HTTP method and status code, your role in Alex (member, client of a coach, or coach, and not your name or account id), the app environment, and a short trail of pages and requests leading up to the error. Request bodies, cookies and query strings are removed. Of the request headers, we keep only the browser's user-agent string (which names the browser and can name the device and operating system), the language, and the content type.
In the browser, Sentry is set so that it does not attach your IP address, cookies or user headers by default. On every report, whether it comes from the browser, our servers or the edge runtime, we remove any IP address, name, email or account id on the user field before the report is sent, and we keep only your role. We do not record your screen.
Before a report is sent we remove fields whose names show they hold health or personal information, and we remove measurements such as weight and glucose, email addresses and phone numbers from the text. We do not remove every ordinary word. If an error message contains health information written in ordinary words, that text can be included.
The app's Content-Security-Policy allows the browser to reach Sentry's EU ingest host, addresses ending in ingest.de.sentry.io, which Sentry uses for its EU region in Frankfurt, Germany. The same policy also allows the US-style host, addresses ending in ingest.sentry.io. Reports from the app are sent through our own /monitoring address, which forwards them to Sentry. The project address that chooses the host is set in our hosting configuration, not in this app's code. Our Sentry project is in the EU region, and reports are held in the EU (Frankfurt, Germany). The basis for that transfer is the UK adequacy regulations for the EU.
11. International transfers
Our main database is hosted in a data centre in a region we choose within our database provider's network (see our sub-processor list for the current region). Some providers are based in, or access data from, the USA or other countries outside the UK. When your data leaves the UK, we protect it with one of the following:
| Provider | Where | Safeguard |
|---|---|---|
| Supabase | Region shown on our sub-processor list; support staff may access from outside the UK | UK adequacy regulations (if the EEA), otherwise the EU Standard Contractual Clauses with the UK Addendum (in Supabase's DPA) |
| Open-Meteo | Germany / EU | UK adequacy regulations for the EU |
| Vercel, Stripe, Resend, Twilio | USA (and others) | UK Extension to the EU–US Data Privacy Framework ("UK–US data bridge"), with Standard Contractual Clauses plus the UK Addendum, or the UK IDTA, as a back-up |
| Sentry | EU (Frankfurt, Germany). Reports are held there (section 10) | UK adequacy regulations for the EU |
| Anthropic | USA | Standard Contractual Clauses with the UK Addendum (in Anthropic's DPA) |
| OpenAI | USA | Standard Contractual Clauses with the UK Addendum (in OpenAI's DPA) |
| Meta (Pixel) | USA | Standard Contractual Clauses with the UK Addendum (Meta's data transfer terms) |
We check that providers relying on the data bridge are listed on the Data Privacy Framework List with UK Extension coverage. You can ask us for a copy of the relevant safeguards.
12. How long we keep your data
| Data | How long |
|---|---|
| Your account and app data (profile, logs, health data, chats, and the facts Alex has remembered about you) | While your account is open. Deleted within 30 days of you deleting your account, and removed from our backups within a further 35 days |
| Accounts that haven't been used | After 30 days without use we stop daily and marketing emails (account and security emails continue). After 90 days we pause the account until you sign in. After 12 months we email you a warning, and 30 days later (13 months in all) we delete the account unless you sign in. Accounts with an active paid plan are not paused or deleted this way |
| Food photos | Not stored permanently. Processed to estimate nutrition, then discarded |
| Technique videos | Automatically deleted after 90 days |
| Stored Dexcom/LibreView login | Deleted immediately when you disconnect or delete your account |
| Your sign-in record (your email, and the Google or Apple connection if you use one) | Deleted with your account, within the same 30 days. Deleting your Alex account does not delete your Google or Apple account, and you can also remove Alex from your Google or Apple account settings at any time |
| Apple refresh token, if you sign in with Apple | Deleted when you delete your account. It is not kept for the 30-day archive |
| Health screening safety record (your screening answers, the safety outcome, and when you accepted which version of our disclaimer) | 3 years after your account closes, kept securely and separately, used only to deal with legal claims (this matches the time limit for personal injury claims) |
| Subscription, payment and tax records | 6 years after the end of the tax year they relate to |
| Complaints and correspondence | 6 years after the matter is closed |
| Error reports (Sentry) | 90 days |
| Security and admin audit logs | 2 years |
| Marketing preferences and consent records | For as long as needed to show you consented or opted out |
| AI providers' copies | See section 6 (normally up to 30 days) |
| Coach records | See our Coach Terms. Deleted or returned when the coach closes their account |
13. Cookies and similar technologies
We use strictly necessary cookies and local storage to log you in and keep Alex secure. We only use the Meta Pixel on our public marketing website, and only if you click Accept. It never runs in the app, on logged-in pages or on health pages. The app does not track you across other companies' apps or websites. You can change your choice at any time with the Cookie settings link in our website footer. See our Cookie Policy (www.getalex.app/cookies).
14. Marketing
We will only send you marketing emails if you have opted in. It is off until you switch it on, and we keep a record of when you did and the wording you saw (section 4). We do not rely on any other way to send you marketing emails, including because you are a customer. Every marketing email includes a one-click unsubscribe link, and you can also change this in Profile, then Privacy and data, then AI services, connected apps and marketing (/profile/privacy). Service messages (such as renewal reminders, security alerts and changes to our terms) are not marketing and will still be sent. Marketing by SMS or WhatsApp also needs your opt-in.
15. Your rights
You have the right to:
- access your data (you can download most of it in Profile, then Privacy and data, then Export my data (/profile/privacy));
- correct inaccurate data;
- delete your data. Delete your account in the app (Profile, then Account, then Pause or delete account, then Delete account, at /profile/account), on the web at www.getalex.app/delete-account, or by email;
- restrict or object to processing, including processing based on legitimate interests, and always to direct marketing;
- data portability: receive the data you gave us in a machine-readable format (JSON/CSV);
- withdraw consent at any time (section 4); and
- ask for human review of automated decisions (section 6).
We will respond within one month. In complex cases this can be extended by up to two further months, and we will tell you if so. We may need to confirm your identity first. Some rights have exceptions, for example we must keep payment records for tax purposes.
16. Complaints
If you are unhappy with how we have used your data, please complain to us first through www.getalex.app/complaints (choose "My personal data") or at hello@getalex.app. We will acknowledge your complaint within 30 days and respond without undue delay.
You also have the right to complain to your data protection authority:
- If you live in the UK, the Information Commissioner's Office (ICO): www.ico.org.uk/make-a-complaint, 0303 123 1113.
- If you live in Ireland, the Data Protection Commission (DPC): www.dataprotection.ie (how to complain: https://www.dataprotection.ie/en/individuals/my-rights/making-complaint-dpc).
- If you live in France or elsewhere in the EEA, the Commission nationale de l'informatique et des libertés (CNIL): www.cnil.fr (complaints: https://www.cnil.fr/fr/plaintes).
17. Children
Alex is for adults aged 18 and over. We do not knowingly collect data from anyone under 18. We previously allowed accounts for people aged 16 and 17. Those accounts are being closed: we have told the account holders, we will delete their data as described in section 12, and we will refund any unused paid period. If you think someone under 18 is using Alex, please tell us at hello@getalex.app.
18. Security
We use encryption in transit (TLS) and at rest, row-level access controls in our database, encrypted storage of connected-service logins and of an Apple refresh token where we hold one, restricted and logged staff access, and we remove health fields, measurements, email addresses and phone numbers from error reports before they are sent (section 10). Ordinary words in an error message can still include health information. No system is perfectly secure. If a breach is likely to put you at high risk, we will tell you without undue delay, and we will report breaches to the ICO where required.
19. Changes to this policy
We will tell you by email or in the app at least 30 days before a material change takes effect, and we will ask for your consent again if we want to use your data in a significantly different way that needs consent. The date at the top shows when this policy was last updated.