Privacy Policy

1. Information we process

• Account and sign-in informationName, app nickname, email address, account ID, the credentials and verification details you submit to sign in, and authentication/session information. If you use an account already linked to Telegram, it can also contain your Telegram ID, profile name and avatar.
• Tasks and productivity informationTask titles, descriptions, subtasks, dates, times, tags, repetition settings, completion history, streaks, challenge progress and focus-session durations or timer events used by the service.
• Social features and account benefitsFriend relationships and requests, shared challenges and their results, referral information, Axion and referral balances, rewards, and Premium entitlement or redemption records. Fledix does not store bank-card details; an external payment provider may process a purchase if you choose to use an available checkout.
• Preferences and local app stateLanguage, theme, onboarding choices, local tasks, timer state, cached account data and session tokens. These use the app's local storage.
• Technical and support informationWhen the app connects to a server, that server receives connection information such as an IP address and HTTP request details. Service errors and security records may be processed to operate and protect Fledix. If you contact support, we receive your email address and the information you choose to include.

Notes, shared tasks and files. Notes, shared-task assignments and chat messages, profile pictures, and files you choose to upload to shared tasks are processed by Fledix. Files may contain photos, video, audio or documents. Personal-task attachments are stored on your device; shared-task uploads are sent to the service and made available to the participants you share them with.

Firebase Analytics and Crashlytics. Native Android builds use Google Firebase for usage analytics and crash reporting. This can include app-instance/installation identifiers, device and operating-system information, app version, screen views, interactions such as task creation/completion and theme selection, focus-session duration, crash reports, stack traces and diagnostic information. Google Analytics may derive an approximate location from the connection IP address. We do not intentionally include task titles, descriptions, chat text, notes, attachments, email addresses or passwords in the custom analytics events. Advertising-ID and Android-ID collection and advertising-personalization signals are disabled in our Firebase configuration.

Calendar and notification features. Calendar access is optional and requested when you enable calendar integration. Selected events are displayed on your device; exporting tasks writes them to the calendar you choose, whose provider may synchronize them under its own settings. Local reminders use task information on the device. Push notifications use a registration token and relevant notification content through Expo and/or Google Firebase Cloud Messaging.

The app does not request your device contacts, microphone, camera or precise location. A system file picker gives access to files you select. Information you put into task text, uploaded files or support messages is processed as content you provide.

2. Why we use this information

We use the information to create and secure accounts, verify sign-ins, save and synchronize tasks, calculate progress, run focus and challenge features, manage friend and referral interactions, maintain account benefits, remember preferences, respond to support and deletion requests, and prevent misuse.

There is no advertising or advertising-profile feature in this version. Providing account information is necessary for account-based functions; you can continue using the available local features without signing in.

Usage analytics and diagnostic reports help us understand feature use, improve performance and investigate crashes. Push tokens enable delivery of relevant notifications. Optional file and calendar features operate when you choose to use them.

3. Local storage and the shared account

Guest tasks and preferences are stored on your device. Clearing the app's storage or uninstalling it removes the device-local copy. Account-based features send relevant data to the Fledix API over HTTPS for storage and synchronization. Local storage also keeps session tokens and cached data so the app can remember your session.

This is a separate Android installation, but it uses the same Fledix service and account as the web app and other Fledix clients. Changes to a shared account can therefore appear in those clients. Signing out or uninstalling this app does not delete the account or its server data.

4. Who receives information

• Other Fledix users: profile information used to find and identify you, friendship information, and information you share through friend challenges or other social features. Shared features can include task text, schedule, progress, results, participant messages and uploaded files.
• Service providers: cloud database services including Supabase, server-hosting providers, and providers that deliver account emails or handle support correspondence. They receive information needed to provide those services.
• Notification services: because accounts are shared, notifications already enabled for your account or its social features in other clients may continue to use Telegram or Expo/Google Firebase Cloud Messaging. Relevant delivery information and notification content can be sent to those services. Native Android builds register for push notifications when the feature is used; delivery tokens and relevant payloads are processed by Expo and/or Google Firebase Cloud Messaging.
• Google Firebase: Google processes analytics and diagnostic data as a service provider for Firebase Analytics and Crashlytics. See Firebase privacy information.
• Legal or security requests: information may be disclosed where required by applicable law or needed to address a specific security incident.

Cloud and communications providers may process information in a country different from yours. External services have their own privacy practices. Following an external link or sending support email also involves the service you choose to use.

5. Keeping and protecting information

Account information and synchronized content are kept while needed to provide your account and its features, until you remove the relevant content or request deletion. Local data stays on the device until it is cleared, replaced or the app is uninstalled.

We process verified account-deletion requests within 30 days. This covers the account and associated personal data, including tasks, progress and social/referral associations. Limited records may need to be retained where required by law or for a specific security or fraud investigation; if an exception applies, we explain the data involved, the reason and the applicable retention period in our response. Technical and support records are kept only as needed for the purposes described here.

App-to-API traffic uses HTTPS and account requests use access controls. No system can guarantee absolute security. Keep your password and verification codes private and avoid including sensitive information in task text or messages unless it is necessary.

6. Request account and data deletion

You can make a request without reinstalling or signing in to the app. Requests are handled by Fledix support, not by an automatic deletion button.

1. Email fledixsupport@gmail.com with the subject Fledix — account deletion request.
2. Tell us your app nickname and the email connected to the account. Send the request from that connected email where possible. Do not send your password, verification codes or payment-card details.
3. We confirm ownership of the account, then delete the account and its associated personal data within 30 days after confirmation, subject to any explained lawful retention exception.

The button opens your email application. Send the email to submit your request. If no mail app opens, copy fledixsupport@gmail.com into your email service.

Deletion affects your shared Fledix account across all Fledix clients. It is not limited to this test installation. It removes your account content and account benefits; signing out is not a substitute for deletion. You can also ask support to delete particular information without deleting the whole account. Data or messages independently saved by another person are not under our control.

In the Android app, open Settings → Request account deletion to reach these instructions. To remove only guest data, clear the app's storage in Android settings.

7. Your choices and requests

You can edit or delete tasks using the available app controls, update account information where supported, and contact fledixsupport@gmail.com to ask about access to, correction of, or deletion of your data. We may need to confirm your identity before acting on an account request.

If you believe a child has supplied personal data that should be removed, contact us. We do not ask for identity documents, passwords or one-time sign-in codes as part of the public deletion instructions.

8. This page and policy updates

This policy page does not contain app analytics or advertising scripts. The hosting service receives normal connection information when serving it. Email links open your chosen email service; they do not submit a request automatically.

We update this policy when relevant app features or data practices change and change the date at the top of the page. Questions about this policy can be sent to fledixsupport@gmail.com.