Privacy Policy

Last updated: October 28, 2026

Your habits and notes stay on your devices. Hazlo keeps your habits, check-ins, notes and settings on your iPhone or iPad, and today's and tomorrow's habits on your Apple Watch if Hazlo is installed there (watchOS installs it automatically unless you turned that off). There is no account, no iCloud sync, no advertising and no tracking across apps. Only if you agree, Hazlo sends error reports and usage statistics to PostHog, never your habits' names, your notes or your Health data (section 6). Apart from what you choose to export, share or email us, and what your iPhone and your Apple Watch send each other, what leaves your device is what purchases need and, from Hazlo 1.5.1, Apple Ads attribution: RevenueCat, the service that handles Hazlo Pro purchases, receives a random identifier, your device's identifier for vendor, your App Store purchase records, your first and latest app-open times and technical details, none of it linked to your identity. From Hazlo 1.5.1 it also receives Apple's Apple Ads attribution token, once per install (section 5). It never receives your habits or your Health data. From Hazlo 1.6.3, and only if you agree, the error reports and usage statistics in section 6 also leave it, for PostHog. From Hazlo 1.7.0, when you open Settings, About or Profile, Hazlo makes a light check, without any identifier, of whether the Ideas & Roadmap board answers, and with it your IP address reaches Feedzzie and Cloudflare, the network in front of Feedzzie's servers; if you use the board, the ideas you send and your votes go to Feedzzie with a random identifier, and an idea becomes public only once we approve it (section 10).

1. Who We Are

Hazlo is a habit tracking app for iPhone and iPad, with a companion app for Apple Watch, made by Mike Pulgar Olguin, an individual developer based in Spain ("we", "us"). We are responsible for the personal data described in this policy, which explains what the app stores, what leaves your device, who receives it and the choices you have. Contact: [email protected].

2. What Hazlo Stores on Your Device

Everything you create in Hazlo is stored on your device: your habit data in a database built with Apple's SwiftData framework, and your preferences in the app's settings storage, inside space that only the Hazlo app and its own widgets can open; your Apple Watch keeps a copy of today's and tomorrow's habits, as explained below. Depending on the features you use, this includes:

  • Habits: name, icon, color, schedule, goal and unit, category, routines, linked Health metric, streak status and whether the habit is archived.
  • Check-ins: the date and amount of each completion, optional notes, and whether it was completed automatically from Apple Health.
  • Categories, routines and reminders: names, icons and colors, routine days and times, and reminder times, days and messages.
  • Profile: the name you choose to enter (optional), an avatar emoji, your level, XP, and your streak and completion totals.
  • Badges, streak freezes and weekly reflections (the answers you write).
  • Setup answers and settings: the areas you want to work on, your preferred time of day, past obstacles and commitment level, plus preferences such as appearance, reminder times and the first day of the week.
  • Your answer about sharing error reports and usage statistics, when you gave it and, if you share, the random identifier described in section 6.
  • From Hazlo 1.7.0, if you open the Ideas & Roadmap board: its random identifier, kept in your device's keychain, which ideas you sent, the ideas you reported, the authors you blocked and that you accepted the board rules (section 10).

Widgets, Siri, Shortcuts and Control Center read and update this same data on your device. If Hazlo is installed on your Apple Watch (watchOS installs it automatically unless you turned that off), your iPhone sends it today's and tomorrow's habits (their names, icons, colors, goals, units, today's progress, streaks and reminder times), your overall streak, your theme and whether you have Hazlo Pro, so the watch and its complications can show them. The watch keeps the latest copy and sends your iPhone what you log on it; your iPhone records it. This goes between your two devices through Apple's watch connection; Hazlo never sends it to us or stores it in iCloud. We never receive a copy of any of it.

3. No iCloud, No Cloud Sync, No Account

Hazlo does not use iCloud or CloudKit and does not sync your data to any server or between your iPhone and iPad. The only other device it reaches is your paired Apple Watch, as described in section 2. It has no leaderboards, friends or public profiles, and there is no sign-up or account. To move the data included in Hazlo's backup format to another device, you can export and import a backup (section 8).

4. Apple Health

Connecting Apple Health is optional. When you link a habit to a Health metric, Hazlo asks for permission to read that metric only and uses it to fill in the habit's progress. The metrics Hazlo can read are steps, walking and running distance, exercise minutes, water intake, mindful minutes, sleep and stand hours.

  • Hazlo only reads Health data. It never writes to Apple Health.
  • It may read in the background when Health reports new data for a linked metric, so your habits stay up to date.
  • What Hazlo keeps: for a yes/no habit, only that the habit was completed that day and that the completion came from Health. For a habit that counts an amount, such as steps, the day's total it reads is saved as that day's progress when it is higher than what you logged by hand.
  • Hazlo never sends Health data to us, to RevenueCat or to anyone else, and never uses it for advertising. For a habit linked to Health, your Apple Watch gets only whether it is done, its streak, whether Health has recorded that metric in the past week and, for a habit with a weekly or monthly target, how many times it has been done in that period; never its total. Apart from what reaches your Apple Watch, completions derived from Health can leave your device only when you choose to export a backup (section 8) or share an image that includes them, such as a Year in Pixels grid (section 9).
  • You can turn off Auto-Sync with Health in Hazlo's settings, and change or revoke access at any time in the iOS Settings app (Privacy & Security → Health → Hazlo).

5. Purchases and RevenueCat

Hazlo is free to use. Hazlo Pro is an optional in-app purchase (a subscription or a one-time lifetime purchase) sold through Apple's App Store. Apple processes the payment under its own privacy policy (apple.com/privacy); we never see your payment details.

To check whether you have Pro, show prices and free-trial eligibility, and complete and restore purchases, Hazlo uses RevenueCat, a service of RevenueCat, Inc. (United States) that processes this data on our behalf. The app contacts RevenueCat when it opens and whenever you return to it, whether or not you have bought anything, and when you view, buy or restore Pro. RevenueCat receives:

  • a random identifier, a random user ID that RevenueCat's software creates on your device for each installation of Hazlo. It is not your name, email address or Apple Account;
  • app-open activity: when you first and most recently opened Hazlo, recorded under that random identifier when the app contacted RevenueCat;
  • a device identifier: the identifier for vendor (IDFV) that iOS assigns on your device to apps from the same developer. It is not the advertising identifier;
  • your App Store purchase records for Hazlo: product, price and currency, dates, and trial and renewal status;
  • technical details sent with each request, such as your device model, iOS version, Hazlo version, preferred languages and App Store country. Like any online service, RevenueCat also sees your IP address;
  • from Hazlo 1.5.1, Apple's Apple Ads attribution token (AdServices), once per install. It lets an install that came from an Apple Ads ad be tied to that ad's campaign, ad group and keyword. It needs no tracking permission, is not linked to data from other companies and says nothing about your habits or your Health data.

None of this is linked to your identity: Hazlo does not give RevenueCat your habits, your Health data, your name or your email address, and it has no account that could tie these records to you. RevenueCat keeps a record under the random identifier even if you never buy anything. The data is used to make purchases work: to check whether you have Pro, show prices, and complete and restore purchases. RevenueCat records your first and latest app opens to count new and active customers in aggregate charts, and uses purchase records to provide aggregate purchase analytics such as revenue charts and dashboards; those analytics are not linked to you. None of this is used for tracking, and Hazlo shows no ads. Through Hazlo 1.5.0, Hazlo did not turn on RevenueCat's optional advertising and attribution features. From Hazlo 1.5.1 it turns on one of them, the collection of Apple's AdServices attribution token, which we use only to tell which of our Apple Ads ads an install came from. Hazlo does not request the advertising identifier, so RevenueCat does not receive it. Accordingly, Hazlo's App Store privacy label declares Purchases > Purchase History (App Functionality, Analytics), Identifiers > User ID (App Functionality, Analytics), Identifiers > Device ID (App Functionality, Analytics), and Usage Data > Product Interaction (Analytics) and, from Hazlo 1.5.1, Usage Data > Advertising Data (Developer's Advertising or Marketing). From Hazlo 1.6.3 it also declares, for what PostHog receives with your consent (section 6), Diagnostics > Crash Data and Diagnostics > Other Diagnostic Data (App Functionality) and Usage Data > Other Usage Data (Analytics); Product Interaction, User ID and Purchase History cover PostHog's events too. They are listed as linked to you, because each travels with a random identifier (RevenueCat's, or PostHog's in section 6) that is never your name, email or Apple Account; none of them is used to track you. RevenueCat stores the data in the United States under a data processing agreement that includes the European Commission's Standard Contractual Clauses. RevenueCat keeps these records for as long as they are needed to operate purchases, provide Pro features and aggregate app-open and purchase analytics, and meet our legal obligations. RevenueCat's privacy policy: revenuecat.com/privacy.

6. Error Reports and Usage Statistics (PostHog), Only If You Agree

From Hazlo 1.6.3, Hazlo can send two kinds of information to PostHog, a service that collects error reports and usage statistics for apps: error reports, to find and fix failures, and usage statistics, to understand how Hazlo is used and improve it. Each one needs your consent, and you can accept or refuse each one separately.

When Hazlo asks. A new installation asks once, in the step right after the welcome screen. If you update from an earlier version, you see the question once, after What's New. You can answer "Share", "Don't share" or "Choose what to share", which shows one switch for each kind, both off. Until you answer, Hazlo does not set up PostHog's software and sends it nothing. If you choose "Don't share", nothing goes to PostHog. Hazlo works the same whatever you choose, and no feature, price or part of Hazlo Pro depends on your answer. If Apple indicates that a law requires a parent's or guardian's consent for a change like this (in Texas, for minors with a new account), Hazlo does not ask you and sends nothing, and it does not ask either until Apple has checked.

What is sent, and only for what you accepted:

  • Error reports:
    • when Hazlo crashes, a crash report: the parts of the app's code that were running, the code libraries that were loaded, the Hazlo and iOS versions and the device model. The crash message is removed;
    • errors that Hazlo detects and handles, as fixed codes: the part of the app, the operation, an error number and how many times it happened, with the parts of the app's code that were running and the code libraries that were loaded, as in a crash report. Never an error message or anything you wrote;
    • a launch that did not finish, for example because iOS closed Hazlo while it was opening its data.
  • Usage statistics, 16 kinds of events:
    • the app opening;
    • in the setup: each step you see, your answer when Hazlo offers to resume it, and when you finish it;
    • your answer to the notification permission;
    • the Hazlo Pro screen: what opened it, and how it closed, including whether a plan was bought and which kind;
    • reaching the free habit limit;
    • a habit created: where you created it (the habit form, the setup, a template, your plan or a routine), whether it is a yes/no or an amount habit, its kind of schedule (such as daily or a number of times a week, without the days or the number), whether it came from a template and whether it has a reminder. Never its name;
    • a habit checked in: what changed (done, undone or progress toward its goal) and how many at once, from where (the app, Siri, a reminder, Apple Watch, a widget or Control Center) and whether for today or an earlier day. Completions that come from Apple Health are never sent;
    • a habit archived or deleted, and whether it was to make room on the free plan;
    • a note or weekly reflection created, edited or deleted. Never its text;
    • the screen you open;
    • a link that opens Hazlo: which screen, and whether it came from a notification or another link;
    • Delete All Data.

    Each event also says whether you have Hazlo Pro, how many active habits you have as a range (0, 1, 2–4, or 5 or more), how many days have passed since you finished the setup (up to 365), whether notifications are allowed, which tab is on screen and whether you have ever logged a habit from a widget. Events carry only these fixed values and numbers, never text.

  • With either one: a random identifier created for this installation the first time you agree; the date and time of each event (for a crash report, rounded to the hour); the Hazlo version and build; the iOS version; the device model and type; your device's language; whether this copy came from the App Store or is a test version; the version of the question you answered; and the name and version of PostHog's software. Hazlo removes the time zone, the screen size, network details and session identifiers before sending.

What is never sent: the names of your habits, your notes and weekly reflections, the name in your profile, and any Apple Health data. The identifier is not your name, your email address, your Apple Account, your device's identifier for vendor, the advertising identifier or the identifier RevenueCat uses for purchases (section 5).

Who receives it, where and for how long. PostHog, Inc. (United States) processes this data on our behalf under a data processing agreement and stores it in its data centers in the European Union, in Frankfurt (Germany). PostHog and the companies it works with may access it from outside the EU, including from the United States: PostHog takes part in the EU–US Data Privacy Framework, and its agreement includes the European Commission's Standard Contractual Clauses. Your device's IP address reaches PostHog with each send, as it does with any online service; Hazlo asks PostHog not to work out a location from it, and PostHog discards it instead of storing it with the data. PostHog keeps the data for one year, the period of the plan Hazlo uses, which cannot be shortened.

Legal basis. Your consent (Article 6(1)(a) GDPR), given separately for each kind. You can withdraw it at any time; withdrawing it does not affect what was sent before.

How to change your mind. Settings › Privacy in Hazlo has one switch for "Error Reports" and another for "Usage Statistics". Turning one off stops that sending at once and deletes what was waiting on your device to be sent. Turning one on applies from that moment: nothing recorded while it was off is sent, not even a crash report from that time.

Your identifier. Settings › Privacy shows it; tap it to copy it. "Reset Identifier" gives what is sent from then on a new identifier; what was already sent keeps the previous one. If you turn both switches off and later share again, Hazlo also starts with a new identifier.

Deleting what was sent. Copy the identifier in Settings › Privacy and email it to [email protected] asking us to delete what was sent with it, and we will ask PostHog to delete it; in any case PostHog keeps it for one year. Without the identifier we cannot find that data, because nothing else connects it to you; before you reset the identifier, copy the old one if you want its data deleted. Delete All Data (Settings › Data Management) also erases your answer and the identifier from your device, so copy the identifier first if you want what was sent deleted too: Delete All Data does not delete what PostHog already has. If usage statistics are on, Hazlo reports that you deleted all data (the last event in the list above), and then sends nothing more to PostHog until you answer the question again.

No tracking across apps, nothing sold. This data travels with the random identifier, never with your name, email or account; because of that identifier, the App Store privacy label lists it as linked to you. Hazlo never combines it with RevenueCat's records, with Apple Ads or with data from other companies, never uses it for advertising and never sells it, and PostHog creates no profile of you. Hazlo does not ask for permission to track you because it does not track you.

Your record of consent. Your answer, when you gave it and the version of the question stay on your device, so your choice can be shown. They are not included in backups, and Delete All Data erases them.

If this changes. If what Hazlo sends, or why, changes, Hazlo asks you again in the app before sending anything new.

7. Notifications

Reminders are local notifications that iOS schedules and shows on your device. Hazlo does not use a push notification service or a server to send them. Depending on your settings, Hazlo can schedule habit and routine reminders, a daily reminder, a weekly summary, a weekly reflection reminder, a one-time reminder on your third day and, if you start a free trial of Hazlo Pro, a reminder two days before the trial ends. You can change them in Hazlo's settings or turn off notifications for Hazlo in the iOS Settings app.

8. Backups You Export

With Hazlo Pro you can export a backup: a JSON file with your habits, check-ins (including the daily totals that came from Health), categories, reminders, profile, badges, streak freezes and selected settings: appearance; notification configuration and custom text; Health-sync preference; onboarding and widget-use status; and view preferences. In versions through 1.4.1, the file also includes the notes on your check-ins; from Hazlo 1.5.0, it also includes your routines, your habit notes and the weekly reflections you write. Hazlo creates the file on your device and opens the iOS share sheet, and you decide where it goes, for example Files, AirDrop or email. The file is not encrypted, so anyone who has it can read it: keep it somewhere safe. Importing a backup replaces the data on your device with the data in the file. We never receive your backups.

9. Sharing and Emails to Us

  • If you tap Share on a milestone, streak or Year in Pixels card, Hazlo draws the image on your device and hands it to the iOS share sheet. It goes only where you send it.
  • If you email us at [email protected], for example with a question, a privacy-rights request or, from Hazlo 1.7.0, the report of an idea on the Ideas & Roadmap board (section 10), we receive your email address and your message. We use them only to reply, follow up, act on reports and improve Hazlo, keep them only as long as needed for that follow-up, and delete them sooner if you ask. Google receives these messages as our Google Workspace email provider and may process them in the United States under the EU–US Data Privacy Framework and, where applicable, the European Commission's Standard Contractual Clauses.

10. Ideas & Roadmap Board (Feedzzie)

From Hazlo 1.7.0, Ideas & Roadmap, in Settings › About and in Profile, opens a public board of ideas for Hazlo. You can read the ideas other people sent, vote for the ones you want and send your own, and so also see whether someone already suggested yours. It needs no account, name or email address. The board runs on Feedzzie (feedzzie.com), a service for app suggestion boards, which processes this data on our behalf. If Apple indicates that a law requires a parent's or guardian's consent for a change like this (in Texas, for minors with a new account), Hazlo hides the Ideas & Roadmap row in both places, and it also hides it until Apple has checked.

What is sent:

  • A random identifier. The board creates it on your device the first time it needs it and keeps it in your device's keychain, not in iCloud. It is not your name, your email address, your Apple Account or the identifiers in sections 5 and 6. The board sends it to find out which ideas you voted for, and with each vote and each idea you send.
  • Your votes: which idea you vote for, with your random identifier. Tapping the vote again removes it.
  • Your ideas: the title and the description you write, with your random identifier. The form does not ask for your name or your email address. While ideas you sent await our review, the board also asks Feedzzie whether we have reviewed them, in a separate request when it loads the list of ideas; that request carries the IDs of up to 20 of those ideas, but not your random identifier.
  • Without any identifier: when you open Settings, About or Profile, at most once every five minutes, Hazlo asks Feedzzie whether the board answers, so the row shows only when the board works; loading the list of ideas carries no identifier either.

Your device's IP address reaches Cloudflare and Feedzzie with each request, as it does with any online service. Cloudflare uses it to deliver the request and to stop abusive traffic, such as too many requests from one connection. Feedzzie uses it only to limit how many requests, votes and ideas can come from one connection, keeps it only while those limits last, a few hours at most, and does not store it with your votes or your ideas. Hazlo never gives the board your habits, your notes, your Health data or the name in your profile.

What becomes public. Nothing you send is public until we review it. Once we approve an idea, anyone who opens Hazlo's board can see its title and description, its status (such as "Under consideration" or "In progress") and how many votes it has; the board does not show who sent it or who voted for it. Each idea also carries a random reference to its author, different from your random identifier, so the board can hide the ideas of someone you block; it only shows that two ideas come from the same person. An idea we do not approve never becomes public.

Board rules. To send your first idea, you accept the board rules: zero tolerance for objectionable content and abusive users; nothing offensive, abusive or illegal, and no personal information. We review every idea before it is public, remove anything that breaks these rules and ban whoever sent it from the board. Your device keeps a record that you accepted them, with the version of the rules, and asks you again if they change.

Report and block. On each idea, you can:

  • Report it. The idea disappears from your board at once, and Hazlo prepares an email to [email protected] with the idea's title and ID, for you to send from your email account; if your device cannot send email, it shows our address and the idea's ID so you can write to us from any account. The report reaches us only if you send that email, and it gives us your email address and whatever you add, which we handle like any other email to us (section 9). We check reports every day and, within 24 hours of a report, remove the idea if it breaks the rules and ban from the board the random identifier that sent it, which can then no longer send ideas or vote.
  • Block its author. Every idea from that person disappears from your board. Blocking happens only on your device: nothing is sent to us or to Feedzzie, and the person is not told.

The ideas you reported and the authors you blocked are kept only on your device; you can show them all again with "Show hidden ideas", in the board's "Sort" menu.

Deleting an idea or your votes. To remove a vote, tap it again. To have an idea you sent deleted, published or not, email its title to [email protected] and we will delete it from Feedzzie, with everything stored with it; tell us if you also want the votes sent with the same random identifier deleted. Without an idea of yours we cannot find your votes, because nothing else connects them to you. Delete All Data (Settings › Data Management) does not erase the board's random identifier or anything Feedzzie has, and the random identifier may stay in the keychain even after you delete Hazlo; Hazlo then uses it again if you reinstall it.

Who receives it, where and for how long. Feedzzie's servers run on Google Cloud in Madrid (Spain), and Feedzzie stores the board's ideas and votes in a Supabase database in Ireland, in the European Union. Ideas, approved or not, and votes stay there while the board exists, until we delete them, for example because they break the rules or because you asked us to. Every request from the board reaches those servers through Cloudflare, Inc. (United States): Cloudflare's global network sits in front of them, delivers the requests and protects the servers from abuse. While a request passes through it, Cloudflare sees what the request carries, including your IP address, your random identifier, your votes and the text of your ideas, and it may process them outside the European Union, including in the United States. Cloudflare processes them on our behalf under its data processing agreement, which includes the European Commission's Standard Contractual Clauses, and takes part in the EU–US Data Privacy Framework. Cloudflare's data processing agreement: cloudflare.com/cloudflare-customer-dpa.

Legal basis. Providing the board you choose to use (Article 6(1)(b) GDPR) and our legitimate interest in knowing which ideas people want for Hazlo and in keeping the board free of abuse (Article 6(1)(f) GDPR).

No tracking, nothing sold. Hazlo never links the board's data with RevenueCat's or PostHog's records, never uses it for advertising and never sells it.

11. What Hazlo Does Not Do

  • No ads and no tracking prompt: Hazlo shows no ads, does not report ad installs (SKAdNetwork) and does not use App Tracking Transparency. Through Hazlo 1.5.0 it also did not request Apple's ad attribution token (AdServices); from Hazlo 1.5.1 it hands that token to RevenueCat, once per install (section 5), so an install from an Apple Ads ad can be tied to the campaign, ad group and keyword of that ad. The token is not linked to data from other companies and says nothing about your habits or your Health data.
  • No tracking across apps or websites. Hazlo never asks for permission to track you.
  • No analytics or crash reporting without your consent: from Hazlo 1.6.3, error reports and usage statistics go to PostHog only if you agree, and never include your habits' names, your notes or your Health data (section 6). RevenueCat's activity analytics are limited to the app opens described in section 5.
  • No access to your location, contacts, photos, camera or microphone.
  • We do not sell or rent your data.

12. Deleting Your Data

  • Settings → Data Management → Delete All Data permanently erases your habits, check-ins, categories, routines, reminders, profile, badges, streak freezes and reflections, and resets your preferences on this device. It also erases your answer about error reports and usage statistics and the identifier (section 6), but not what PostHog already received: to have that deleted, copy the identifier first and follow section 6. It does not erase the Ideas & Roadmap board's random identifier or anything Feedzzie has (section 10). Your Apple Watch empties too the next time it gets an update from your iPhone.
  • You can delete any habit, together with its check-ins and reminders, in the app.
  • Deleting Hazlo from your device, or from your Apple Watch, removes the data it stored there, except the Ideas & Roadmap board's random identifier, which may stay in your device's keychain (section 10).
  • Your purchases stay with Apple, and deleting the app or its data does not erase RevenueCat's records. RevenueCat keeps a record under a random identifier created on your device even if you never buy anything. That identifier is random: it is not your name, email or Apple Account, and Hazlo shows it in Settings › About as "Support ID" so you can give it to us. We can locate a record only if you give us that identifier or a purchase identifier, such as the order ID in Apple's receipt email; without either one, we cannot locate or delete it.
  • Deleting Hazlo or its data does not erase what PostHog already received with your consent; see section 6.
  • Deleting Hazlo or its data does not delete the ideas and votes you sent to the Ideas & Roadmap board; to have an idea deleted, see section 10.
  • Hazlo never changes or deletes anything in Apple Health.

13. Children's Privacy

Hazlo needs no account and has no chat, leaderboards or public profiles. From Hazlo 1.7.0, an idea sent to the Ideas & Roadmap board becomes public only after we review it, and the board rules forbid personal information: we do not publish an idea that includes any (section 10). We do not knowingly collect personal information from children. The third parties that may receive data are RevenueCat, for the data described in section 5; Google, our Google Workspace email provider, for any message sent to [email protected], whatever version of Hazlo someone uses: questions, privacy-rights requests and, from Hazlo 1.7.0, reports of ideas on the Ideas & Roadmap board (section 9); from Hazlo 1.6.3 and only with consent, PostHog, for the data described in section 6; and, from Hazlo 1.7.0, Feedzzie, for the ideas, votes and random identifier of the Ideas & Roadmap board, and Cloudflare, the network in front of Feedzzie's servers, which sees them and the IP address while they pass through it (section 10). Where Apple indicates that a law requires a parent's or guardian's consent for a significant change of an app (in Texas, for minors with a new Apple Account), Hazlo does not ask about error reports and usage statistics and sends none (section 6), and it hides the Ideas & Roadmap board (section 10).

14. Health Disclaimer

Hazlo is not a medical device. Habit tracking is for informational and motivational purposes only. Consult a healthcare professional for medical advice.

15. Your Rights by Jurisdiction

European Union / EEA (GDPR): Data controller: Mike Pulgar Olguin, individual developer, Spain. The data Hazlo keeps on your device (sections 2 and 4) stays under your control and we cannot access it: you can manage it in the app, and with Hazlo Pro you can export the subset that section 8 lists for your version of Hazlo. The personal data we process is the RevenueCat data in section 5, which RevenueCat processes on our behalf to operate purchases, provide Pro features and produce aggregate app-open and purchase analytics (performance of a contract, Article 6(1)(b) GDPR, and our legitimate interests in checking whether a device has Pro, showing current prices and understanding aggregate app-open activity and purchase performance and, from Hazlo 1.5.1, knowing which of our Apple Ads ads an install came from, Article 6(1)(f) GDPR), from Hazlo 1.7.0 the ideas, votes and random identifier you send to the Ideas & Roadmap board (section 10), which Feedzzie processes on our behalf to provide the board you choose to use (performance of a contract, Article 6(1)(b) GDPR) and for our legitimate interests in knowing which ideas people want for Hazlo and in keeping the board free of abuse (Article 6(1)(f) GDPR), and any email you send to [email protected] from any version of Hazlo: questions, privacy-rights requests and, from Hazlo 1.7.0, reports of ideas on the Ideas & Roadmap board (section 9), and, from Hazlo 1.6.3 and only if you agree, the error reports and usage statistics in section 6, which PostHog processes on our behalf on the basis of your consent (Article 6(1)(a) GDPR). You can withdraw it at any time in Settings › Privacy without affecting what was sent before. Google Workspace processes these emails as our email provider, with the safeguards for transfers to the United States described in section 9. We use them to answer you and follow up (our legitimate interest in answering messages, Article 6(1)(f) GDPR) and, for privacy-rights requests, to comply with our legal obligation to handle them (Article 6(1)(c) GDPR). We keep them only as long as needed to answer and follow up, and delete them sooner if you ask. You have the right to access, rectification, erasure, restriction, portability and objection, and to withdraw your consent at any time; to exercise them, contact [email protected]. You can also lodge a complaint with the supervisory authority: AEPD, C/ Jorge Juan 6, 28001 Madrid, Spain.

United Kingdom (UK GDPR): UK residents have the same rights as under the GDPR. Supervisory authority: ICO, Wycliffe House, Water Lane, Wilmslow, SK9 5AF, United Kingdom.

California, USA (CCPA/CPRA): We do not sell personal information and do not share it for cross-context behavioral advertising. We do not use sensitive personal information for any purpose other than providing the app.

Brazil (LGPD), Canada (PIPEDA), South Africa (POPIA), Japan (APPI): You have the rights these laws give you. You manage the data on your device directly in the app; for purchase data, for error reports and usage statistics and for what you sent to the Ideas & Roadmap board, contact us.

16. Changes to This Policy

If we change this policy, we will publish the new version on this page and update the date at the top. If what Hazlo sends to PostHog, or why, changes, Hazlo asks you again in the app before sending anything new.

17. Contact

If you have questions about this privacy policy or your data:

Developer: Mike Pulgar Olguin (individual developer), Spain.