Privacy Policy

Effective date: September 23, 2026 · Last updated: September 23, 2026

Cristobal Jones (FiuFiu Labs), an independent developer based in Chile.

This Privacy Policy explains how FiuFiu handles personal data in its mobile app and at https://fiufiuapp.com. It covers accounts, alarms, wake-up challenges, sleep information, subscriptions and the community feature board. It also explains your choices and how to contact us. Optional permissions are separate from accepting our Terms and Conditions.

1. Who is responsible for your data

Cristobal Jones is responsible for the personal data described in this policy, acting as the data controller where that term applies. Registration details: Individual developer operating in Chile; no incorporated company.

For privacy questions or requests, email privacy@fiufiuapp.com. The FiuFiu privacy team at that address is our designated privacy contact and privacy officer where local law requires one. FiuFiu is intended for users aged 16 and over in the countries where it is offered. Local privacy rights and additional protections for younger users still apply.

2. Information you provide and account records

The app's main service requires an account. We receive information from you, your device, your chosen sign-in provider and the stores and providers that support the features you use.

• Email registration supplies your email address and a password, which our authentication system stores as a hash. Verification and account emails are delivered through Resend.
• Sign in with Apple supplies the name and email Apple shares, which may be a private relay address. Google sign-in supplies your name, email and profile-picture link.
• Authentication creates session records that may include an IP address and device or browser description. Sessions have a rolling one-year expiry and may renew while you remain active. Signing out or deleting the account ends access through the affected sessions.
• The app creates a random device identifier to distinguish devices sending sync data. It is not an advertising identifier or hardware serial number.
• We keep your permission choices, including analytics and optional Apple refund-use sharing, so we can apply and record them.
• If you contact support or make a privacy request, we receive your contact details, message and any attachments or diagnostic information you choose to send. Avoid including passwords or unnecessary personal information.

3. Alarms, progress and data that syncs

We store account-linked records to save your settings and support sync:

• Alarm times, labels, sounds, repeat days, chosen challenges and app-blocking settings.
• Wake schedules, bedtime settings, sleep goals and schedule exceptions.
• Wake sessions, including when an alarm fired, when it ended, its outcome, challenge types, attempt times and failure counts.
• Streaks and completion dates.
• Setup answers, including selected habits, text entered in the other-habit field, preferred challenges and times, language, app version and completion time.
• Personal photo-mission references, including a name, emoji, numeric image descriptor and optional descriptive labels, or a barcode's type and value. The reference image itself is not uploaded for sync.

Your wake-up challenge photos, recordings and raw sensor readings are not part of these cloud-sync records. Community photos are handled separately under section 5.

4. Device permissions and local processing

Apple Health

On iPhone, with your permission, FiuFiu reads sleep information from Apple Health to display sleep summaries. Health readings stay on your phone and are not uploaded to our backend or analytics. FiuFiu does not write to Apple Health. We do not sell Health data or use it for advertising. Morning mood check-ins also stay on your phone and are not uploaded.

Camera and motion

Photo and barcode challenges use the camera. Supported photo recognition and movement verification run on the device. Movement challenges may use camera, motion or step-sensor readings. We do not receive wake-up challenge photos, video, audio or raw movement readings; challenge outcomes and reference descriptors may sync as described in section 3.

Choosing to take and upload a photo for a community proposal is a separate action. That photo leaves the device and is stored for the community feature.

App blocking and notifications

On iPhone, app blocking uses Screen Time permissions. The selection of apps to block remains under the device's Screen Time system; our alarm records sync whether blocking is enabled, not a list of selected apps or browsing history. Feature availability differs by platform.

Alarm notifications are scheduled locally. The app does not collect remote push-notification tokens. FiuFiu does not request access to your contacts, location or photo library for its current features.

You can change permissions in your device settings. Withdrawing a permission stops the related access and may make a feature unavailable. It does not delete data you already submitted, such as community uploads or synced reference descriptors.

5. Community submissions and safety review

The feature board stores your display name, proposals, comments, votes, uploaded photos and related timestamps. It also stores reports, block relationships and human moderation decisions. Reports and block relationships are private to the moderation process.

New display names, posts, comments and uploaded photos require review and approval by our team before they appear to other signed-in community members. Bug reports remain private to their author and our team. We review reports ourselves and may remove content or restrict accounts. A report alone does not remove content or suspend an account. We do not send community content to OpenAI.

Do not submit personal information about yourself or others. Other members may copy content they can view, and we cannot control copies made outside FiuFiu. Our community rules explain reporting, blocking and appeals.

OpenAI screening has been retired. This stops new transfers; it does not undo earlier processing. Any records from earlier processing remain subject to the applicable retention and deletion terms. Contact us about historical processing or deletion requests.

6. Subscriptions and refunds

Apple or Google handles payment; RevenueCat helps manage subscription access. We do not receive your full card or bank details. We process the plan, product, store, trial or billing-period type, subscription status, renewal or expiry dates, transaction identifiers, purchase events, cancellations and refunds. We also keep Stop Alarm balances and transactions and the allowance information needed for snoozing.

A store-provided identifier links purchases to the relevant FiuFiu account. It is not your store email. We keep records needed to resolve purchase ownership and subscription transfers. RevenueCat uses your FiuFiu account identifier, or an anonymous identifier before sign-in.

We currently do not send Stop Alarm usage information or refund recommendations to Apple for refund review. We still process store refund notifications to update purchase access and balances. Apple's refund decision remains its own.

7. Optional analytics and technical requests

If you allow analytics, the app sends selected usage events to PostHog to help us understand which features people use and where problems occur. You can allow or decline during setup and change your choice in Settings. Before you decide, FiuFiu temporarily holds limited usage events in memory on your device. These events are sent to PostHog only if you allow analytics. Choosing “No thanks” discards them. Declining does not remove access to other features.

Events use a restricted set of properties, such as event name, app version, platform and app environment. They do not contain your email, free-text setup answers, Health data, community content or exact sleep schedule. Before sign-in they use a random identifier; after sign-in they use your account identifier. This allows us to associate activity and count returning users. Session replay and automatic crash capture are disabled.

The analytics payload replaces the IP field with zeros and disables location lookup. Network providers still receive the technical connection information needed to handle a request; this is separate from the properties saved in analytics events. Product analytics currently operates on iPhone and uses PostHog's EU endpoint. Withdrawing permission stops new events. Account deletion requests removal of linked analytics records.

The backend also sends a small number of operational signals to PostHog, such as processing health and failure counts. These describe the service and do not carry an account identifier. We do not run advertising in the app or use personal data for targeted advertising.

The website consists of static pages without account forms, advertising cookies or product analytics. Its fonts and assets are served with the site. Vercel receives request information such as IP address, browser description, requested page and time to deliver and protect the website. Expo receives technical request information to deliver compatible app updates. Following an external link sends you to a service with its own privacy practices.

8. Why we process data

Where a law requires a lawful basis, we distinguish the purpose of processing:

• Providing the service under our agreement with you, including account access, alarm and progress sync, subscription verification and the community features you request.
• Your consent for optional product analytics and optional Apple refund-use sharing. Device permissions control access to Health, camera and motion features.
• Our legitimate interests in protecting accounts, reviewing community safety, investigating abuse, responding to support requests and maintaining the service, balanced against your rights.
• Legal obligations where we must keep transaction records, handle legally required requests or disclose information under applicable law.

You may withdraw consent without affecting the lawfulness of processing already carried out. Accepting the terms is not blanket consent to optional processing.

We do not sell personal data or share it for cross-context behavioural advertising. We do not make decisions with legal or similarly significant effects solely through automated processing.

9. Who receives data and international processing

We use providers for the specific tasks below:

• Convex: backend, database, authentication storage and community uploads.
• RevenueCat: subscriptions, purchase records and access management.
• Resend: verification and account emails.
• PostHog: optional product analytics and backend operational signals.
• Vercel: website delivery and hosting.
• Expo: app-update delivery.

Apple and Google also handle sign-in, store payments and distribution under their own terms and privacy policies. Published community content is shared with signed-in members as described in section 5. We may disclose relevant records when legally required or necessary to protect users, investigate fraud or establish or defend legal claims, subject to applicable law. We do not give providers permission through this policy to use your data for unrelated advertising.

Convex and our other service providers use US hosting; PostHog analytics uses EU hosting. Hosting location does not establish where every support operation or subprocessor processes data.

We operate FiuFiu from Chile, so support and administration access happens from Chile. Each provider processes data on our documented instructions under its data-processing terms and publishes its own list of subprocessors. To request a copy of the safeguards that apply to a transfer, email privacy@fiufiuapp.com.

10. Retention and deletion

We keep data only as long as the purposes above require, subject to the periods below and any legal retention requirement:

• Account settings, alarms, schedules, progress and reference descriptors: until you delete your account.
• Sign-in sessions: expire after one year without use. Account deletion removes authentication records immediately.
• Community profile, proposals, comments, votes, uploaded photos, reports and block relationships: until removed through the service or moderation, or until account deletion.
• Analytics events (PostHog): removed when you delete your account. Otherwise no longer than the retention period of our PostHog plan, currently seven years. Withdrawing analytics consent stops collection but does not by itself erase earlier events.
• Moderation records in the app: until the related content or account is deleted.
• Support email correspondence: up to two years after the case is closed.
• Purchase and refund records, transaction identifiers, Stop Alarm transaction history and subscription ownership and transfer records: until you delete your account, then normally 180 days from your deletion request to handle refunds, disputes and payment reconciliation, then deleted. If account deletion or deletion by a provider remains unresolved, we retain these financial records and the minimal deletion record beyond that period until the outstanding steps are resolved. There is no fixed maximum for this hold. Once those steps are resolved and the 180-day period has passed, our automated cleanup deletes the retained records. Apple and Google keep their own purchase records under their policies. Our payout reports from Apple and Google contain no account identifiers.
• Account deletion record: normally 180 days from your deletion request, subject to the same unresolved-deletion hold described above. It holds only what is needed to prevent deleted data from being recreated and track outstanding deletion steps.
• Store notification and account-transfer audit logs: six months.
• Provider copies: Convex backups are kept for up to 14 days. Website and update-delivery logs are kept for short periods set by Vercel and Expo. Historical OpenAI processing is addressed in section 5.

Deleting your account removes your synced records and community profile, proposals and their discussion threads, comments, votes, uploaded photos, reports and block relationships. A minimal deletion record prevents deleted data from being recreated. The in-app flow also clears local account data and cancels app alarms.

Apple and Google retain store records under their own policies. Deleting your FiuFiu account does not cancel a store subscription. See account deletion for the steps and cancel billing separately in the store.

11. Your rights and choices

Depending on the law that applies, you may request access, a copy of your data, correction, deletion, restriction or blocking of processing or portability. You may also object to processing based on legitimate interests and withdraw optional consent. Some rights have exceptions, including when a record must be retained by law.

Email privacy@fiufiuapp.com, preferably from your account address. If you no longer have access to it, tell us so we can arrange another reasonable identity check. We may need limited information to verify a request or a representative's authority. We aim to acknowledge requests within two business days and respond within the deadline required by the applicable law. If an extension is legally permitted and needed, we will explain why and when to expect a response.

You can also use the app's account deletion and permission controls or your device's privacy settings. Signing out stops account sync on that device but does not delete stored account data. Changing a device permission does not cancel a subscription.

You may also complain to the privacy regulator in your country where one exists. You do not have to contact us first.

Where US state privacy laws apply, eligible residents may exercise the applicable access, correction, deletion, portability and appeal rights. Contact the privacy address to appeal a denied request or submit an authorised-agent request. We do not sell or share data for targeted advertising, so we do not use your data for those activities. We will not penalise you for exercising a legally protected privacy right. Withdrawing information necessary for a requested feature can prevent us from providing that feature.

12. Children and younger users

FiuFiu's minimum age is 16. Children under 16 must not create an account or submit personal data. If you believe a child under 16 has provided information, contact us so we can investigate and delete it as appropriate.

Users under the age of majority must have a parent or guardian's permission under our terms. In countries where consent to an online service requires parental authorisation above age 16, that higher local threshold applies to processing based on consent. A general agreement to the terms does not replace any legally required parental-consent process.

13. Security

We use encrypted connections, authenticated account access and permissions that restrict access to account records. Service providers support storage and security controls. No system can guarantee complete security. Protect your sign-in details and contact support if you suspect unauthorised access. We will make any breach notifications required by applicable law.

14. Changes and contact

We update the date on this page when we change the policy. For material changes, we will notify you in the app or by email as appropriate, before new processing begins where required. If a new purpose requires consent, we will request it separately.

Contact privacy@fiufiuapp.com. FiuFiu is not currently offered in the European Economic Area, the United Kingdom or Switzerland.