Legal

Privacy Policy

Last updated:

This policy describes what Zybble collects and how it is used. It is written to be read, not skimmed past. How we protect what we hold is described separately on our security page.

1. What we collect

  • Account information: your name, email address and password (stored only as a salted hash) when you create a Zybble account.
  • LinkedIn connection data: when you connect LinkedIn, we store the OAuth access token and basic profile identifiers returned by LinkedIn's API. We never see or store your LinkedIn password.
  • Content you create: drafts, scheduled posts and media you add to the workspace.
  • Usage and analytics data: metrics returned by the LinkedIn API for your posts, plus standard technical logs (browser type, IP address, timestamps) required to operate the service securely.
  • If you write to us through the contact form, we receive your name, email address and message, and use them only to respond.

2. What we never do

  • We never scrape LinkedIn or collect data LinkedIn has not made available through its official API.
  • We never sell your data or your content to anyone.
  • We never publish to LinkedIn without a post you explicitly scheduled.
  • We never train third-party models on your private drafts — Zybble has no features that send your content to model providers.

3. How we use data

  • To operate the core service: publishing scheduled posts, rendering your calendar, and computing your analytics.
  • To communicate with you about your account — transactional email only (confirmations, security alerts and receipts), sent through a third-party email delivery provider. Marketing email does not exist today; if that ever changes, it will be opt-in and one click to leave.
  • To process payments for the Pro plan through a third-party payment processor. Card details go to the processor, not to Zybble.
  • To keep the platform secure: abuse detection, rate limiting and debugging.

4. Where data lives

  • Zybble is hosted on Vercel with a managed Postgres database. LinkedIn tokens are stored encrypted at rest.
  • A small, ordinary set of sub-processors is involved in operating the service: hosting (Vercel), the database, authentication (Supabase), email delivery and payment processing.
  • Backups are retained for a limited disaster-recovery window and then purged.
  • Workspace data is isolated at the database layer with row-level security, so one workspace's data is never served to another.

5. Your rights

  • Your drafts, schedule history and analytics are visible in your workspace at any time. For a copy of your data in a portable format, contact us and we will provide it.
  • Disconnect LinkedIn from Zybble or from LinkedIn's own settings; either action revokes our access.
  • Delete your account and its associated data from your account settings. Deletion removes data from live systems; backup copies expire with the backup window described above.
  • Residents of the EEA, UK and California have statutory rights over their personal data, including access, correction and deletion. To exercise them — or ask anything about this policy — write to us.

6. Changes to this policy

  • If this policy changes in a way that matters, we will tell you in the product or by email before the change takes effect. The date below always reflects the current version.

7. Contact

  • Questions about this policy or your data: tejassutar.business@gmail.com — or through the contact form. Messages reach the founder directly.