Privacy Policy

Scope and provider

This policy covers the Dialee Android app, cloud services, and public support pages. Dialee is provided by the developer identified on its Google Play listing and is intended for adults aged 18 or older. We do not knowingly offer the service to anyone under 18. Privacy questions may be sent to gml5453@gmail.com.

Information Dialee handles

• Account and profile: account identifier, email, display name, authentication provider, and optional personalization focus.
• Phone contacts: contact identifiers, names, and phone numbers available after Contacts permission. Granted phonebook contacts are cached on the device for matching. Only contacts with Dialee memory are intended to sync.
• Your content: notes, summaries, talking points, tasks, reminders, dates, recaps, AI questions, preferences, and settings.
• Relationship context: validated non-sensitive facts such as stated interests, preferences, relationships, role, organization, email, or address. Local filters are designed to reject sensitive categories, but automated filters are not perfect.
• Call-companion metadata: call-related signal type and time, phone or contact match, direction, source phone package, and companion state. Dialee does not request historical call logs or retain unrelated notification text.
• Explicit voice recap: audio you deliberately record, duration and size, returned transcript, and usage information. This is not call audio.
• Subscription: entitlement, product, billing period, purchase and expiration times, renewal state, and management information supplied by Google Play and RevenueCat. Dialee does not receive full card details.
• Service and security: authentication events, request success or failure, provider and model, quota and usage, estimated service cost, account activity time, and content-minimized technical errors.
• Private feedback (optional): if you use Settings → Help & feedback, the category (problem or suggestion), your message, whether you allow an email reply, the app version, your account identifier, and up to three images you choose yourself. Images are resized and re-encoded as JPEG on your device and again on our server, which removes embedded metadata, but they still show whatever is visible in the image, so avoid other people's private details. Dialee never attaches notes, contacts, logs, recordings, or screenshots automatically.
• Error reports (builds that include them): a JavaScript error report containing the app version and build, release channel, timestamp, a random event identifier, and code file, line, and column positions. Dialee discards error text, names, breadcrumbs, request URLs, device and account identifiers, and the content of your notes, contacts, tasks, and recaps before sending. Native crashes are not collected. Our error-reporting provider, Sentry (United States), necessarily receives the network connection and may derive an approximate location from it; we have blocked IP storage and enabled server-side location scrubbing. A fresh verification event contained neither a stored IP address nor location fields. Sentry still processes the network connection when receiving a report.

Permissions and special access

Depending on features you choose, Dialee may request Contacts, Notifications, Notification Access, Phone state, Microphone, Display over other apps, system biometric or device credential, foreground service, boot completion, and alarm access. Notification Access inspects fields from allowlisted Phone and Truecaller packages in memory to identify call signals. System authentication protects selected call-time notes without giving Dialee your fingerprint, face template, PIN, pattern, or password.

The stock Phone app always controls answer, decline, mute, speaker, keypad, emergency behavior, audio routing, and hang-up. Dialee does not use Accessibility to infer calls and does not replace your dialer.

Local and cloud storage

Dialee keeps an app-sandboxed SQLite cache containing phonebook contacts, Dialee content, recaps, validated relationship context, pending local jobs, settings, usage caches, search index, and sync queue. Android backup is disabled. Uninstalling ordinarily removes device data but does not delete cloud data or cancel a subscription.

After sign-in, Supabase provides authentication, synchronization, database storage, and server functions. Cloud records can include profile, contacts with Dialee memory, phone mappings, notes, tasks, recaps, validated context, entitlement, quota, and activity information. Access controls are designed to scope synchronized records to their owner.

Optional AI and transcription

When you consent and request an AI feature, Dialee sends relevant content and context to a Supabase server function. This may include your question or recap, selected notes or relationship context, contact name, phone scope, dates, and timezone. Text AI requests may be sent directly to OpenAI or through OpenRouter to model providers including OpenAI and Anthropic. Explicit voice recaps may be sent to Google for Gemini transcription, with OpenAI and OpenRouter-routed transcription providers as fallbacks. Model providers and routing may change.

Dialee does not persist submitted recap audio in its database; it returns the transcript and stores limited usage metadata. Providers may process request data under their own terms. AI can be inaccurate; review outputs before saving or acting and do not rely on Dialee for professional or high-impact decisions.

Purposes and legal bases

We use information to create and secure accounts, synchronize requested features, show saved caller context, provide requested AI and transcription, administer subscriptions and limits, respond to support and privacy requests, prevent abuse, diagnose failures, comply with law, and enforce the Terms. Where applicable, processing relies on our agreement, consent, legitimate service and security interests, or legal obligations.

Service providers and international processing

Dialee uses Google for sign-in, Android, Play Billing, and Gemini voice transcription; Supabase for authentication, database, sync, and server functions; RevenueCat for subscription status; Sentry for privacy-filtered error reports; OpenRouter and its model providers for text AI and fallback transcription; OpenAI directly for AI and fallback transcription; and an email provider only when configured for account service notices. Feedback does not trigger an automatic email: it is stored privately in Supabase and read by staff there. If you allow a reply, staff may look up your account email to respond. We do not sell personal information or use Dialee content for third-party advertising. Providers may process data outside your country under applicable safeguards and their terms.

Retention

Active-account information is retained while needed to provide Dialee or until deleted, subject to legal, security, fraud-prevention, dispute, and backup requirements. Private feedback, including any images, is readable only by Dialee staff through the Supabase dashboard, is deleted 90 days after submission, and is deleted when you delete your account. Error reports are retained by Sentry under its project retention settings. Dialee contains code for a 335-day warning and 365-day deletion of eligible inactive accounts without a paid entitlement, but that automation is not relied upon until its trusted schedule and email delivery are operationally configured.

Deletion and subscriptions

Delete through Settings → Account → Permanently delete account, or use the public deletion instructions after uninstalling. The in-app flow removes the authenticated cloud account and owner-scoped cloud records and clears local data on the device completing the flow. An offline device may retain local data until reconnection or uninstall. Account deletion does not cancel Google Play subscriptions.

Your choices and rights

Depending on your location, you may have rights to access, correct, delete, restrict, object, receive a copy, withdraw consent, or complain to an authority. Dialee does not currently offer automated export. Email gml5453@gmail.com from the account address. We may verify identity. We aim to acknowledge requests within 48 hours.

Security

Safeguards include HTTPS, secure device session storage, server authentication and access controls, request limits, disabled Android backups, and system authentication for optional call privacy. No system is completely secure. The local database is protected by Android's app sandbox and is not described as end-to-end encrypted.

Changes and contact

Updates will show a new effective date, with additional notice where law requires. Questions and complaints: gml5453@gmail.com. Governing location: India, subject to mandatory protections where you live.