Privacy Policy

01Scope and service status

This policy covers the PostingZone website and its content-planning demonstration. PostingZone is an early-stage product. The current workspace lets you arrange sample posts, edit captions, and record sample approvals in your browser. It does not create a PostingZone account, connect a social account, run AI generation, or publish a post.

References to future accounts, billing, integrations, or AI processing describe intended handling that must be confirmed before those services are offered. They do not mean those services are operating today. The operator’s legal identity and an operational privacy contact must be supplied before commercial launch.

02Information used by the current website

The local workspace saves the content you enter into its demo, including post titles, captions, scheduling days, approval status, business name, brand voice, brand color, sample account choices, and the model-training preference. These values are stored on the device and browser you use. The application does not synchronize them to a PostingZone database.

The demo login and signup forms do not transmit credentials or create accounts. The waitlist form does not submit or store email addresses. Do not enter a real password, confidential client data, private customer records, or sensitive personal information into a demonstration.

If an operational contact endpoint is configured, submitting the contact form can send your name, email, selected subject, and message to that endpoint. Without an endpoint, the form displays a notice and sends nothing. An enabled endpoint must be identified and covered by this policy before it receives personal data.

03Technical data and external requests

Serving a web page necessarily involves network requests. The hosting and access providers may receive an IP address, request time, requested URL, browser details, and information needed for access control or abuse prevention. Their own notices govern provider-level account and session processing. PostingZone does not currently operate its own application analytics dashboard or advertising tracker.

Fonts are served from this website, so displaying text does not require a font request to Google. The Pexels photographs are served as optimized files from the site, rather than as embedded Pexels trackers. Clicking an external social profile or future payment link takes you to a separate service with its own data practices.

04Purposes and legal bases

Local storage supports the demonstration and remembers your display and workflow choices. A configured support channel would use the information you provide to answer your request. Hosting request processing supports delivery, access, and protection of the website.

Where data protection law requires a legal basis, the operator must identify the applicable basis for each actual activity. Depending on the activity and law, these may include providing a requested service, legitimate interests in site security, legal obligations, or consent for optional uses. Optional marketing or nonessential tracking must not be bundled into a required service without the applicable lawful basis. No particular jurisdiction or blanket consent is assumed by this draft.

05Future account and content processing

Before a live service launches, this notice must identify account details, workspace members, uploaded media, prompts, generated outputs, review history, publishing instructions, platform identifiers, and other information it will actually process. Payment providers may handle billing details and transaction references; payment card entry should take place in the payment provider’s interface.

If a business submits personal data about other people, the business must have authority to do so. The respective controller and processor roles, instructions, security commitments, and deletion arrangements must be set out in an appropriate agreement where required. The browser-local demo does not establish a hosted customer-data processing arrangement.

06AI processing and training preferences

No AI provider receives your prompts or media through the present demo. The “keep my content out of AI training” control is a locally stored preference, not an implemented provider-side enforcement mechanism.

Before generation is enabled, PostingZone must disclose the providers involved, what they receive, their retention and training terms, and how a training preference is enforced. Do not assume that generated material is private, accurate, unique, or suitable for publication until the applicable service settings and terms have been confirmed.

07Sharing and service providers

The current application includes no feature that sells browser-local demo content or shares it with advertising networks. Providers necessary to deliver the site may process technical requests. Planned payment processing and future AI or social integrations must be assessed individually before activation.

Where information is actually held by an operator, disclosure may also be required by law, needed to address abuse or a security incident, or involved in a business transfer. Any such disclosure must have an applicable lawful basis and be limited to what is necessary. Shared-workspace access must be explained before collaborators can see customer content.

08Retention and deletion

Browser-local demo content and the theme preference remain until you clear them, reset the demo, or your browser removes site data. They have no application-defined expiry. Reset demo data restores the sample workspace; it does not clear the separate theme preference or hosting-session cookies.

Production retention periods have not been finalized. A proposed target of deletion within 30 days after account deletion is a design target, not a current guarantee. Before launch, the operator must document active storage, backups, logs, support records, billing records, legal holds, and exceptions. A local reset cannot delete information retained independently by a hosting or payment provider.

09Your choices and privacy rights

You can change demo preferences in the workspace, reset its sample data, or clear the site’s storage in your browser. Depending on the law that applies and the processing involved, you may also have rights to access, correct, delete, receive a portable copy, restrict processing, object, or withdraw consent. These rights are subject to their applicable conditions.

A privacy request should identify the information or activity concerned and a way to reply. Do not include passwords, full payment details, or unrelated identity documents. A working request channel, proportionate identity verification, and legally applicable response deadlines must be established before personal data is collected commercially. You may have a right to complain to the relevant supervisory authority.

10International processing and safeguards

Website delivery and external resource requests can involve infrastructure in different countries. Provider locations and contracts must be verified before representing that data stays in a particular country.

Where a restricted international transfer occurs, the operator must establish an applicable transfer mechanism and any necessary assessment or additional safeguards. This page does not claim an adequacy decision, standard contractual clauses, a specific data-residency region, or a completed transfer assessment.

11Children and sensitive information

PostingZone is intended for adults managing business or creator content. It is not designed as a service for children or for storing highly sensitive personal records. Avoid submitting health details, identification documents, financial account credentials, or information about children to the demo.

If personal information is inadvertently sent to an operational channel, describe the concern through that channel so it can be assessed. Removing browser-local information requires clearing the relevant browser storage.

12Updates and related policies

The date above identifies this revision. This policy must be updated before new collection, optional tracking, AI processing, or live integrations are enabled. Material changes affecting existing service users must be communicated through an appropriate operational channel.

Read the Cookie Policy for storage controls and Security for the distinction between current behavior and launch requirements. Operator details and the contact route remain subject to owner confirmation.