Pefu Privacy Policy
Last updated: 24 October 2026 · Android and iOS identifier: com.pefu.main
Core routines work on your device without an account. Optional family connection, purchases and notifications use the services explained below.
Who provides Pefu
Pefu is provided by Caner Şahan, based in The Netherlands, who is responsible for Pefu’s handling of personal data. For privacy questions, access, correction or deletion requests, contact canersahan@gmail.com. This policy covers the Pefu app and these Pefu web pages.
Local routines and backups
The app stores a child’s nickname, age, language choices, companion, routines, custom activity text, calendar, progress, stars, badges and screen-time agreements on the device. Core use needs no account. Local routines and progress are not automatically uploaded.
A parent can export a file backup and choose where to save or share it. A file backup is separate from family synchronization. Copies on other devices or in your chosen backup location are under your control.
Optional family connection
Parents may sign in by email and pair parent phones or a child device. Supabase processes parent email, authentication and session identifiers, family membership, device labels and device permissions for this service. Resend delivers parent sign-in emails from noreply@pefu.canersahan.com and processes the recipient email address, authentication email content and delivery information for that purpose. The sending domain is configured in Ireland with encrypted delivery required; open and click tracking are not enabled. Child profiles and routine content are not included in authentication emails. A child device uses an anonymous authentication identifier and a parent-authorized invitation; no child email is required.
Only when a parent explicitly chooses to share progress does Pefu send the selected child profile, routines, calendar, progress and family screen-time records to its Supabase service in Ireland. Authorized family members can then access shared information. Creating a family alone does not publish the local child profile. We use this information to provide synchronization, shared requests, decisions and family access controls.
Optional external calendar subscriptions
In the parent area, a parent can explicitly create a private calendar link for selected shared activities. Anyone holding that link can read the selected event titles, dates and durations. Adding it to Apple Calendar, Google Calendar or another calendar service shares those events with that provider, which may retain its own copies. The feed excludes the child’s name, age, routine steps, progress, stars and screen-time records. Avoid putting identifying or sensitive information in event titles.
Each parent has a separate revocable link. Creating a replacement invalidates the old link. Revoking a link, removing that parent from the family, deleting the family or expiry of Family access stops new access. Previously downloaded copies are not remotely erased. Refresh timing is controlled by the calendar provider and may be delayed; this is a read-only subscription, with editing in Pefu.
Purchases and shared Pro
Google Play handles Android payments and Apple handles App Store payments; Pefu does not receive full payment-card details. On-device purchase services connect after a parent approves the optional purchase connection. RevenueCat processes store purchase records, a random app purchase identifier and technical device information to verify and restore access. This approval does not itself make a purchase. Optional family Pro verification associates a parent’s account identifier with that purchase identity. Child routine text, calendar and progress are not sent to RevenueCat.
A verified one-time Pro purchase is separate from the optional monthly Family subscription. Valid Pro access can remain shared within the connected family when monthly synchronization ends. Refunds, revoked purchases or leaving/removal from a family can affect shared access. Backups do not grant purchased rights.
Notifications
If you allow notifications, Pefu processes device push tokens, request identifiers and notification dispatch/delivery information through Supabase, Expo Push Service, Google Firebase Cloud Messaging on Android and Apple Push Notification service (APNs) on iOS. This supports family request and decision notifications. Permission can be declined or revoked in device settings. Family requests can also be checked in the app. This policy will be updated when additional platform services are introduced.
Voice recordings and biometric protection
Prepared narration consists of bundled AI-generated recordings played offline. Pefu does not send your custom activity text to a voice-generation service. Fingerprint or face verification is performed by the operating system. Pefu receives an authentication result, not biometric images or templates.
Advertising, analytics and website access
The current app version has no advertising-network SDK and no behavioral analytics or tracking SDK. The Pefu pages on this website do not add advertising or analytics scripts, tracking cookies, or an embedded third-party video player. Azure hosts these pages and may process ordinary connection information, such as IP address and request metadata, to deliver and secure the website. Following links to the wider portfolio or other websites may involve their own services.
We do not sell children’s personal data or use it for behavioral advertising. Any future advertising integration requires an updated policy, store disclosures and child-appropriate configuration before release.
Children and parents
Pefu is a parent-configured routine companion for children. Parents manage optional accounts, family invitations, sharing and purchases. Please use a nickname rather than unnecessary identifying information, and do not place sensitive personal information in custom activities or calendar notes. Contact us if you believe information was shared without the parent’s authorization.
Security, service providers and international processing
Online connections use HTTPS, and the family service checks membership and roles before allowing access. Device biometric protection and secure storage protect selected credentials and access checks. Local routine storage and the full family service are not described as end-to-end encrypted.
Providers include Supabase for optional authentication/database services, Resend for parent authentication email delivery, RevenueCat for purchase verification, Expo, Google and Apple for push delivery, Google Play and Apple for payments, your chosen calendar provider when you add an external subscription, and Microsoft Azure for this website. They may process data in countries outside your country. Ireland hosting of Pefu’s database or email sending does not mean every provider processes data exclusively in the EU. Where required, processing is covered by the providers’ applicable data-protection and international-transfer arrangements. See Supabase, Resend, RevenueCat, Expo, Google, Apple and Microsoft.
Retention and deletion
The parent area’s Family connection screen offers Delete family account with a separate explicit confirmation. This removes the parent’s sign-in identity, membership, push registration and associated purchase-service customer profile. An owner’s deletion also removes the shared family cloud space and disconnects its members. Local records remain. Minimal opaque account-closure identifiers prevent old session tokens being reused; necessary historical transaction/security records may remain without the removed sign-in contact details.
Local records remain until removed through app or device controls. Signing out or ending a subscription does not erase them. Exported backups and copies held on other family devices require separate removal.
Optional family cloud records are kept while the family uses the service, until the owner deletes the family or a verified deletion request is fulfilled. An owner can delete the family’s cloud profile, invitations and permission records from Family connection; other members can leave. These actions alone do not delete the parent’s authentication account.
To delete your parent account and associated cloud data, use the account deletion request page. We verify ownership, remove the Pefu account and associated data from active systems, and coordinate deletion of associated identifiers with relevant processors. We may need to keep limited information when legally required or necessary for security, fraud prevention or a dispute; any applicable exception and retention period will be explained in response. Provider backups and security logs follow their retention schedules rather than disappearing immediately with a live-record deletion.
Deleting an owner account can remove the shared family space and disconnect its members. Store transaction records may be retained by the store for its legal obligations. A deletion request does not cancel a store subscription; you can manage subscriptions separately in Google Play. Cancellation is not a prerequisite for requesting deletion.
Your privacy rights and contact
Depending on your location, you may request access, correction, deletion or a copy of personal data, and object to or restrict certain processing. Parents can withdraw optional sharing and notification permissions. We handle requests without undue delay and within applicable legal time limits. You may also contact your local data-protection authority. To exercise your rights, email canersahan@gmail.com; do not send passwords, app PINs, recovery keys, payment-card details or unnecessary information about a child.
Changes
We update this policy when Pefu’s actual data handling changes. The date above identifies the current version. Material changes to optional data use will be explained in the app where required.