Cookie Policy
1. What cookies are
Cookies are small files that a website stores on your device. Similar technologies, such as local storage and pixels, do the same job. This policy covers all of them.
A first-party cookie is set by us. A third-party cookie is set by a provider that supplies a tool to us.
2. Who sets them
SwiftSoft Labs LLC ("we", "us") sets the cookies that run the service. The providers listed in section 4 may also set cookies or read data from your device when they supply their tool to us.
3. Cookies we need
We set these first-party cookies on our own domain. All are HttpOnly, so scripts on the page cannot read them:
- `ef_access_token` and `ef_refresh_token`: keep you signed in. The refresh cookie lasts up to 30 days.
- `ef_oauth_state` and `ef_oauth_redirect`: protect sign-in with Google or GitHub. They last 10 minutes.
- `ef_social_oauth_state`, `ef_social_oauth_provider`, `ef_social_oauth_application`, `ef_social_oauth_verifier` and `ef_social_oauth_user`: protect a creator's connection of a TikTok, Instagram or Facebook account. They last 10 minutes.
You cannot switch these off in the service, but you can block them in your browser, and the service may then not work.
4. Cookies and tools from other providers
We group the providers by what their cookies do:
- Strictly necessary: These are needed to run the service and keep it secure, for example to keep you signed in or to complete a payment. They do not need your consent.
- Performance and analytics: These show us how the service is used and where it fails, so that we can improve it.
Strictly necessary
- GitHub Sign-In. Sign in with GitHub. Data: Email address, name, GitHub account ID. Location: United States. Agreement: https://github.com/customer-terms/github-data-protection-agreement. GitHub sets its own cookies only on GitHub's pages, when you choose to sign in with GitHub.
- Google Sign-In. Sign in with Google. Data: Email address, name, Google account ID. Location: United States. Agreement: https://business.safety.google/processorterms/. Google sets its own cookies only on Google's pages, when you choose to sign in with Google.
- Sumsub. Creator identity verification. Data: Creator name, date of birth, government ID images, selfie, country. Location: Not provided. Agreement: https://sumsub.com/files/data_processing_agreement.pdf. Sumsub's verification screen may set its own cookies while a creator uses it.
- Cloudflare Turnstile. Bot check on sign-in, sign-up and booking. It may set its own cookies for that check.
- Plaid. A US creator's bank link opens in Plaid's own screen, which may set its own cookies.
- Kelviq. The checkout page is Kelviq's, and it sets its own cookies there.
Performance and analytics
- PostHog. Anonymous page views on public pages. Data: Random session ID, page URL. Location: United States. Agreement: https://posthog.com/dpa. It keeps a random ID in your browser's session storage (`ssl-marketing-distinct-id`), which is cleared when you close the tab, and sets no cookies.
- Sentry. Error monitoring. Data: Error reports with technical details (no default personal data, no session replay). Location: United States. Agreement: https://sentry.io/legal/dpa/. It uses no cookies.
Our other providers (InsForge, OpenRouter and Vercel) work on our servers and set nothing on your device. We set no advertising cookies.
5. Your choices
You can block or delete cookies in your browser settings. Blocking them may stop parts of the service from working. Each browser explains how in its help pages.
6. How long cookies last
A session cookie is deleted when you close your browser. A persistent cookie stays on your device until it expires or you delete it. The lifetime of a provider's cookie is set by that provider and is described in its own policy.
7. Changes and contact
We may update this policy. Questions go to legal@swiftsoftlabs.com.