This policy explains how Feathly: Smart Planner handles your data.
Official language notice: This English version is the controlling version of this policy. Translations are provided for convenience and reference only. If a translation differs from this English version, the English version prevails.
Local-first by design: Feathly: Smart Planner stores your Loop and planner content on your device during normal planner use. Planner content is not uploaded to Feathly servers unless a future optional cloud/server feature is introduced and you choose to use it, or you deliberately submit information through support or a Closed Test feedback channel. If your app version includes optional Usage Analytics and you choose to enable it, limited app-usage and technical data may be sent to Google Analytics for Firebase, but Loop titles, notes, attachments, and other user-entered planner content are excluded from Feathly custom Analytics events.
Feathly: Smart Planner stores core planner data locally on your device. This may include Loop titles, notes, categories, templates, schedule settings, generated reminder occurrences, reminder times, review records, completion history, app preferences, language, theme, wake and sleep time, notification windows, time zone settings, local entitlement information used to maintain Feathly Pro Lifetime status, including bottom-banner ad removal, and attachments you add to Loops.
In the current version, Feathly does not operate cloud sync for your Loop content. Your Loop titles, notes, schedules, reminder content, attachments, and review content are not sent to the Feathly Billing Server during normal planner use.
To save storage space and keep backup and restore reliable, attached images or files may be reduced, resized, compressed, or stored in an optimized form inside the app. Feathly does not modify the original file selected by the user; only the app-managed copy is optimized.
For example, a high-resolution photo may be saved inside Feathly as a smaller app-managed copy so that local storage, backup, and restore remain practical. Non-image files are normally preserved as selected, except where size limits, safety checks, or user-facing warnings apply.
The current version does not require a Feathly account and does not provide real-time cloud sync or cloud backup of planner content. There is therefore no Feathly cloud account to delete in the current version.
If optional cloud sync, cloud backup, account login, AI assistance, or other server-based planner features are introduced later, this policy and the Google Play Data safety disclosure will be updated before those features are made available for use.
If you purchase Feathly Pro Lifetime or another paid entitlement, the payment transaction is processed through Google Play. Feathly does not directly receive or store your full payment card number, card security code, or other full card credentials.
To verify or restore a Google Play purchase, Feathly: Smart Planner may send the following information to the Feathly Billing Server: a randomly generated installation ID, package name, product ID, Google Play purchase token, app version, and platform. The server and its hosting/network providers may also process normal network and security metadata such as IP address, request timestamps, and request logs needed to operate and protect the service.
This billing information is used only as reasonably necessary to verify purchases, restore purchases, maintain PRO entitlement, reflect refund, cancellation, or revocation status, prevent billing abuse or fraud, investigate billing problems, and maintain necessary billing, security, accounting, and dispute records.
The Billing Server does not receive your Loop titles, notes, schedules, reminder content, attachments, or review content for purchase verification. If you choose to save a purchase account hint in the app, the masked email address and encrypted local copy remain on your device and are not sent to the Feathly Billing Server.
The app may also store local purchase state, product ID, purchase restoration state, last verification time, and encrypted entitlement information on your device so that PRO access can be maintained appropriately.
When you use the Feathly support form or email support, Feathly may collect the information you choose to provide, including your name, reply email, Google Play purchase email, Google Play order ID, approximate purchase date and country, request category and title, message, app version, build number, device model, Android version, locale, time zone, and attachments.
Support requests are used to answer questions, investigate technical and billing issues, verify purchase or refund records, prevent abuse, improve the product, and maintain necessary support history. The current public support form may use an external form-delivery provider and anti-spam processing to send requests to support@feathly.com, which is hosted through Zoho Mail. These providers may process network and security metadata needed to deliver and protect the form.
Do not include passwords, full card numbers, card security codes, account recovery codes, raw purchase tokens, or unrelated personal information. Do not attach Feathly backup or database files unless Feathly support specifically requests them.
Routine support requests may be retained for up to 24 months. Billing, refund, abuse, security, accounting, or dispute records may be retained longer where reasonably necessary or required by law. Attachments are removed when they are no longer needed for the support purpose.
If you apply to join a Feathly Google Play Closed Test, Feathly may collect your Google Play email address, your consent to participate, and optional information such as Android version and device model. The application is sent over encrypted HTTPS to a Feathly support API hosted on Netlify. The API uses anti-abuse services including Cloudflare Turnstile and Upstash rate limiting, validates the submitted fields, and sends the application and acknowledgement email through Zoho Mail using support@feathly.com. The SMTP password is stored only in the server environment and is not exposed to the website browser.
If you join the Feathly Closed Testers Google Group, Google processes the Google account and group-membership information needed to operate Google Groups. Feathly group owners or managers may view member information needed to manage tester eligibility and test communications. Joining a Google Group is separate from opting in to the Google Play Closed Test.
During a Closed Test, Feathly may invite testers to submit feedback through a Google Form. The form may collect the responder email address and information about test day, features used, approximate usage time, stability or usability ratings, comments, issue details, reproduction steps, app/device support information, optional screenshot or video links, Day 7 or Day 14 review answers, and test purchase results. Google Forms may store these responses in a linked Google Sheet managed by Feathly.
Closed Test application and feedback information is used to manage tester invitations and eligibility, communicate test instructions, understand device coverage, investigate defects, evaluate usability and reliability, improve Feathly, document test results, and prepare release-readiness or Google Play production-access submissions.
Closed Test forms are not a place to submit passwords, full payment-card information, recovery codes, raw purchase tokens, Feathly backup/database files, or unrelated sensitive personal information. If a screenshot or video link is provided, the tester is responsible for checking that it does not expose unrelated personal or confidential information.
Identifiable Closed Test application and feedback records are generally retained for up to 12 months after the relevant test ends or its production-access/release-readiness review is completed, whichever is later. They may be retained longer where reasonably necessary for security, abuse prevention, legal obligations, or dispute handling. Aggregated or de-identified product-improvement summaries may be retained longer.
The free version of Feathly: Smart Planner may display a bottom banner ad through Google AdMob. Depending on your device settings, region, consent choices, SDK configuration, and applicable law, the Google Mobile Ads SDK may automatically collect or share information such as IP address, app interactions, diagnostic information, and device or account identifiers for advertising, analytics, and fraud-prevention purposes.
Data transmitted by the Google Mobile Ads SDK is protected in transit by transport encryption according to Google's SDK documentation. Feathly does not directly sell your personal information to advertisers, and Feathly does not provide your Loop titles, notes, schedules, attachments, or review content to advertisers.
Feathly: Smart Planner does not use interstitial ads, app-open ads, rewarded ads, native ads, or pop-up ads in the current version. Feathly Pro Lifetime removes ads from the app.
You can learn more about how Google uses information from apps and sites that use its services at Google's partner sites policy.
If your version of Feathly includes the optional Usage Analytics setting, Analytics is off until you explicitly choose to enable it. Declining Usage Analytics does not block core Feathly functionality, and you can turn it off later in Settings > Privacy.
When enabled, Feathly uses Google Analytics for Firebase, provided by Google, to understand how the app is used and to guide statistics, usability improvements, reliability work, onboarding improvements, and app-development priorities. Depending on the Google Analytics for Firebase SDK behavior and configuration, Google may process app interactions and events, app lifecycle or session information, app-instance or device identifiers, diagnostics, and network information such as masked IP addresses from which coarse or approximate geography may be derived.
Feathly does not intentionally include Loop titles, notes, attachments, user-defined category or tag names, search terms, notification content, contact information, raw purchase tokens, database or Loop UUIDs, or other user-entered planner text in Feathly custom Analytics events. Feathly does not set a custom Google Analytics User ID. Advertising ID collection and Analytics ad-personalization signals are disabled in the app configuration, and Feathly does not link this product Analytics data to Google Ads or AdMob for remarketing.
Google Analytics for Firebase may still process automatic events or technical metadata when Usage Analytics is enabled. Turning Usage Analytics off stops future Analytics collection from Feathly on that installation, but it does not automatically erase historical data already processed by Google Analytics. Retention and deletion of Analytics data are governed by Feathly's Analytics settings and Google's applicable policies and controls.
Feathly: Smart Planner may request notification permission so the app can send Loop and Focus Timer reminders that you configure. You can change notification permissions in your device settings.
If you export or import Feathly data, the exported files are controlled by you. You are responsible for where you save, share, or back up those files. Local backup/export files are not automatically uploaded to Feathly servers in the current version.
When a local backup includes attachments, it contains the app-managed attachment copy stored by Feathly. It does not modify the original file in your gallery, Downloads folder, or other external location.
The Google Play Data safety section describes the behavior of the version of Feathly: Smart Planner currently distributed through Google Play. It is updated when the app's data practices or integrated SDKs materially change.
The Google Play Data safety form is a current-state disclosure. Future cloud or AI features are not treated as current collection until they are actually released and used.
Feathly does not sell your personal data. Feathly does not share your core planner content with advertisers.
Google Play processes purchase and payment-related information. Feathly's Billing Server and hosting/network providers process the limited billing and network-security information described above. Google AdMob processes advertising-related information. When optional Usage Analytics is enabled, Google Analytics for Firebase processes the Analytics data described above on Feathly's behalf for product measurement and improvement. The current public Support form may use an external form-delivery provider. Closed Test applications are processed by Feathly's Netlify-hosted support API, Cloudflare Turnstile, Upstash rate limiting, and Zoho Mail for application and acknowledgement delivery. Google Groups processes tester group membership, and Google Forms/Sheets may process tester feedback and response records.
Service providers are used only for their relevant service functions and may be subject to their own privacy terms and legal obligations.
Because core planner data is stored locally, you can remove local app data by deleting Loops inside the app, clearing app data, or uninstalling the app. If you uninstall without exporting or backing up your data, local Feathly data may be lost.
The current version does not provide a Feathly cloud account, so there is no Feathly account-deletion workflow. To request deletion of support correspondence, Closed Test application/feedback records, or other server-side data that Feathly controls, submit a support-data deletion request or email support@feathly.com. Some data held by Google or another provider may also be subject to that provider's own account and deletion controls.
If Usage Analytics is enabled, turning it off stops future Analytics collection on that installation. Historical Analytics data already processed by Google is subject to the applicable Analytics retention/deletion controls. Because Feathly does not set a custom Analytics User ID, Feathly generally cannot identify a specific person's pseudonymous Analytics records merely from an email address or support request.
Billing, refund, security, fraud-prevention, accounting, or dispute records may be retained for as long as reasonably necessary to maintain entitlements, protect the service, resolve disputes, meet accounting obligations, or comply with law. Data that is no longer needed for those purposes is removed or de-identified where reasonably practicable.
Feathly: Smart Planner is designed as a local-first app. Purchase entitlement and optional purchase account-hint information may be stored locally using encrypted storage where supported. Billing Server communications use HTTPS/TLS transport protection. Hosting and network providers may maintain security logs needed to detect abuse, diagnose failures, and protect the service.
Your local data security also depends on your device security settings, such as screen lock, device encryption, backups, and operating-system protection.
Feathly: Smart Planner is a general productivity and study-planning app. It is not specifically designed for children under the age required by local law to use digital services without parental consent. If you are under that age, please use Feathly with permission from a parent or guardian.
Feathly may later offer optional cloud sync, cloud backup, account-based collaboration, additional server-side attachment handling, or AI/server-based features. Depending on the feature a user chooses to enable, those future services may need to process categories such as account/contact information, user-generated planner content, attachments, synchronization metadata, service diagnostics, and security information.
These are not current data-collection practices for the local-first planner simply because they are listed here as possible future features. Before any such feature is launched, Feathly will define the exact data fields, purposes, retention rules, deletion controls, service providers, security measures, and any required consent, and will update this Privacy Policy and the Google Play Data safety disclosure before users are asked to use the feature.
We may update this Privacy Policy as Feathly: Smart Planner changes. Important changes, especially those related to Usage Analytics, advertising, purchases, support data, Closed Test data, attachment handling, cloud sync, accounts, AI features, or server-based data handling, will be communicated clearly and reflected in applicable store disclosures.
If you have questions about this Privacy Policy or want to request access, correction, or deletion of data that Feathly controls, use the support form or contact support@feathly.com.
Last updated: 2026-09-10.