Privacy Policy

1. Scope

This Privacy Policy applies to the Pearlie iOS and web applications (formerly Brother: AI Mentor for Men), supporting website, and backend services (together, “Pearlie,” “we,” “us,” or the “Service”).

2. Information we process

• Account information. If you sign in with Apple or Google, Firebase Authentication may process identifiers, email address, display name, authentication tokens, and sign-in metadata. If you continue without an account, Firebase may create an anonymous identifier.
• Profile and memory. Your name or nickname if you give one, age, the topic you pick, preferred support style, saved memories, theme, and related onboarding answers (profiles created before October 2026 may also include life situation, goals, pressures, and the people who count on you) are stored on your device. For Apple- or Google-signed-in users, this information is also included in a private account backup so it can be restored. Relevant profile context is sent with chat requests so replies can be personalized.
• Conversation notes. To keep replies consistent over time, Pearlie maintains a short set of notes drawn from your conversations — people you have mentioned, situations that are unresolved, things you said you would do, and advice already given. These notes are generated from your messages, stored on your device in protected storage, and included in the private account backup when you sign in with Apple or Google. Deleting Pearlie's memory or your account deletes them.
• Conversations. Your current message and a limited amount of recent chat context are sent to our backend and AI providers to generate a response.
• Screenshots. A screenshot is uploaded only when you choose to attach it. It may contain third-party messages or other personal information, so review it before sending. Original screenshot files stay in local chat history for a limited number of recent screenshot turns and are not included in account backup. A text summary of visible context may remain with the conversation so later replies can remember what was shown.
• Usage, attribution, and technical data. App analytics is a switch on the last onboarding step. It is preselected on, and you can turn it off there or anytime afterward in Settings. Nothing is sent to Firebase Analytics, AppsFlyer, Meta, Apple's attribution service, or our analytics service until you finish onboarding with the switch on. When enabled, Firebase Analytics and our first-party analytics service receive app events such as screens viewed, onboarding completion, settings use, message counts, response times, reply-length ranges, feedback taps, whether a screenshot was attached, and error types, together with the app version, operating-system version, device type, and a random installation ID. Firebase also collects its own app-instance identifier, device model, and approximate location derived from IP address. Our first-party analytics service also records whether a reply followed one of Pearlie's safety rules; that flag is not sent to Firebase or any other provider. First-party analytics events are not linked to your account. AppsFlyer receives privacy-limited install and campaign attribution data, app and operating-system details, device and network metadata, IP-derived approximate location, a non-advertising app/device identifier, and a small allowlist of product milestones such as onboarding completion and the third successful reply. Pearlie also uses Meta's iOS SDK to send Meta app activation and a separate Meta-prefixed allowlist of conversion milestones. Meta automatic events, automatic purchase logging, codeless events, SDK-managed SKAdNetwork reporting, and advertising-identifier collection are disabled. If you installed Pearlie from an Apple Ads campaign, Pearlie sends Apple's attribution token through our backend to Apple, which returns campaign, ad group, keyword, and country identifiers that may be attached to an analytics event. AppsFlyer may provide campaign attribution and allowlisted milestones to Meta and TikTok when their advertising integrations are enabled. Pearlie uses AppsFlyer's Strict iOS SDK and does not provide IDFA. On the web, only our first-party analytics service is used. Message text, Pearlie replies, profile answers, saved memory, names, email addresses, account or Firebase identifiers, and screenshot contents are not included in analytics or advertising-attribution events. Cloudflare, Firebase, Google, AppsFlyer, Meta, TikTok, and other infrastructure providers may process limited device, network, diagnostic, request, and campaign metadata.
• Optional conversation improvement. After five successful replies, Pearlie may separately ask whether you want to share future de-identified text conversations for internal response-quality review. Sharing remains off unless you affirmatively choose it. We do not attach your name, email address, Firebase or account identifier, profile answers, IP address, advertising identifier, or screenshot content to this research copy. Common contact and identity details in message text are automatically replaced where possible before storage, but free-form text can still contain personal or sensitive context. Screenshot turns and crisis or safety turns are excluded.
• Personal check-ins. When you choose a check-in time, Pearlie may generate a short follow-up from the conversation being processed. The schedule, notification wording, privacy-preview choice, and in-app opening are stored on your device and delivered using Apple’s local notification system. Pearlie does not operate a remote push-notification database for these check-ins.
• Contextual advertising. Contextual sponsored suggestions are not currently active, and Pearlie does not currently send chat context to an advertising provider for sponsor matching. If this feature is enabled later, this policy and the in-app disclosure will be updated before that sharing begins.

3. How information is used

We process information to authenticate users, personalize and provide conversations, analyze optional screenshots, maintain security, prevent abuse, diagnose failures, understand feature usage, and comply with law. When you separately opt in, de-identified conversation copies are reviewed internally to evaluate and improve Pearlie’s response quality, tone, safety boundaries, and reliability.

4. AI processing and permission

Before the first AI-generated reply, Pearlie asks for permission to send your messages to OpenAI, which generates the replies. If you do not continue, Pearlie does not send a chat request and cannot generate replies.

When permission is active, chat requests are routed through our backend to OpenAI. OpenAI may process your current message, a limited amount of recent conversation, relevant profile context (including your name, age, onboarding answers, goals, pressures, preferred tone, and saved conversation notes), approximate time context, and any screenshot you choose to attach solely to generate and maintain Pearlie's replies. We do not send your password, Apple or Google credentials, authentication token, or payment-card details to OpenAI.

5. Storage and retention

Pearlie stores your profile, saved memory, conversation notes, chat history, check-in schedule and wording, and notification preferences on your device. Guest conversations remain local and are removed when you delete Pearlie's memory or remove the app. If you sign in with Apple or Google, Pearlie stores a private account backup containing your profile, conversation notes, chat text, feedback, and text summaries of screenshot context on Cloudflare infrastructure so the conversation can be restored. Original screenshot image files and scheduled check-ins are not included in that backup. The backup remains until you delete Pearlie's memory or account. Optional de-identified conversation-improvement copies are kept for up to 90 days and are not connected to the account backup. Turning that sharing option off requests deletion using a random on-device deletion key. First-party analytics events are kept for up to 180 days. Service providers may process or retain request, security, diagnostic, authentication, analytics, advertising-attribution, or AI request data under their own retention rules. Using “Delete account” deletes the private account backup and Firebase sign-in account, then clears local Pearlie memory and chat history. Deleting only the app removes the local copy; a signed-in backup remains available for restoration.

6. When information is shared

We share information only as needed to operate the Service, including with Apple and Google for sign-in; Google Firebase for authentication and optional analytics; Cloudflare for backend delivery and security; OpenAI for reading attached screenshots and generating responses; AppsFlyer for optional privacy-limited install attribution and product milestones; Meta for direct privacy-limited app-event measurement and campaign measurement; and TikTok for campaign measurement when its advertising integration is enabled. AppsFlyer, Meta, and TikTok do not receive chat text, Pearlie replies, profile answers, saved memory, names, email addresses, account or Firebase identifiers, screenshots, or IDFA from Pearlie's analytics and attribution pipelines. Each provider is required to protect information under its applicable agreement and to use it only for the services described. We may also disclose information when required by law, to protect users or the Service, or as part of a business transfer. We do not sell your chat text or profile answers.

7. Your choices

• Choose whether to continue with AI processing by OpenAI before Pearlie sends its first chat request.
• Switch app analytics and privacy-limited campaign attribution off on the last onboarding step, before anything is sent, or anytime afterward in Pearlie’s Settings.
• After five successful replies, separately choose whether to share future de-identified text conversations for response-quality improvement. Choosing “Keep my chats private” leaves sharing off. Turning sharing off later stops future sharing and requests deletion of copies associated with the random deletion key stored on that device or browser.
• Turn personal check-ins and detailed lock-screen previews on or off, and cancel scheduled check-ins, in Pearlie’s Settings.
• Delete local and signed-in account memory from Settings. Deleting the iOS app or clearing this site's browser storage removes a guest's local memory; signed-in backups remain until deleted through Pearlie or a verified support request.
• Limit screenshot access by choosing only the image you want to share.
• Use Apple or Google account controls to manage information held by those providers.

8. Your privacy rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or object to certain processing, and to withdraw consent. Requests may be submitted using the developer support contact displayed on Pearlie’s App Store listing. We may need to verify your identity before completing a request.

9. Children

Pearlie is not directed to children under 13. If you are under the age of legal majority where you live, use the Service only with permission from a parent or legal guardian. If we learn that information from a child under 13 was collected without appropriate authorization, we will take reasonable steps to delete it.

10. Security and international processing

We use reasonable technical and organizational safeguards, but no online service is completely secure. Providers may process information in countries other than your own, where privacy laws may differ.

11. Changes and contact

We may update this policy as Pearlie changes. The effective date above will be revised when material updates are published. For privacy questions or requests, use the developer support contact on Pearlie’s App Store listing.