Last updated: 31 October 2026

Privacy Policy

This Privacy Policy explains how Social Publishing Studio handles information in connection with the creation and publication of original social-media content, including content produced for the 8 Ways to Wear project.

1. Who operates the app

Social Publishing Studio is operated by Antonio Malafronte, with an address at Via Gioacchino Murat 88, Torre Annunziata, Italy.

Privacy questions and rights requests should be sent to tonymalafronte10@gmail.com.

2. Information we collect

The current Cloudflare Pages media archive is a static site. It does not currently implement TikTok Login Kit, a social OAuth callback, analytics, advertising pixels, or an application database for social-account credentials. Visitors can view the archive and legal pages without creating an account or submitting a form.

The repository's publication and generation registries contain editorial metadata such as dates, garment and colour names, image paths, hashes, captions, platform statuses, deployment IDs, URLs, and timestamps. They do not contain OAuth tokens, passwords, social-account identifiers, or visitor-submitted personal data.

If Social Publishing Studio is connected to TikTok or another platform in the future, it may receive the account and authorization data made available through the relevant official login flow, such as a platform user identifier, display information, scopes granted, access-token metadata, and refresh-token metadata. The exact fields will depend on the approved scopes and the integration actually enabled.

Social Publishing Studio does not request passwords. Any future OAuth tokens must be handled server-side, used only for the authorized publishing operation, and never placed in public source files, page content, logs, or the media manifest.

3. How information is used

• to authenticate an account when an official social login integration is enabled;
• to prepare, submit, and monitor publication requests that the account owner has authorized;
• to prevent duplicate submissions and record non-sensitive publication outcomes;
• to respond to support, security, or legal requests.

The app does not sell personal information and does not use social-account data for unrelated advertising or profiling. The repository also contains an inherited Verde Studio enquiry form and D1 schema that can handle names, email addresses, phone numbers, company and city details, messages, consent, and uploaded photos. That separate Verde Studio surface is not part of the Social Publishing Studio media archive or its current static Pages deployment.

4. Content and external services

Users remain responsible for the content they provide or authorize for publication. Images for 8 Ways to Wear are intended to be original editorial assets. The media archive is hosted on Cloudflare Pages at outfits.verdestudio.me.

The project is configured to use Codex/ChatGPT ImageGen for image creation, not a paid AI API. The repository contains no Cloudinary integration or third-party social automation service. TikTok, Instagram, Facebook, Pinterest, and their APIs may process content and account data under their own policies when an official integration is enabled.

5. Retention and deletion

No automatic deletion procedure or fixed retention period is currently implemented for Social Publishing Studio. Published media should normally remain available while the public 8 Ways to Wear archive is intentionally maintained. The current operational recommendation is to review published assets and non-sensitive publication records every 24 months, delete failed or obsolete temporary copies within 30 days, and retain an asset only while it serves an active editorial, legal, or accounting purpose. These are proposed governance periods, not automated controls, and require Antonio Malafronte's confirmation before being represented as a binding schedule.

To request deletion of information held by Social Publishing Studio, email tonymalafronte10@gmail.com. At present, deletion must be handled manually because no self-service deletion workflow is implemented. A user can also revoke an app's authorization through the relevant platform. Revocation may not remove content already published to a platform.

6. Security

The repository contains no OAuth tokens, passwords, or social credentials. Public media is served over HTTPS, and the media manifest exposes only editorial paths, hashes, URLs, and non-sensitive publication metadata. No additional security certification, encryption architecture, deletion control, or monitoring guarantee is claimed beyond the controls actually configured in the deployed environment. Any future OAuth implementation must use server-side secret storage, least-privilege scopes, HTTPS, access controls, and auditable error handling.

7. Your rights

Depending on applicable law, you may have rights to access, correct, delete, restrict, or object to processing of your personal information, and to withdraw consent where processing is based on consent. Contact tonymalafronte10@gmail.com to exercise a right. You may also complain to your local data-protection authority.

8. Changes

We may update this policy when the app, integrations, or legal requirements change. The revised version will be posted at this URL with a new “Last updated” date.