PRIVACY POLICY (UNITED STATES) — LIBFY
Last Updated: 27/10/2026
This Privacy Policy describes how Libfy collects, uses, discloses, and protects personal information when you use the Libfy mobile application and related services.
1. Company Information
Controller / Business: LIB Social Present
Address: 4444 W Point Loma Blvd Unit 84 San Diego, California 92107-1030 United States
Privacy Contact: customerservice@libfyapp.com
2. Scope
This Privacy Policy applies to personal information processed through the Service in the United States, including information collected through the app, customer support, and related websites or pages we operate.
3. Age Notice (Not for Children Under 13)
The Service is not directed to children under the age of 13, and we do not knowingly collect personal information from children under 13.
If you are under 13, do not use the Service and do not provide personal information to us.
If we become aware that we have collected personal information from a child under 13, we will take reasonable steps to delete that information.
Note: We do not ask users to provide their age during account sign-up. If you believe a child under 13 is using the Service, please contact us at customerservice@libfyapp.com so we can investigate and take appropriate action.
4. Categories of Personal Information We Process
4.1 Account and Identification Data
•	Phone number used to sign in
•	User identifier associated with the account (e.g., Firebase Authentication UID)
• Preferred language and registration date to adapt communications and manage the account
Purposes: account creation, authentication, essential Service operation, security, and abuse prevention.
4.2 Profile Data
•	Nickname / display name
•	Optional profile image, stored in Firebase Storage and referenced via a download URL
•	Update timestamp associated with the account or its status
Purposes: profile personalization and display in social features.
Important: If you upload a profile image, avoid using images that include sensitive information. Depending on configuration, the file may be accessible via a link.
4.3 Social Connections / Status Data
Stored in our database and linked to your authenticated account:
•	Connection status / sharing status
•	Status description and lists of followed contacts and followers
•	Last update timestamps
Purposes: enabling social and interaction features in the Service.
4.4 True Social Mode Events and Session Statistics
Stored events include title, description, user-entered place, category, organizer, participants and invitees, dates, schedules and recurrence, and invitation and participation statuses. Event information, profiles and responses are displayed to people linked to the event through event and invitation screens.
For True Social Mode statistics, the app sends user, event or block identifiers, title and description, category, frequency, start, end, time zone and session completion outcome to the Service. Family Mode has its own records and statistics described in Section 4.6. These records describe Libfy features rather than a general history of other apps' use.
Purposes: organizing events, coordinating participation, and displaying disconnection and shared-time history and statistics.
4.5 Technical Operation Information
The app maintains local recovery states and generates operation and error diagnostic messages, which may include account, family, agreement or session identifiers. These operational records are separate from the session participation statistics described in Sections 4.4 and 4.6.
Purposes: operation, recovery and troubleshooting.
4.6 Family Mode: Families, Agreements, and Sessions
Information stored by the Service:
• Family and member identifiers, family name and optional image, creator, roles, membership status, and creation, joining, and update dates. Family images are uploaded to Firebase Storage and referenced by a URL.
• Invitations: family, sender and recipient, pending/accepted/declined status, and sending and response dates. Invitations may include snapshots of the family name and image and the sender's display name and avatar for presentation.
• Agreements: title, description or purpose entered by users, family, creator, proposed participants, acceptances, declines, departures, status, and dates. Creating an agreement records its creator's acceptance; others must respond. Changing its title or description makes the other participants' responses pending again.
• Sessions: family, agreement, session and participant identifiers; initiator; expected, active, joined and declined participants; requested, scheduled and actual start, joining, leaving and end times; disconnection and shared participation durations and totals. These records coordinate sessions across devices and provide history and statistics by participant, agreement and family.
Information visible or shared:
• Members can see the family name and image, members' display names and avatars, and invitation statuses presented in the member list. Invitees receive the family and sender information needed to decide whether to join.
• Access to each agreement's information depends on participation: accepted participants and pending invitees may consult it under the visibility rules. Accessible agreements display their title, purpose, creator, participants, responses and individual shared-time statistics. Session screens show active participants and avatars. Users are not shown individual statistics from agreements they cannot access.
• Time from inaccessible agreements may contribute to the family's overall total without revealing individual details from those agreements. Family membership alone does not grant access to every agreement's details or individual statistics.
• Participation may update the account's social status to indicate a Family block, visible through contacts and favorites features. Visibility of this status is not necessarily limited to the family.
Local storage and temporary use:
• The device retains the active session, pending invitations, decisions, activation schedules and pending leave or synchronization operations to recover after app closure or network interruptions. Some of this information persists locally until the operation is resolved, rather than being held only in memory.
• The app temporarily processes remote status information to verify membership, agreement acceptance and participation before activating or recovering a session. A session invitation lets you join or decline; if it remains pending, the app may join you automatically at the scheduled start, subject to verification and device availability.
Purposes: providing Family Mode, managing invitations and agreements, coordinating blocking and shared sessions, recovering interrupted operations, and displaying session history and statistics.
Family membership and the creator role do not verify legal guardianship or replace any authorization required for minors or device permissions.
4.7 Firebase Analytics
Libfy does not currently use Firebase Analytics, including on iOS, and does not collect information through this service.
4.8 Diagnostics and Stability (Firebase Crashlytics)
On iOS, we use crash reporting and diagnostics to detect incidents, fix bugs, and improve stability. We do not use Crashlytics for advertising or advertising tracking.
5. Contacts (Address Book) — Only If You Enable It
The Service accesses your device contacts only when you use the corresponding feature and grant the necessary device permission. It checks for matches only with people who already use Libfy and whose phone numbers are in your address book, to help you connect and send invitations. Libfy does not automatically query or synchronize your address book in the background.
•	Contacts are read on the device.
•	To check matches, the app may transmit phone numbers to backend services over encrypted connections (HTTPS).
•	We do not store your entire address book as a persistent “contacts database.”
• You can withdraw this permission at any time in your device settings.
• Results are presented in the requesting user's app; profile and status information may also be visible to others through the social features described in this Policy. Matching supports selecting contacts for event or family invitations, which create their own shared records.
• Normalized numbers and matching results are temporarily kept in memory to reuse the query. Local address-book names are not sent in that matching request.
Purpose: facilitating user connections.
Device permission is a technical authorization to access contacts. Granting it does not, by itself, establish legally valid consent to personal information processing or constitute consent from the people listed in your address book.
6. Local Processing and Device Permissions
The Android app processes launchable apps locally (name, icon and package identifier) to configure and apply blocking. Selected apps, blocking profiles and personal PQB session history are stored on the device. This local history is separate from Family and True Social Mode session records synchronized with the Service.
• Accessibility: you must explicitly enable the service in Android settings. Window events, foreground apps and system interface elements, including identifiers and labels needed to recognize screens such as Home or Recents, are processed on the device to apply blocking and prevent bypassing it during a session.
• Access to other apps' notifications (optional): allows local postponement of notifications from blocked apps in PQB. Notification identifiers, source apps, categories, groups and ongoing service attributes are used to preserve exceptions. Libfy does not copy or store notification text; Android manages the postponed originals.
• Do Not Disturb access: manages silencing during blocking modes. This is separate from permission to display Libfy notifications and access to other apps' notifications.
• Image selection: the image you select for your profile or family is uploaded to the Service for that feature.
• Background operation, battery and autostart settings: support scheduled activation and session recovery, including after device restart, depending on Android and the manufacturer.
You can manage these permissions and special access settings on your device. Denying or withdrawing access may prevent dependent features from working.
The current Android version does not request health, location or Bluetooth permissions for these features. A place voluntarily entered in an event is stored as event information; this does not obtain the device's location.
On iOS, Libfy does not store general Screen Time / device usage metrics, health data, precise location data or nearby device Bluetooth information as persistent server-side user data. If related features exist and are used, processing is performed locally and governed by system permissions. General device usage is separate from the Libfy session records and statistics described in Sections 4.4 and 4.6.
7. Notifications (Firebase Cloud Messaging)
We use Firebase Cloud Messaging for operational/service notifications. An installation token is associated with the account to route messages and may be updated.
Notifications include family invitations, agreement proposals and changes, session invitations and end notices, as well as event and social status alerts. Messages may carry identifiers to open a family, agreement or session, presentation information and expiry dates. Pending invitations and decisions may be stored locally for recovery. Depending on system settings, family or agreement names and other notice information may appear on the lock screen.
We do not use notifications for behavioral advertising. Turning off notification display does not decline a session invitation or leave an agreement.
You can control notifications in your device settings.
8. How We Use Personal Information
We use personal information to:
•	Provide, operate, and maintain the Service
•	Authenticate users and secure accounts
•	Enable requested social features and interactions
•	Provide customer support and respond to requests
•	Monitor, debug, and improve performance and stability
•	Prevent fraud, abuse, and unauthorized access
•	Comply with legal obligations and enforce our Terms
9. Service Providers and Sharing
We may share personal information with service providers that help us operate the Service. These providers process information on our behalf and under instructions.
9.1 Technology Providers (Firebase/Google)
We use Firebase services (Google) for core app infrastructure and features, including:
•	Firebase Authentication
•	Firestore Database
•	Firebase Functions
•	Firebase Cloud Messaging
•	Firebase Storage
•	Firebase Crashlytics (iOS)
Recipients also include users who see information through contacts, events and Family Mode, as described in Sections 4 and 5.
9.2 Legal and Safety
We may disclose information if we believe it is reasonably necessary to:
•	Comply with law, regulation, legal process, or governmental request
•	Protect the rights, safety, and security of users, the public, or Libfy
•	Detect, prevent, or address fraud, security, or technical issues
9.3 Business Transfers
If we are involved in a merger, acquisition, reorganization, financing, bankruptcy, or sale of assets, personal information may be transferred as part of that transaction.
9.4 Aggregated / De-identified Information
We do not currently share aggregated or de-identified user information with third parties for purposes separate from operating the Service. Any future changes to these practices will be reflected in this Privacy Policy, and we will provide additional notice or choices where required by applicable law.
10. Selling / Sharing for Targeted Advertising
We do not sell personal information.
We do not share personal information for cross-context behavioral advertising (targeted advertising) as those terms may be defined under certain U.S. state privacy laws. If our practices change, we will update this Privacy Policy and provide any required choices.
11. Data Retention and Account Deletion
We retain personal information for as long as needed to provide the Service and for legitimate business purposes such as security, dispute resolution, and compliance.
Account deletion requests: The app lets you submit a request associated with your account and the name provided, and records the request and its date. Under Libfy's operational policy, valid account deletion requests will be processed within a maximum of 48 hours of receipt. Associated personal information will be deleted, except where retention is legally justified. This time limit is an operational commitment by Libfy. Submission confirmation acknowledges the request, not that deletion has already been completed. Contact customerservice@libfyapp.com for the status of a request or to exercise your rights.
Shared family records may be retained in anonymized form where appropriate, provided they do not allow the deleted user to be identified.
Leaving a session, agreement or family changes participation and access; it does not submit an account deletion request or automatically delete shared historical records. Account deletion is processed as described above.
Operational retention: Some service providers may maintain limited logs or backups for operational resilience for a limited period. We do not control provider backup retention schedules, but we take reasonable steps to align our settings and practices with data minimization.
Retention criteria are described further in Section 13.7. The 48-hour commitment above concerns valid account deletion requests; other privacy requests are subject to the response periods required by the law applicable to the request, as explained in Section 12.
12. Your Privacy Choices and Requests
Depending on where you live and applicable law, you may have rights to:
•	Access the personal information we hold about you
•	Request deletion of your personal information
•	Correct inaccurate personal information
•	Obtain a portable copy of certain information
•	Opt out of certain processing where required by law
How to submit a request:
Email us at customerservice@libfyapp.com with your request.
To protect your account, we may need to verify your identity (for example, by confirming control of the phone number associated with the account).
These rights apply only where provided by applicable law and subject to its conditions and exceptions. You can submit requests by email; this Policy does not imply that each right has a separate in-app control. Privacy requests other than valid account deletion requests will be handled within the response periods required by applicable law, including any legally permitted extensions and required notices. Those periods do not extend Libfy's operational commitment to process valid account deletion requests within a maximum of 48 hours of receipt under Section 11.
13. U.S. State Privacy Disclosures (Including California)
Some U.S. state privacy laws, including California law, require additional disclosures when their applicability criteria are met. This section summarizes the practices described elsewhere in this Policy; it does not establish that Libfy is necessarily subject to the California Consumer Privacy Act (CCPA) or every other state privacy law. Any state-specific rights apply where the relevant law applies.
13.1 Categories of Personal Information Collected
We process the following categories as described in Sections 4 and 6; information described as local remains on the device for those functions:
•	Identifiers (e.g., phone number, account identifiers)
•	Activity in the Service (event invitations, agreement responses and session participation)
•	Device information (device/OS, app version) and diagnostics (crash logs and performance data) for the iOS stability features described in Section 4.8
•	Technical operation and error information as described in Section 4.5
• Profile information and family, invitation, agreement, event, participation and session statistics records as described in Section 4
13.2 Purposes
We collect and use these categories for the purposes described in Section 8.
13.3 Sale / Sharing
We do not sell personal information and we do not share it for cross-context behavioral advertising.
13.4 Non-discrimination
We will not discriminate against you for exercising applicable privacy rights.
13.5 Categories of Sources
The categories in Section 13.1 come from the following sources, as described in Sections 4 through 7:
• Information you provide when using the Service, including your phone number, profile name and selected image, family names and images, agreement content, event details and responses to invitations.
• Other users' actions in shared features, including invitations, proposed agreement participation and session activity involving your account. Their visibility is limited as described in Section 4.6.
• Your device contacts, if you enable access. Contacts are read locally, and phone numbers are transmitted for matching as described in Section 5; local address-book names are not sent in that request.
• Information generated when the app and Service operate, including account, family, agreement and session identifiers, participation states, dates, durations and the installation token used for notifications. Local-only processing remains subject to the distinctions in Sections 4 and 6.
• App and device information processed through the iOS crash reporting features described in Section 4.8.
13.6 Categories of Recipients
Information is processed by the Firebase/Google service providers listed in Section 9.1 for the functions described in this Policy, including the iOS stability service.
Other users receive information through contacts, events, invitations and Family Mode only within the visibility described in Sections 4 and 5. Family membership alone does not provide access to individual statistics from every agreement; inaccessible agreements may contribute to the family total without exposing their individual details.
Sections 9.2 and 9.3 describe possible disclosures for legal or safety reasons and in a business transfer. Those conditional disclosures are separate from routine feature sharing. As described in Section 9.4, we do not currently share aggregated or de-identified user information with third parties for purposes separate from operating the Service.
13.7 Retention Criteria
For the categories in Section 13.1, retention depends on whether the information is still needed to maintain the account, provide the requested feature, coordinate or recover a pending operation, or display the session history and statistics described in this Policy. Legally justified retention may also depend on applicable obligations, security needs or unresolved disputes, as described in Section 11. These criteria do not establish a fixed retention period or justify retaining every category for the same duration.
The valid account deletion process, its maximum 48-hour processing commitment, the exception for legally justified retention and any anonymized retention of shared family records are governed by Section 11. Any such anonymized records must not allow the deleted user to be identified. Local device records and provider operational retention remain subject to the distinctions in Sections 6 and 11.
14. Security
We implement reasonable administrative, technical, and organizational safeguards designed to protect personal information (including encryption in transit and access controls). No system is 100% secure, and we cannot guarantee absolute security.
15. International Processing
We and our service providers may process and store personal information in the United States and other countries where providers operate. Data protection laws may differ from those in your state.
16. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. We will publish the updated version and revise the “Last Updated” date. We will provide additional notices or obtain consent to changes when required by applicable law. Continuing to use the Service does not, by itself, constitute consent to new or changed personal information processing where such consent is legally required.
17. Contact Us
For privacy questions or requests:
LIB Social Present
4444 W Point Loma Blvd Unit 84 San Diego, California 92107-1030 United States
Email: customerservice@libfyapp.com