Privacy Policy
Draft only. Not an effective or accepted public policy. Operator identity, contact, retention and legal terms require owner review before release.
Planned subscription processing — inactive
When separately approved and enabled, Google Play or the App Store handles the purchase interface. Posynca verifies purchase evidence server-side, keeps an account/workspace binding, encrypted purchase references, subscription lifecycle and usage/audit records, and does not collect card details in the mobile app. Store evidence must not be sent in support or diagnostics. Final lawful basis, retention and contact disclosures require operator review.
Scope and release status
This draft describes Posynca Creator. Public availability, the legal operator, contact channel, effective date and retention periods require owner review before release. This is not an approved privacy notice.
Information used to provide your studio
The application uses your account email, profile and workspace preferences, private drafts, selected photos or videos, connected-account identifiers, authorization grants and publishing records. These support sign-in, ownership checks, private media access and the posting actions you request.
Service providers and social platforms
The existing architecture uses Neon for authentication and database services, Cloudflare for the Backend and private R2 media, and the configured authentication email provider. Authorized social content is sent to Facebook, Instagram or Threads only for the accounts and actions you select. Those providers apply their own privacy policies.
Private storage and permissions
Provider credentials remain on the server. Device session handles use secure operating-system storage; temporary media copies stay in the app’s private storage. Selected media permissions support drafts and uploads. Camera, microphone, contact and location access are not required by the current Creator implementation.
Diagnostics and tracking
The new app diagnostic summary contains predefined error categories and coarse times, not captions, email addresses, passwords, tokens, provider URLs or raw exception stacks. It stays in memory until you choose to share it. No advertising SDK, advertising identifier collection or automatic third-party crash-reporting service is configured by this implementation.
Retention and deletion
Final retention periods and any legal retention exceptions remain to be approved. An account-deletion request must be acknowledged by the Backend; an on-screen draft or missing record does not establish erasure. Removal can involve private media, connected grants and provider-side steps. Posts already delivered to social platforms may require separate removal there. Do not uninstall before confirming any pending request and saving its receipt.
Your controls
You can manage workspace preferences, disconnect social accounts, clear private device downloads, sign out and use available recovery and account-deletion controls. A disconnected provider may also require revocation in its own settings. Inactive controls explain their status and never pretend to complete an operation.
Contact and review
A verified support and privacy contact and the operator’s identity must be supplied before publication. During private development, contact the workspace owner directly. Do not send passwords, email codes, API keys or private media in a support request.
Operator: not yet supplied. Effective date: not yet accepted.
Support & privacy contact →