SocialForge · Legal information
Privacy Policy
Version: 23 October 2026 · Invitation-based creator pilot
This policy covers SocialForge's existing workspaces and invitation-based pilot for independent creators. Public registration remains closed. Pilot applications and availability are described on the creator pilot page.
1. Who is responsible
Iliya Simeonov, based in Bulgaria, operates SocialForge and is the controller for personal data used to administer and secure the service and answer enquiries. Contact support@socialforge.dev about personal data or to exercise your rights.
This policy also covers personal information that may appear in submitted media and campaign material. A person providing such material must have authority to collect and use it for the intended purpose. Future processing solely on a business customer's instructions will require an appropriate processing agreement before that service begins.
2. Information we handle
- Account details: name, email, password hash, verification and access information, and associated organisations or brands.
- Pilot access: application name, email and proposed workflow; access decisions, invitation expiry and a hash of the invitation token; accepted terms version; help and deletion requests. Invitations do not verify email possession. We use these records to review requested access, administer accounts and respond to applicants, not to subscribe them to marketing.
- Content: uploaded and generated media, original filenames, prepared copies, prompts, reference material, subtitles, titles, descriptions, tags, languages, publication settings, schedules, time zones and review decisions.
- Connected profiles: platform account, page or channel identifiers, supported profile details, permissions, authorisation tokens and expiry information.
- Operations: publication identifiers, results, timestamps, diagnostic errors, requested generation and usage records, and supported account or post metrics.
- Technical and support data: session records, security and server logs, and information supplied in support requests. Session or infrastructure records can include IP addresses and browser information.
Information comes from you, activity within SocialForge, and platforms or providers used for your authorised operations. Do not submit unnecessary sensitive personal data, passwords or access tokens in media, prompts or support messages.
3. Purposes and legal bases
Account access, content preparation, requested campaign operations and support use data necessary to provide the service under our agreement with you. Security, abuse prevention and fault diagnosis serve our legitimate interests in protecting the service and its users, subject to their rights. A legal obligation may require particular records to be retained.
Where a separate optional use requires consent, that consent must be obtained and may be withdrawn. Granting a social-platform API permission does not authorise unrelated uses. Basic account details and the permissions needed for an integration are required for those functions to work.
SocialForge executes content and scheduling instructions; it does not use these features to make automated decisions with legal or similarly significant effects about individuals.
4. Social platforms
Pinterest · When connected, SocialForge reads your profile and list of boards. It stores encrypted connection tokens and sends the image, text and link you approve to your chosen board. You can disconnect in Social Accounts and revoke access in Pinterest settings. Disconnecting cancels pending Pins. Pins already sent remain on Pinterest.
Facebook and Instagram: authorised operations use account or page details, send requested content, receive processing results and retrieve supported insights. Meta processes data received by its services under its own policies.
YouTube: SocialForge uses YouTube API Services for authorised channel, upload and supported publishing operations, including optional features when enabled. Google's handling of data is described in the Google Privacy Policy. You can revoke access through Google's account permissions and contact us to request deletion of data held by SocialForge.
TikTok: authorised connections use basic profile information and permission to upload a selected video for the creator to finish in TikTok. Direct Post requests a separate permission and public use depends on TikTok's audit and the account's available options. Live app status alone does not establish public Direct Post approval. Stored information includes profile identifiers and display name, encrypted access and refresh tokens, expiry, scopes, creator-specific posting options, publishing identifiers and status/error information. Signed transfer URLs expire and are not retained as complete URLs in publication diagnostics.
Published content is available to the audience selected on its destination platform. Revoking access or deleting a SocialForge record does not automatically delete a published post or the platform's own records.
5. Service providers and AI operations
- OVHcloud: hosts the application and its local database, files and server backups.
- Resend: delivers service emails, such as verification and password recovery, and receives the recipient address and message information needed for delivery.
- Support email: Cloudflare forwards messages sent to our support address to the operator’s Gmail inbox. We also use Resend to manage support conversations and send replies. These providers process the sender and recipient addresses, message content and attachments needed to deliver, store and respond to these enquiries.
- Cloudflare: supplies domain infrastructure. Cloudflare Workers AI is also an enabled option for AI operations that select it.
- AI providers: available configured routes include OpenAI, Cloudflare Workers AI, Hugging Face Spaces and AI Horde. Which receives input depends on the operation, available credentials, configuration and permitted fallback. Availability does not mean every provider receives every request.
- Font delivery: some existing site pages load fonts from Bunny Fonts. These legal pages use system fonts and do not request that external font service.
AI requests may contain prompts, relevant brand or content context and reference media supported by the selected operation. Outputs and usage records may be retained in SocialForge. A structured-file import alone does not send every imported video to these AI providers. Provider-specific settings and terms govern their processing; do not assume a uniform no-retention or no-training rule across providers. Hugging Face Spaces can be operated by a separate Space author.
The operator may access relevant information for support, maintenance or security. Disclosure may also be necessary to meet a legal obligation or establish or defend legal claims. SocialForge does not sell personal data.
The creator pilot provides only TikTok video upload, review, status, help and account security. Creators connect their own authorised TikTok accounts. They cannot access AI services, other platform workspaces, the operator's personal provider keys or another workspace's connections. The application's server-side OAuth client credentials and infrastructure remain confidential and are used to operate the integration; they are not shared with creators.
6. Cookies and site measurements
Session and security cookies support sign-in and protect requests. Selecting remembered sign-in can create an additional persistent cookie. The current session inactivity limit is 120 minutes; this is not a promise that every associated database record is erased at that moment. Blocking necessary cookies may prevent account functions from working.
The application's page-measurement component records visit time, route name, response status and duration, whether a visitor is signed in, and the referring domain, and maintains hourly aggregates. It does not record IP addresses, user identifiers, full referring URLs or browser fingerprints in those measurements. Session records and infrastructure logs are separate and may contain additional technical information.
7. Retention and deletion
Account records, media, publishing history and related working data are retained while needed for requested operations, review, support and account administration. They do not all have automatic expiry. A deletion or closure request requires review of the relevant records and files; deleting an account row or archiving a campaign is not a guarantee that every associated copy has been erased.
Pilot invitations expire after seven days and are invalidated when used, replaced or revoked. Application and support records require operator review for deletion; they do not have an automatic deletion promise. You can record an authenticated request in your creator workspace or contact support@socialforge.dev. Marking a request reviewed does not mean erasure is complete.
- Process activity events and stale runtime signals currently have scheduled cleanup after 30 days. This does not cover every application log or history.
- Web-server logs rotate daily with 14 retained rotations. The main application log currently has no equivalent automatic age limit and needs manual review and cleanup.
- Completed daily database and configuration backups are eligible for automatic cleanup after approximately 15 days, on the next successful cleanup run. Incomplete, exceptional, migration and deployment backups are not all covered by this rule and require manual review.
Retention is assessed against continuing service needs, outstanding faults or requests, security, recovery, applicable legal obligations and the rules of each connected platform. Data that is no longer needed should be removed or anonymised. Platform API data is also subject to the platform's applicable retention and revocation requirements; the backup periods above do not override them.
To request access, correction, deletion or account closure, email support@socialforge.dev with your account email and the records or connection concerned. Do not send a password or token. We may request proportionate evidence of your authority, then explain the action taken, any remaining copies and the reason and period for any lawful retention. Copies held by external platforms are handled separately under their policies.
8. Security and processing locations
Passwords are stored as hashes and social-account access and refresh tokens are encrypted in storage. Authentication and authorisation restrict account functions. No service can guarantee absolute security.
External platforms and service providers may process data outside Bulgaria and the European Economic Area. The destinations and applicable transfer arrangements depend on the provider and operation used. Hosting with OVHcloud does not mean that all processing stays in the EU. Contact us for information about the providers handling a particular operation and the applicable transfer safeguards. Any transfer subject to European data-protection law requires a valid basis under that law.
9. Your rights
Where applicable, you can request access, correction, erasure, restriction and portability, object to processing based on legitimate interests, and withdraw consent for processing based on it. Withdrawal does not affect prior lawful processing. The availability of particular rights depends on the purpose and legal basis.
Requests under the GDPR are normally answered within one month. If a permitted extension is necessary, we will explain it within that first month. Contact the operator using the email above.
You may complain to a competent supervisory authority, including the Commission for Personal Data Protection in Bulgaria, or an authority in the EU country where you live or work.
10. Changes
Updates carry a new version date. Material changes will be communicated as required before new processing begins. Business use requiring processing solely on a customer's instructions needs appropriate arrangements before that processing begins.