Privacy policy

This policy explains how Playbit, inc. (“we” or “us”) handles personal information in the Playbit beta and on our website. We use account and service information to operate Playbit, understand adoption, prevent abuse, and provide support. We do not collect what you type, which app contents you view, or a history of foreground activity for analytics.

Your account and email address

We process your email address to send sign-in codes and find your account. After successful verification, we retain the address and its verified status with your account. An account can have multiple associated email addresses. We may use verified addresses for account and service notices, including security notifications and material policy changes. Product news subscriptions are separate, as described below.

We also store hashes of normalized email addresses for lookup and account statistics. Your account ID is not derived from your email address, but these records let us find the account when given an associated email address, including for sign-in, support, and sharing. Account IDs and email hashes are not anonymous information.

We store account and installation identifiers, public authentication material, sign-in verification and rate-limit records, account creation time, the accepted Terms revision and timestamp, and account-setup milestones. Your account key stays on devices you control and trust. You can enter it into another trusted installation of Playbit, but it is not sent to or stored on our servers. We store a public verification key derived from it, which cannot decrypt your data. Credential backups can contain other private keys, but are encrypted on your device before upload; we do not have the account key needed to decrypt them.

App data, synchronization, and sharing

We store and transmit app packages, synchronized data, and the records needed to manage access and sharing. Your synchronized account records, including your display name and saved invitations, are encrypted on your device. Access to app databases depends on their permissions and whether their keys are shared with the Playbit service; databases that permit service access can be read and processed by the service. Encryption does not hide all service metadata, such as account and volume identifiers, access relationships, data sizes, and connection times.

Apps and people you grant access to can use the data available to them. Recipients may retain copies after you end access. External services used by an app have their own privacy practices.

Usage statistics

We count accounts with authenticated server connections, including background synchronization and automation. These counts do not measure attention or foreground use, and exclude offline use. We record connection days, last observed connection time, and whether email verification, credential saving, account-key setup, and profile setup have completed. We use these records to operate and improve the service and investigate support requests.

Network information and approximate region

Our servers and network providers process IP addresses to deliver connections. At account creation, we use the connection IP address to estimate country and state or region using a locally installed geographic database. This estimate may be wrong or unavailable, particularly with VPNs. The signup statistics retain the approximate region, not the raw IP address. We do not collect precise location for these statistics.

We retain a hash of the connection IP address to limit sign-in requests and prevent abuse. Website access logs record request categories, response status, timing, and traffic volume. Website error logs may include IP addresses, usernames, and request URLs. These operational records are separate from signup statistics.

Authentication security logs record the connection IP address and port, the normalized recipient email and device label when supplied, the server timestamp, authentication method and outcome, and account and installation identifiers when known. We use these restricted logs to investigate unexpected sign-in emails, account access and abuse. An attempted recipient address does not establish who made the request. These logs do not include sign-in codes, account keys, authentication tokens, or app contents, and are separate from usage statistics.

Optional crash reports

The Mac app can save diagnostic reports locally after a failure and ask whether to send them. Reports include the Playbit build, environment, process information, time, error details, and stack traces, and may contain local app data. “Send” includes your current account ID when available. “Send Anonymously” omits the account ID field, but does not remove identifying information that may appear in the diagnostic text. “Don’t Send” deletes the reports covered by that prompt from the local report queue without uploading them.

We use submitted reports to diagnose and fix problems. Authorized operators can access them, and we keep restricted server copies and backups.

Apple push notifications

For Finder integration on macOS, we store an Apple push token associated with your account, installation, and selected volumes. When push delivery is enabled, we send Apple the token and a notification identifying the account and volume so your Mac can check for changes. The notification does not include file contents.

Service providers and communications

We use Amazon Web Services for hosting, storage, and sign-in email delivery, and Cloudflare for website and download delivery. These providers process the information needed to provide those services, including network request information. Apple delivers the push notifications described above.

Authorized operators can look up account status and assist with access problems. Internal Slack announcements about new accounts contain the approximate signup region and a link containing the account ID. They do not contain your email address or IP address. Slack processes these announcements as our service provider; access to the linked account page requires separate authorization.

If you subscribe to our news mailing list, the signup form sends your email address and any name you provide to Mailchimp. You can unsubscribe using the link in those emails. Contacting us for support also gives us the information you choose to include in your message. Do not send your account key.

Retention

The analytics database keeps account-linked connection days for a rolling 90-day window. Sign-in attempt summaries are removed after 90 days without a new attempt for that email hash. Daily aggregate counts are retained longer. Associated email addresses and their verification status, account creation, last connection, setup completion, Terms acceptance, and support audit records are retained with the account. Authentication records, including the email-to-account mapping and rate-limit records, are stored separately and do not automatically expire after 90 days.

Submitted crash reports and their backups currently have no automatic expiration. Website logs are rotated daily, with up to seven older log files retained. Other restricted backups may retain older records until those backups expire; restoring analytics data reapplies its 90-day activity cutoff.

Authentication security logs have a 30-day retention period. Host copies use daily or size-based rotation with up to four older files and a 30-day age setting; rotation and removal are best effort and can be delayed by inactivity or an unavailable host. Additional server copies follow separate retention limits. These logs are collected prospectively after the updated service and logging configuration are deployed; they cannot reconstruct earlier requests, and interruptions or logging limits can leave gaps.

Local storage and your choices

You can use locally available Playbit data offline without generating connection activity. The browser version stores credentials and app data in your browser; clearing that storage can remove local copies. The internal operator dashboard uses a security cookie to protect account administration from forged requests. Our account usage statistics are not used for advertising or cross-site tracking.

Contact [email protected] for questions about personal information, access, correction, deletion, or an objection to processing. Applicable rights depend on your jurisdiction. Deleting a local copy does not itself delete server records or copies held by other people. Accepting the Terms does not waive privacy rights.