Scope of this policy
This policy describes the Paypig Meet website in its current form: a static demonstration containing educational pages and non-functional product concepts. It does not describe a future member platform. If accounts, messaging, payments, analytics or other production features are introduced, this policy must be replaced or updated before those features begin collecting personal information.
Who is responsible for the website
The website currently identifies its publisher as Paypig Meet, the name of an independent website project. No separate incorporated company, registered business address or data-controller identity has been disclosed for this demonstration. Those details, together with a direct privacy contact, must be published before the site operates as a live service.
Information the website does not currently collect
The current front-end code does not create member accounts, store profile details, transmit contact-form entries, process payments, set advertising cookies, run analytics tags or save information in browser local storage. The contact form validates entries in the browser and then clears them; it does not send the entered information to Paypig Meet.
Because the form does not transmit data, visitors should not use it for urgent safety reports or assume that a message has been received.
Technical information a hosting provider may receive
Like most websites, the server or hosting provider used to deliver these pages may automatically receive limited technical information such as an IP address, browser type, requested page, referring page, timestamp and security logs. The project files do not identify the current hosting provider or its retention settings, so this policy does not claim a specific retention period.
Before public launch, the operator should identify the hosting provider, document its role, confirm where logs are stored and disclose the applicable retention period.
Cookies, analytics and third-party content
The current website code does not set cookies, load analytics services or embed third-party videos, payment widgets or social-media feeds. Ordinary links may take visitors to another page, but the current site does not disclose information to a third party through an embedded integration.
If any of these technologies are added, this policy and any required consent controls must be updated before deployment.
What a future service would need to disclose
A production community may need to process information such as account identifiers, age or identity checks, profile content, messages, moderation reports, transaction records, device data and support requests. This demonstration does not currently process those categories. A future policy must explain, for each category, why it is collected, the lawful basis where applicable, who receives it, how long it is kept and how users can exercise their rights.
Privacy choices and rights
Because the current website does not maintain visitor accounts or receive form submissions, it does not provide an account-access or deletion tool. Depending on a visitor’s location, privacy law may provide rights concerning information held by a website operator or hosting provider. A working privacy contact and identity-verification process must be established before the site collects information for which such requests may be made.
Security and sensitive information
No website can promise complete security. Visitors should never enter passwords, one-time codes, banking credentials, identity documents or unnecessary intimate information into a demonstration form. Read the safety guide for practical steps to separate identities and reduce exposure.
Adults only
Paypig Meet is intended only for adults aged 18 and older. The current demonstration does not knowingly collect information from anyone, including children. A production service would need an age-assurance process appropriate to its features, audience and legal obligations.
Changes to this policy
The effective date will be updated when the policy changes. Material changes should be explained clearly rather than hidden inside a silent rewrite. This policy must be reviewed again before any account, messaging, moderation, payment, analytics or data-submission feature goes live.
Contact
For privacy questions or requests, email support@paypigmeet.com. Do not include passwords, one-time codes, banking credentials or unnecessary identity documents.