Privacy Policy

Who operates Wholething

Confirm the legal operator’s full name, business address and country; privacy contact email; and its role when processing material for clients.

Information we handle

• Inquiries: the name, business name and email address entered in the public contact form.
• Business and account information: account details, business questionnaire answers, brand information, notes, links, uploaded documents and communications supplied for the service.
• Content: uploaded photos and videos, captions, drafts, creative plans, schedules, publication results and links, research, strategy and brand-book material.
• Connected-account information: platform identifiers, profile names and images, authorization tokens and expiry information, and available post or account statistics for authorized features.
• Operational information: session and authentication records, service errors and technical information used to operate the service. Confirm hosting/access-log fields and retention, questionnaire fields and any additional tracking.

Social-account connections

Wholething uses Postiz-based software to connect authorized social accounts and prepare, schedule and publish content. Connections include YouTube, X, Facebook and Instagram. TikTok integration is being prepared for approval and is not yet available as an approved production integration.

Account authorization takes place through the social platform’s authorization flow. The application stores access tokens and, where issued, refresh tokens so it can perform authorized actions and renew access. These tokens are different from a social-network password.

The TikTok implementation requests basic and extended profile information, account statistics, video listings, direct publishing and upload permissions. It can retrieve profile identifiers, display name, username, avatar, follower/following and like/video counts, video identifiers and performance counts. Reconcile this description with the final approved and deployed TikTok scopes before publication.

YouTube features use YouTube API Services. Google’s handling of information is described in the Google Privacy Policy.

How information is used

The service uses business materials to understand a client’s business, prepare research and strategy, plan and create content, coordinate work, show content schedules, and publish to authorized channels. Account information supports access control, client separation and support. Connected-account data supports account selection, publishing and available analytics.

Confirm applicable legal bases, marketing uses, and whether any additional uses occur outside the application.

Service providers and sharing

• Hostinger: hosts the public website and the existing questionnaire.
• Convex: receives public contact-form submissions. Confirm downstream recipients, access and retention.
• DigitalOcean: hosts the application, its database and uploaded files on the current Amsterdam deployment.
• OpenRouter and selected AI model providers: process material included in AI requests for research, strategy and creative features. Confirm the enabled providers, information sent, retention and model-training settings; no promise that providers never train on data has been established.
• Connected social platforms: receive content and publishing instructions when those features are used, and provide information permitted by the account authorization.

Confirm staff/contractor access, other vendors, international-transfer arrangements, legal disclosures, and whether information is sold or shared for advertising. These statements cannot be inferred from the code.

Storage and security

The deployed application uses a database and server-side file storage. Client portal uploads and business research files are stored separately from publishing media. Publishing media can be available through a URL so the connected platforms can retrieve it; it should not be treated as a private document store. The service uses HTTPS and authenticated access for protected application features.

Backups and retained files can contain information no longer visible in the application. Confirm all backup locations, authorized access, security commitments and international processing locations before this policy becomes effective.

Cookies and browser storage

The application and client portals use cookies for sessions and preferences. The website’s inquiry form temporarily stores a pending submission in browser session storage so a retry can be recognized; it removes that entry after a successful submission. The application also uses browser storage for preferences such as timezone.

Confirm any Hostinger/CDN cookies, questionnaire sessions, analytics, advertising pixels or optional integrations. The inspected homepage contains no external script tags; that alone does not establish a service-wide absence of tracking.

Retention

Confirm retention periods or criteria for inquiries, questionnaire answers, accounts, social tokens/API data, media, drafts and published-post records, research/AI conversations, logs and backups, including what happens when the client relationship ends.

Removing a channel in the current application marks its record as deleted. It does not by itself erase stored tokens, historical content or backup copies. Disconnection and deletion are separate actions.

Disconnecting a social account

An authorized staff member can remove a connected channel in Wholething. Account owners can also revoke the application’s permission through the relevant social platform’s connected-app settings. YouTube users can revoke access through Google’s security settings.

Revoking authorization prevents continued use of that permission. It does not erase Wholething’s stored copies or remove posts already published on the social platform. Requests to erase Wholething’s stored data are handled separately.

Confirm the client-facing support route for disconnection and the operational process for cancelling queued/in-progress jobs and removing credentials.

Deletion and privacy requests

Confirm a monitored privacy/deletion email, request-verification process, responsible operator and response/deletion deadlines. Specify the data actually erased, retained records and reasons, vendor requests, and treatment of backup restoration. Do not publish an unimplemented deletion promise.

Deleting information held by Wholething does not delete content or account information held independently by a social platform. To remove a published post from a social network, use that network’s controls or a supported authorized deletion feature.

Age, privacy rights and changes

Confirm the minimum age, applicable jurisdictions and rights/request routes, complaint contact or regulator where required, and how material policy changes will be communicated.