Legal

Privacy Policy

Last updated: 2026-09-21

1. Who we are

This Privacy Policy describes how Publane handles personal data through the service at https://app.wtverkoop.com. The service is operated by an individual operator based in Brazil. Privacy questions and requests can be submitted through the Contact page or by email at carmajarred@gmail.com.

2. Scope

This policy applies to the public website, SaaS account, account connection features, publishing workflow, support, and security operations. It does not replace the privacy terms of a connected third-party platform.

3. SaaS account data

We process the email address, authentication identifiers, account status, consent timestamps, and security/session information needed to create, protect, recover, and delete a product account. Password authentication is provided by Supabase; the application does not store plaintext passwords.

4. Connected account data and OAuth permissions

Users may authorize `user.info.basic` and `video.publish`. We process the platform open ID, display name, username, avatar URL, granted scopes, connection status, and expiration metadata needed for that connection. We do not request unrelated platform permissions in V1.

5. Tokens and credentials

Access and refresh tokens are kept server-side, encrypted at the application layer, and never intentionally exposed to the browser, source control, or ordinary logs. Client secrets and encryption keys are kept in deployment secret storage.

6. Publishing metadata

We may store a caption, selected privacy and interaction settings, commercial content disclosure, AIGC declaration, consent timestamp, file metadata, publishing identifier, internal state, raw platform status, safe error fields, and public post identifiers where returned. We do not use this metadata to create unrelated advertising profiles.

7. Video handling

V1 is designed not to permanently store user video files. A local file may be previewed in the user’s browser and, after explicit confirmation, transferred to TikTok for publishing. Publane does not retain a copy. If the browser cannot complete TikTok's cross-origin upload, a small-file fallback may process the bytes transiently in memory solely to forward them to TikTok.

8. Logs and security data

We may process timestamps, route/event names, a limited request identifier, safe error codes, and platform log identifiers to secure and operate the service. Passwords, cookies, authorization headers, OAuth codes, tokens, client secrets, upload URLs, and raw request bodies are excluded or redacted from application logs by policy.

9. How we use data

  • Provide and secure the requested product features.
  • Authenticate users and maintain sessions.
  • Carry out user-confirmed account connection and publishing operations.
  • Display publishing status and troubleshoot safe error information.
  • Meet legal, abuse-prevention, and security obligations.

10. Service providers and third parties

Service providers include Supabase for authentication and PostgreSQL, Netlify for web hosting, and TikTok for authorized account and publishing services. Each provider processes data under its own terms and privacy commitments and may process data in the regions where it operates its infrastructure.

11. Retention

Account, connection, publishing history, and minimal audit data are retained while the account is active and as needed to provide and secure the service. OAuth state is short-lived and expires automatically. Account deletion removes account-linked application data according to the deletion process, except where limited retention is required for security or legal obligations.

12. Deletion and disconnect

Users can delete their account in Settings. The deletion process revokes connected authorization where available, removes token material, ends the application session, and deletes account-linked product data subject to required retention. Disconnecting a platform account does not delete content already published on that platform.

13. Security

The service is designed with encrypted transport, server-only secrets, application-level token encryption, access controls, CSRF defenses, validation, rate-limit boundaries, redacted logging, and reviewed database migrations. No system can guarantee absolute security; suspected incidents should be reported promptly.

14. User rights and regional terms

The operator is based in Brazil and handles applicable requests in accordance with Brazilian data-protection requirements, including the Lei Geral de Proteção de Dados Pessoais (LGPD), where applicable. Available rights may include confirmation, access, correction, deletion, portability, information about sharing, or objection, as provided by applicable law. Users outside Brazil may also have rights under the laws that apply to them.

15. Changes and contact

Material updates will be posted with a new effective date. Privacy questions and rights requests can be submitted through the Contact page or by email at carmajarred@gmail.com.