Legal
ContentSpark Privacy Policy
Last updated: April 1, 2026
This Privacy Policy explains how ContentSpark ("ContentSpark," "we," "us," or "our") collects, uses, stores, and shares information when you use the ContentSpark website and application (the "Service"). By using the Service, you acknowledge this Privacy Policy.
1. Scope
This Privacy Policy applies to information processed through the ContentSpark app and website, including account access, content generation, saved history, subscription and billing flows, and related support or operational activities.
2. Information We Collect
2.1 Account and Authentication Data
We use a third-party authentication provider (currently Clerk) to manage sign-in and account identity. Depending on your sign-up method and profile, this may include:
- email address
- authentication provider user ID
- basic profile information you provide to the auth provider
- session/authentication status
We do not need your password for day-to-day operation if authentication is handled by the provider.
Legal basis: contract / service performance and, where applicable, legal obligation.
Retention period: We retain this data until the service is terminated.
2.2 Information You Enter Into the App
We collect and store data you actively provide in order to use the Service, including:
- text, source material, prompts, or content you submit for repurposing
- selected output platforms or generation preferences
- saved generation history
- basic account preferences and app configuration
Examples include pasted articles, transcripts, draft copy, selected platforms such as LinkedIn or X, and editable generated outputs saved in your account history.
Legal basis: contract / service performance and legitimate interests.
Retention period: We retain this data until the service is terminated.
2.3 Generated Content and History Data
To provide the Service, we process and may store operational generation data such as:
- generation requests
- generated outputs
- selected target platforms
- generation timestamps and related metadata
- history or deletion state where supported in the app
Legal basis: contract / service performance and legitimate interests.
Retention period: We retain this data until the service is terminated.
2.4 Usage and Operational Data
We may collect limited usage or operational event data to run and improve the Service, such as:
- first sign-in / activation events
- generation events
- subscription status events
- request logs and diagnostics
Legal basis: legitimate interests.
Retention period: We retain this data until the service is terminated.
2.5 Payment and Subscription Data
If you use paid features, billing is processed through a third-party payment processor (currently Stripe). We may store or receive limited billing-related metadata, such as:
- subscription status
- checkout/session references
- customer or subscription identifiers
- payment state needed to manage access
We do not intend to store full raw payment card details ourselves.
Legal basis: contract / service performance, legitimate interests, and where applicable legal obligation.
Retention period: We retain this data until the service is terminated.
3. How We Use Information
We use personal data and app data to:
- provide the Service
- authenticate users
- process source content and generate repurposed outputs
- store saved history and preferences
- provide subscription-gated features
- troubleshoot bugs and improve reliability/performance
- protect the Service against misuse or unauthorized access
- comply with legal obligations
4. Cookies, Sessions, and Local Storage
4.1 Essential Authentication Cookies
The app uses essential authentication/session cookies through Clerk and related auth/session handling. These cookies are used to keep you signed in, identify your authenticated session, and protect access to account-specific routes and APIs.
These cookies are considered essential for the app to function.
4.2 Local Storage / Similar Browser Storage
The app may also use browser storage such as localStorage for limited app-state purposes, for example UI state or temporary checkout/auth handoff behavior.
4.3 Analytics Cookies
Based on the current application setup, we did not identify a clear non-essential analytics-cookie or marketing-cookie implementation that would automatically require a cookie-consent popup solely for the current auth and app flow. If non-essential analytics, advertising, retargeting, or similar cookies are added later, this policy should be updated and any legally required consent mechanism should be implemented.
5. How We Share Information
We do not sell your personal data.
We may share information with service providers and infrastructure providers that help us run the Service, such as providers for authentication, hosting, databases, AI generation, and payment processing.
Examples from the current stack may include:
- Clerk
- Vercel and related hosted infrastructure
- our VPS / database infrastructure
- Stripe
- OpenAI or related AI model providers used to generate content
We may also disclose information when required by law or to protect rights, security, or the Service.
6. Security
We use reasonable technical and organizational measures to protect information, including authenticated access controls and HTTPS/TLS in normal operation. However, no method of storage or transmission is perfectly secure, and we cannot guarantee absolute security.
7. Your Rights
Depending on your jurisdiction, you may have rights such as:
- access to your personal data
- correction of inaccurate data
- deletion of your data
- restriction of processing
- objection to certain processing
- data portability
- withdrawal of consent where processing is based on consent
You may also be able to use in-app account deletion or history deletion tools where available. For privacy-related requests, contact: plug4264@gmail.com
8. International Transfers
If infrastructure or providers process data in countries outside your own, your data may be transferred internationally. Where required, we rely on appropriate safeguards or legal mechanisms.
9. Children
ContentSpark is not intended for children. We do not knowingly provide the Service to children below the age permitted under applicable law.
10. Changes to This Policy
We may update this Privacy Policy from time to time. If we make material changes, we may notify users in-app, by email, or by updating the effective date.
11. Contact
For questions or requests relating to privacy or data protection, contact:
plug4264@gmail.com