Ease Privacy Policy

1. About this policy

Ease is operated by Merek Barrett in Ontario, Canada. Ease is responsible for the personal-information decisions described in this policy. Contact our support and privacy mailbox at support@helloease.app.

This policy covers the Ease iPhone app, helloease.app, our editorial services and support. Features and connected requests depend on your installed version, permissions and choices. Third-party websites you choose to open also handle information under their own policies.

2. Information you provide

Your app setup can include onboarding answers, a self-reported screen-time estimate and goal, motivations, a discovery-source answer, and an optional age in whole years. It also includes selected launcher apps, custom names, order, colours and other appearance settings, saved widgets, protection rules, schedules, sessions, intentions, check-ins and progress. This setup is stored in app or shared extension storage on your device.

The optional age is used locally for the timeline illustration. A confirmed answer below 13 also prevents continuing interactive use of Ease. This answer is self-declared: it is not verified age assurance or verification of a parent or guardian’s authority. Ease does not add your exact age or date of birth to onboarding analytics events. Current age records use whole years rather than a newly collected birth date. Older local records may contain birth-date fields until normalized and saved; device backups can contain older copies.

You do not need an Ease email-and-password account to use the consumer app or read the public blog. If you contact support, we receive your email address, message, attachments and related message metadata. Please remove unnecessary personal information from screenshots and do not send passwords or payment-card details.

3. Device features and permissions

Age access: the current iOS release asks Apple’s Declared Age Range service for an age range after the first Continue in onboarding and again before opening a social website inside Ease. It requests thresholds at 13, 16 and 18, rather than your date of birth. Apple handles its sharing interface and may provide an age band and information about applicable restrictions. Ease uses the response on your device to decide access. Ease does not save the returned age band or send it to our servers or analytics providers. Apple processes its service under its own privacy terms.

If sharing is declined, unavailable or cannot establish the required range, core onboarding can continue without treating the person as an adult, but social websites inside Ease remain closed. A recognized under-13 result stops interactive use of Ease. Social access is also withheld when the response includes restrictions the current implementation cannot satisfy. Existing installations may resume beyond the first onboarding page; social access still requires its own check. The check does not verify a parent’s agreement to our Terms or guarantee age-appropriate third-party content.

Screen Time: with your authorization, Apple’s selection system provides opaque app, category and website tokens for your chosen restrictions. Ease stores them locally and shares them with its protection extensions. DeviceActivity reports display measured activity through the iOS report extension. Ease does not add your actual Screen Time reports or private selection tokens to optional onboarding analytics events.

Calendar: Month view does not need access to your events. Upcoming events requests iOS full calendar access. Standalone Upcoming widgets read events from all calendars available under that permission; calendar features with a calendar selector read the selected calendars. Local/shared caches may contain event identifiers, titles and times. Ease does not create or edit your events. Calendar-account synchronization follows your iOS and account settings.

Weather: city search sends queries to Apple MapKit. Forecast requests send the selected place’s coordinates to Apple WeatherKit; forecast data, freshness information and attribution can be cached locally. If you choose Use My Location where offered, Ease requests iOS location permission for that action. Requested location accuracy does not guarantee that coordinates are rounded. Ease does not use this feature for continuous location tracking.

App catalog: app search and lookup send your search term, storefront or relevant app identifier to Apple’s App Store services. App metadata and artwork may be cached locally, and artwork requests can reach Apple’s delivery infrastructure. These public catalog requests are separate from Screen Time selection tokens.

Wallpaper, Shortcuts and notifications: saving a wallpaper can request add-only Photos access or open a share destination you choose; it does not require reading your photo library. Shortcuts handoffs are local iOS actions. Local notifications and Live Activities can display session details, an app name or an intention on iOS surfaces, including the Lock Screen, according to your settings. Copies you export or share are controlled separately from Ease’s local storage.

5. Paused onboarding analytics and install measurement

Onboarding analytics is paused in the current iOS release. There is no onboarding analytics opt-in in this version, and it does not send optional onboarding views or answers to Google Analytics for Firebase. A sharing choice saved by an earlier version does not override this pause.

Earlier configured versions could offer optional onboarding analytics to adults aged 18 and older. Those records could include approved setup steps, broad time-spent and confirmed answer categories, timestamps, a Firebase app-instance or installation identifier, and SDK technical information. They were pseudonymous, not guaranteed anonymous. Exact age or birth date, free text, selected-app identifiers, measured Screen Time reports or tokens, credentials and social content were excluded from those onboarding events.

Pausing new collection does not delete earlier provider or reporting records. The retention and rights-request sections explain how to ask about those records.

Purchase verification and RevenueCat’s purchase, subscription and hosted-paywall reporting are separate and can still operate while Firebase analytics is paused. The age check does not delay every necessary service until an age response is shared. If optional onboarding analytics is offered again, Ease will provide updated information and any required permission before it begins; neither an illustration age nor an Apple age response enables it automatically.

Some app versions include install measurement through Apple’s SKAdNetwork. In those versions, Ease tells iOS that the app has launched, using a fixed install-baseline conversion value. Apple’s system decides whether an eligible ad impression and installation qualify for an attribution report. Earlier app versions may not include this measurement.

iOS can send an Apple-signed, privacy-limited attribution report to the ad network responsible for an eligible ad, such as Meta for a Meta campaign. Reports can include app and campaign/source identifiers, a report transaction identifier used for deduplication, redownload information and other fields permitted by the applicable system version and privacy threshold. These are campaign reports rather than an Ease user or device profile. Reports can be delayed, have limited fields, or be unavailable; an app launch or a successful API call does not establish an attributed install or receipt by Meta.

This Apple route records only a fixed install baseline. It does not report trials, subscriptions, purchase amounts, revenue, onboarding answers, selected apps or Screen Time information. Ease does not construct a Meta app-event payload, create a marketing identifier, read IDFA or IDFV, or create a person-to-campaign activity history for this route. Apple manages the system attribution process; Ease does not operate a server endpoint to receive copies of these reports.

Where included in an install-measurement update, Meta’s software library remains inactive, with Meta app-event collection off. The library is not initialized or used to create a Meta SDK installation identifier or report installs, app opens, sessions or purchases. Including the library does not establish that Meta received an event or that an ad campaign is eligible. Any later activation of direct Meta measurement requires a separate review, updated information and the applicable consent and Apple tracking permission before it starts.

6. Crash reporting and earlier versions

Firebase Crashlytics crash-report uploads are not enabled in this release.

Earlier versions or configurations may have sent Firebase screen or feature events, onboarding records, permission outcomes, setup counts, acquisition categories, paywall interactions, purchase/restoration outcomes or crash reports. Those records could use installation identifiers, and earlier configurations could associate Firebase and RevenueCat identifiers or send acquisition attributes.

Turning a service off or installing a new version does not erase information already held by a provider, previously queued SDK attributes or authorized reporting copies. Contact us about an applicable request concerning earlier records. RevenueCat purchase, subscription and hosted-paywall reporting is separate from optional onboarding analytics.

7. Purchases and paid access

RevenueCat supports retrieving products and paywalls, verifying purchases, recognizing eligible access and restoring transactions. Apple and RevenueCat process a customer identifier, product and transaction information, entitlement state and related dates. RevenueCat also provides purchase, subscription and hosted-paywall reporting to Ease.

RevenueCat’s hosted paywall records views, close actions and supported control interactions, together with the purchase-service customer identifier, a paywall session identifier and relevant offering, product, time, locale and design information. Which details are recorded depends on the paywall and interaction. This reporting is separate from Firebase product analytics and can operate while Firebase analytics is off.

RevenueCat can generate an anonymous App User ID without an Ease account. “Anonymous” is the provider’s identifier type; the transactions associated with it can still be linked and are not guaranteed anonymous personal data. Ease disables RevenueCat’s automatic advertising/device-identifier collection option and does not attach onboarding answers or new Firebase identifiers to that customer in this release configuration.

The purchase SDK also exchanges technical service information, such as app, SDK and operating-system versions, storefront, language/currency and purchase-related configuration. It can send the device’s identifier for vendor (IDFV) and its existing App Tracking Transparency authorization status independently of automatic attribution-identifier collection. Those are distinct from Apple’s advertising identifier (IDFA).

Apple handles payment credentials. Ease does not receive your Apple Account password or full payment-card number through its purchase flow. Necessary purchase processing is separate from optional product analytics; changing an optional analytics preference does not stop transaction verification or cancel a subscription.

Ease does not request App Tracking Transparency permission or integrate Singular in this release, and does not collect IDFA. A tracking status retained from an earlier version is not new permission for onboarding analytics.

8. Website, editorial tools and technical information

Visiting helloease.app sends request information, such as IP address, requested resource, time and browser headers, to our hosting and delivery providers. These requests deliver pages, protect services and help investigate technical problems. Essential editor-session storage is separate from optional visitor analytics.

The website and public blog use Vercel hosting and Payload CMS. Neon Postgres and Vercel Blob support the database and media setup. Authorized editors have separate administration accounts with email, password hashes, session and login-security records; those are not consumer app accounts. Drafts, review decisions, publishing history, media and operational records are administrative information.

Editorial automation can send approved product facts, editorial text, public research and aggregate Search Console query or page metrics to OpenAI to help prepare blog drafts for human review. We do not supply app users’ private onboarding records, Screen Time reports, calendar events, social passwords or purchase histories to that editorial workflow.

Search Console reporting concerns aggregate search discovery, such as queries, pages, country and device category. It is not proof of an individual reader’s app installation or purchase. Optional website analytics is not configured. Browser controls on the website do not control native app measurement, third-party websites or essential infrastructure logs.

9. Why we use information and applicable legal bases

We use local setup and requested connected-service information to provide the features you choose, purchase information to recognize and restore eligible access, support correspondence to respond to you, and limited technical information to operate and secure the service.

Where a law requires us to identify a legal basis, necessary service and purchase processing relies on performing our agreement with you or taking requested steps before it. Optional onboarding analytics relies on your consent. Security and support administration may rely on legitimate interests where available and the relevant safeguards apply. We also comply with legal obligations for records we must keep. Hosted-paywall interaction reporting is described separately from transaction verification.

In Canada, the form of consent depends on the purpose, sensitivity, reasonable expectations and applicable law. We do not treat a privacy notice, Terms acceptance or a legitimate-interest assessment as a substitute for any separately required consent or device-access permission.

We use optional onboarding information to understand and improve setup and the paywall. That choice does not authorize advertising targeting, cross-company tracking, a RevenueCat-linked answer history or materially different marketing reuse. We do not make solely automated decisions with legal or similarly significant effects based on onboarding answers.

10. Who receives information

Only the information relevant to the feature or service is provided to the recipients described here. Not every provider receives every category.

Ease does not sell your personal information or share it for cross-context behavioural advertising, meaning advertising based on your activity across unrelated companies’ websites or apps. We do not use onboarding answers to target advertising. We disclose information to the providers and independent services described below to deliver Ease, process purchases and provide support. Earlier configured versions could also send optional onboarding analytics with the applicable sharing choice; that collection is paused in the current iOS release.

Apple provides the Declared Age Range service, iOS permissions and Screen Time services, App Store transactions, public app lookup, MapKit and WeatherKit. EventKit reads the on-device calendar store; separate calendar synchronization follows your account settings.
For the Apple aggregate install-measurement route described above, Apple’s system manages install attribution and sends qualifying privacy-limited reports to the relevant ad network, including Meta for its campaigns. Ease may view aggregate campaign results from that network. This route does not send Meta SDK app events or create an Ease-held user-level advertising history. The included, inactive Meta library is separate from Apple’s system reporting.
RevenueCat supports products and paywalls, purchase validation, customer entitlements and restoration. It also supports purchase, subscription and hosted-paywall interaction reporting, with the technical service metadata described above. This release sends no new Firebase association or custom discovery/link attributes. Older customer attributes or reporting copies are not automatically deleted by that restriction. Ease does not attach an onboarding-answer history to this customer.
Google/Firebase may hold analytics or diagnostic records from earlier configured versions, including SDK identifiers and technical or service events. The current iOS release does not send the optional onboarding analytics described above. A new version or local preference does not automatically erase earlier records.
Vercel, Neon and Vercel Blob support the website, editorial database and media operations described above. Website hosting, media and editor-account storage have different roles; one database’s region does not establish where every network log or backup is kept.
OpenAI receives the selected editorial/research inputs described above, not the private app datasets excluded from that workflow.
Ease’s owner reporting tools can hold authorized aggregate analytics reports and customer-keyed subscription or attribution reports from separately configured services. These reporting copies have their own access, retention and rights handling. This release does not add customer-level onboarding-answer joins to them.
An email provider handles support correspondence. Social websites and destinations you choose receive the requests or exports you direct to them and handle information under their own policies.
Authorized people working on Ease may access necessary support, service or aggregate reporting records. Information may also be disclosed when required by law or to address a valid legal process, limited to what is appropriate under applicable law.

11. Your choices

Optional onboarding analytics is paused in the current iOS release, and a saved sharing choice cannot enable it. Pausing collection cannot recall an earlier request already in flight or erase records already received by a provider.

An illustration answer, agreement to the Terms, an Apple age response or purchase approval does not itself authorize optional analytics. Local setup, iOS permissions and purchase verification have their own controls. If a later version offers optional sharing, it must provide the applicable information and choice before collecting it.

You can contact support@helloease.app about an objection, withdrawal, access or deletion request. Withdrawing consent affects future processing and does not make earlier lawful processing unlawful. Changing a sharing preference does not cancel a subscription.

Local controls do not remove every SDK diagnostic file, earlier provider record or independent website record. A materially different marketing, tracking or measurement purpose requires appropriate information and any required permission before it begins.

The Apple system install-measurement route adds no onboarding consent screen or App Tracking Transparency request solely for that nontracking attribution. The included Meta library remains inactive and provides no Meta app-event sharing choice in this configuration. Neither route enables optional Firebase analytics or authorizes individual tracking. Other features and providers retain their own permission and privacy requirements. Before a materially different measurement or tracking method is introduced, Ease must provide the applicable information and any required choice.

12. Retention and deletion

Local setup generally remains until you change or reset it, subject to app cache behavior, iOS storage management and device backups. Reset Ease completes only after the required cleanup checks for its supported local scope succeed. That scope covers local setup, rules, sessions/progress, onboarding information, saved designs and covered website/cache storage. If a required cleanup fails, Ease reports that the reset could not finish; some earlier data may already be cleared, and you can retry.

The Apple age response is assessed in memory; Ease does not retain the returned age band in its saved setup. A restriction derived from an Apple under-13 response lasts for the current app process. A confirmed optional illustration answer is stored separately and can restrict access again after a restart. Social entry requires a new check rather than treating a past sharing result as a permanent grant.

Reset Ease does not revoke iOS permissions, cancel subscriptions or erase remote provider records. It preserves an older optional sharing choice while clearing the local information covered by Reset; that choice cannot enable analytics while the current pause applies. Resetting a local analytics identifier is not remote erasure and does not prove every SDK diagnostic file has been removed.

RevenueCat’s SDK-local purchase identity, customer-information cache and hosted-paywall event queue are outside Ease’s local Reset scope, as are remote Apple and RevenueCat records. Clearing Ease setup does not delete that purchase-service customer. Restore and subscription management have separate controls.

Optional analytics and authorized reporting copies are retained for the time needed to understand and improve setup, address reliability or support issues, meet applicable legal duties and handle rights requests. Provider data, restricted backups and earlier records can have different retention processes. Changing a preference or a cache freshness timestamp does not delete every earlier copy.

Purchase and entitlement records, support cases, security logs, editorial and owner-reporting records, and legally required records have separate retention purposes. They are kept for the period needed to provide the service, resolve the matter, meet legal duties or establish, exercise or defend legal claims, with deletion or restriction when no longer needed. A cache freshness timestamp is not a deletion period for every storage copy.

Infrastructure logs, restricted backups and independent-provider copies follow their applicable retention and deletion processes. Removing active data is not a promise that every deleted storage block or backup has been physically erased at the same moment. Restricted copies must not be returned to ordinary use without applying applicable expiration and deletion requirements.

Deleting a saved widget design does not remove its iOS Home Screen placement. Exported Photos, wallpaper, shared files and Shortcuts have separate controls. Apple, social providers and other independent services retain their own records under their applicable policies and obligations.

For the Apple install-measurement route, Ease keeps no new persistent marketing identifier, per-person campaign history or copy of individual attribution reports. The included, inactive Meta library is not used to create a new Meta SDK installation identifier or app-event queue. Apple manages its system attribution state, and Apple and the receiving ad network handle their service records under their applicable policies. Reset Ease does not retract reports already sent by iOS or promise to reset Apple’s attribution windows. We do not create an identity link to locate an individual within aggregate campaign results, and a local reset is not proof of provider-side deletion. Earlier provider records, if any, retain their separate rights and retention processes.

13. Privacy rights and requests

Depending on the law that applies, you may have rights to access or receive a copy, correct information, request deletion or portability, withdraw consent, object to or restrict processing, and complain to a privacy regulator. Applicable law may also provide authorized-agent requests, appeals, particular marketing choices and protection against unlawful discrimination for exercising rights. Conditions and exceptions vary.

Email support@helloease.app in ordinary language. We may ask for information reasonably needed to locate the records and verify your authority. We do not routinely require government ID, and you should not email passwords or unnecessary sensitive documents.

The consumer app has no email account that maps every provider identifier to you. Some information exists only on your device, while purchase, support or website records have different lookup details. We will explain relevant lookup limits rather than create an unnecessary identity link solely to identify you. We may retain records where the law permits or requires it and explain the reason when applicable. See our Privacy Requests guide.

14. Children and teenagers

Ease is intended for people aged 13 and older. People under 13 are not permitted to use Ease. Users under 18 need a parent or legal guardian’s agreement and supervision under our Terms.

Apple’s age-range check supports access decisions; it does not establish a parent or guardian’s agreement and supervision under our Terms. A result that cannot establish the required range does not count as an adult result. Social services have their own age and account rules, and the check does not make all third-party content suitable for teenagers. Optional onboarding analytics is paused in the current iOS release; an age response does not turn it on.

If you believe a child has provided personal information to Ease, or you are a parent or guardian seeking to exercise an applicable right, contact support@helloease.app. We will assess the request, verify authority proportionately and take the steps required by applicable law.

15. International processing and security

Ease operates from Canada. Connected services can process or access information in other countries, including the United States. The location of a website database does not establish the location of every support message, service log, subprocessor or backup.

Where applicable law requires safeguards for an international transfer, the relevant transfer must use an available lawful mechanism and required safeguards. Contact us for information about applicable recipients and safeguards. We do not promise Canadian-only storage.

We use platform storage protections, service authorization and access controls appropriate to the information and service. Administrative passwords are stored as hashes rather than readable passwords. No electronic system is risk-free, and we cannot guarantee absolute security. Please protect your device and accounts and contact us about a suspected security problem.

16. Additional information by location

Canada: applicable federal and provincial law governs meaningful consent, access, correction and complaints. Contact us first about a concern, or consult the Office of the Privacy Commissioner of Canada or the relevant provincial authority.

EEA and United Kingdom: where applicable, you may exercise the GDPR-related rights described above and complain to the supervisory authority where you live, work or believe an infringement occurred. This includes the UK ICO and Ireland’s Data Protection Commission. A non-consent basis for personal-data processing does not remove a separate requirement for consent to device access.

United States, Australia and New Zealand: privacy rights and complaint routes depend on the law that applies to the service and the circumstances. We will assess a request under that law rather than require you to hold a consumer account. This policy does not waive mandatory local rights.

17. Updates and contact

The effective date appears at the top of this policy. Material changes to purposes, recipients or controls will receive appropriate notice and any consent required by law before the changed processing begins.

For privacy questions, requests or complaints, contact support@helloease.app.