Privacy notice

Effective date: 29 October 2026

This notice describes the Becoming beta app and this website. For privacy questions, contact support@becomingapp.tech.

What Becoming collects

When you use the app, we process your account identifier and information provided by your sign-in provider, which may include your email address and name. We also store the name you choose, your selected identities and descriptions, journal entries (moments), suggested connections, and app preferences.

Signing in with Google requests basic identity information. Becoming does not request access to your Gmail messages, contacts, or Google Drive files. Sign in with Apple may use an Apple private relay email address.

Why we use this information

We use it to authenticate you, save and display your writing, suggest connections to your chosen identities, provide reminders you enable, respond to support requests, and understand whether the beta works reliably.

Journal processing with AI

Your journal text and relevant identity information are sent to Google Gemini to suggest identity connections. Your entry is saved before this processing begins. Suggestions may be inaccurate; they are not a clinical assessment or professional advice.

Google processes submitted content under the terms applicable to the configured Gemini API service. Data use and retention can differ between service tiers; this beta does not promise that AI providers never retain or use submitted content for service improvement. Avoid including sensitive information or information about others that you do not wish to submit to an AI service. See Google’s Gemini API terms.

Service providers and analytics

• Supabase provides account authentication, application data storage, and backend functions. The app’s Supabase projects are configured in Singapore.
• Google provides Google sign-in and Gemini-based interpretation. Apple provides Sign in with Apple when you choose that method.
• PostHog, when configured, receives limited product analytics such as app openings, sign-in outcomes, onboarding steps, screen names, and moment-save outcomes and duration. Before login, events use an SDK-generated identifier; after login, the Supabase account ID is used to associate activity across sessions and devices. We do not send journal text, identity descriptions, name, or email in these analytics events. Session replay is disabled.
• Website and email infrastructure serves these pages and forwards support email. Hosting and email providers may process network/security information and support message contents to deliver those services.

Some providers may process information outside Singapore. We do not sell your personal data.

This website

This static website does not contain a journal form, advertising trackers, or a site analytics script. Hosting infrastructure may process standard request data such as IP address, browser information, and security logs. Email links open your email application; messages you send become support correspondence.

Storage, retention, and deletion

Application data is kept so the service can provide your account and saved moments, unless you delete it or the beta service is discontinued. You can manage moments and identities in the app and delete your account in Profile. Account deletion removes associated application data; operational providers may retain backups, security logs, or other records according to their applicable policies. Analytics records and support correspondence may be retained separately.

See account deletion instructions. For requests about personal data or analytics records, email support; we may need to verify account ownership before acting.

Notifications and your choices

Weekly reminders are scheduled locally on your device and depend on notification permission. You can disable notifications in device settings. You can choose not to submit journal text and can stop using the beta at any time.

Security and beta limitations

We use authenticated requests, access controls, and encrypted network connections. No service can guarantee absolute security. Becoming is an early beta whose features may change; do not use it to store passwords, financial credentials, medical records, or emergency information.

Updates and contact

We may update this notice as the product changes. The effective date will identify the current version. Contact support@becomingapp.tech with questions.