Privacy Policy

What this policy covers

This policy covers the SharetoBoard Android app and SharetoBoard website. The detailed SharetoBoard for Chrome Privacy Policy governs the Chrome extension and is incorporated here by reference.

Core principles

• Privacy-first defaults and fail-closed behavior on sensitive paths
• No offline queue intake or delivery in this release; existing rows remain frozen on-device
• App-private storage and encrypted-at-rest handling where implemented
• No sale of personal data

Chrome extension privacy

SharetoBoard for Chrome sends website content only after the user highlights content and chooses Send to Board or clicks the optional Selection Bubble. When the bubble is enabled, its local page script observes non-empty selections only to position the logo. The free Chrome beta copies the selected content directly to the configured Poppy board, does not send it to SharetoBoard-operated servers, and does not create a persistent highlighted-content outbox.

The configured Poppy board URL is stored in Chrome extension sync storage and may be synchronized through the user's Chrome profile. Version 1.7.0 click diagnostics do not include highlighted-content previews. Optional access to ordinary HTTP/HTTPS pages is requested only when Selection Bubble is enabled and is removed when the feature is disabled.

Data handling summary

• Capture metadata and action receipts may be stored for reliability diagnostics.
• Sensitive payloads are not logged to public analytics channels by design.
• Board delivery features require a valid Poppy destination selected by the user.
• Existing queue rows from earlier builds remain frozen on-device; this release does not ingest, retarget, or deliver them.
• External sharing accepts online text and links only. Native media prep and external image, video, and PDF sharing are unavailable.
• Calendar nudges remain available for user-selected calendars.
• The invite-based closed beta is free. SharetoBoard does not offer subscription purchase or entitlement verification in this release.
• Notion Inbox is temporarily unavailable. SharetoBoard’s Notion authorization endpoints do not exchange or refresh credentials in this release.

Third-party authentication

Poppy uses Clerk to authenticate users. During beta, SharetoBoard supports the email-and-password option presented by Poppy. Google sign-in is not supported inside SharetoBoard.

SharetoBoard does not operate a separate Google OAuth exchange and does not ask users to copy or provide Google passwords, authorization codes, access tokens, ID tokens, or Clerk session tokens. Google sign-in navigation is blocked rather than bridged into native app code.

Poppy and Clerk may store authentication cookies or related session data inside Android WebView to maintain the Poppy session. SharetoBoard does not implement a separate bridge that exports or relays a Google-authenticated session into native code or the SharetoBoard backend.

Microphone

SharetoBoard requests microphone permission only so the embedded Poppy board recorder can function inside the app. SharetoBoard does not record, buffer, store, transcribe, or upload microphone audio. Recording and transcription are handled by the Poppy board service inside the WebView, subject to Poppy's own policies.

Closed-beta subscriptions

SharetoBoard subscriptions and entitlement verification are unavailable during the invite-based closed beta. The app does not send Google Play purchase tokens, product or package identifiers, or app-install identifiers to SharetoBoard’s entitlement service in this release.

Any inactive billing route returns an unavailable response. It does not verify purchases or create entitlement records.

Third-party destinations

• Poppy handles board content, recording, and transcription under Poppy's policies.
• Google Play distributes the closed-beta app. SharetoBoard subscription checkout is not offered in this release.
• Notion Inbox is temporarily unavailable, so this release does not send captures to Notion through that integration.
• SharetoBoard does not sell personal data or use advertising or cross-app tracking SDKs.

Retention and deletion

• Local app data normally clears when the app is uninstalled.
• No new entitlement records are created while closed-beta billing is unavailable.
• You may request deletion of eligible historical support records by emailing support@sharetoboard.com.

Your controls

• Configure the target destination in app settings.
• Understand that existing queued rows remain frozen; delivery is unavailable in this release.
• Disable optional features (for example scheduled captures or calendar nudges).
• Contact support for deletion/help requests: support@sharetoboard.com.