Privacy Policy

1. Accounts and writing on your device

The app processes service type, server/PDS address, account identifiers and credentials to maintain sign-in and switch accounts. Credentials and encryption keys use protected operating-system storage. Bluesky authorization is bound to the DID, issuer and approved permissions.

Timeline caches, reading positions, drafts and local attachments are separated by account. Drafts may include text, reply and quote targets, visibility, content warnings, polls, alt text and service-specific settings. This writing is not sent as analytics or crash-report content.

2. Information sent to your chosen service

Signing in, reading, posting, searching, managing relationships and messaging send necessary requests and authorization to the relevant server, PDS, authorization provider or service API. Your chosen service processes posts, media, profile information, messages and search terms to perform your actions.

Public posts may be federated or copied to other services or devices. Private posts and DM/chat are also subject to recipient and service policies; deleting something in the app cannot guarantee removal of outside copies. Opening external links or remote media may send connection information, including an IP address, to the destination.

3. Notifications and Push Relay

In-app notifications come from the selected account’s service API. Device push depends on support, separate setup and permission. Operational delivery routes and receipt on real devices have not yet been fully verified.

When push is enabled, the Relay and Apple APNs or Google FCM may process device push tokens, installation and subscription identifiers, service/account identifiers and minimal notification identifiers for delivery. Separately authorized Misskey Relay credentials are protected on the Relay; this does not mean all Mastodon or Bluesky app login credentials are forwarded to it.

The Relay is designed to exclude post and DM/chat bodies from push payloads and delivery logs. Current source limits queue validity to 24 hours, deduplication/delivery metadata and deletion receipts to seven days, and backups to seven files/seven days. Cleanup intervals, actual settings and backup deletion conditions must be checked before activation.

4. Usage analytics and crash diagnostics

The code includes Google Firebase Analytics and Crashlytics for app quality. The reviewed configuration has collection verification flags disabled. Collection must remain inactive until published disclosures, user notice and platform privacy verification are complete.

If activated, processing may include startup, fixed screen categories, generic error states, app/OS versions, device categories and session/anonymous installation information. Post text, search terms, DM/private-post bodies, email addresses, credentials and push tokens are excluded from analytics and crash reports. The implementation must be verified against its no-advertising-ID and no-ad-tracking contract.

Actual fields, Google processing and retention, international processing, legal bases and any required consent must be finalized and disclosed before activation. An app-use notice does not replace separate consent where the law requires it.

5. Website and support

This website adds no advertising or analytics SDK, external fonts or contact form. Language selection uses links and does not set a language cookie. Hosting and delivery providers may process IP addresses, request times, browser and connection information to serve and secure pages. Actual logging and retention must be confirmed before publication.

Emailing [email protected] provides your email address, message and any voluntary attachments for support and troubleshooting. Do not send passwords, tokens, DM text or unnecessary sensitive information. The mail processor and support retention period must be identified in the finalized policy.

6. Retention, deletion and disconnecting accounts

On-device accounts, caches and drafts are retained according to app functions and your deletion choices. Account removal should ask about local drafts; authentication expiry alone must not automatically delete them. OS backups or external storage may retain copies after app removal.

Removing an account or signing out of the app is separate from deleting a server account or posts. Use the relevant service’s settings and policies for deletion and revoking authorization. Team-held information is deleted when its purpose ends; any legally required retention must identify the data, basis and period.

7. External processing and international transfers

Your chosen server/PDS, authorization provider and media hosts are separate operators handling your requests. Google Firebase, Apple APNs and Google FCM may process relevant data only for features actually activated.

The Team’s hosting, Relay and mail processors, processing countries, transferred fields, purposes, timing, methods, retention and rights procedures must be verified before final publication. This draft does not authorize unverified transfers or additional collection.

8. Your rights and protection

You may request access, correction, deletion, restriction and other rights under applicable law by contacting us below. We may need to verify your authority. Requests about information held by outside services should go to those operators.

We protect access to credentials and account-separated data and restrict sensitive information from logs, analytics and crash reports. Follow the age and parental-consent requirements of your service, server and location; do not bypass access restrictions.

9. Changes and contact

For privacy questions and rights requests, contact the Pointless.chat team at [email protected]. We publish policy changes and dates, and provide advance notice or obtain consent when applicable law requires it for significant changes.