WRLDGATE
LIVECreate World Account

Part II · Pre-Launch Draft v2.0

Privacy Policy

Last Updated: August 15th, 2026 · Effective Date: [DATE]

Pre-launch draft — not in effect

This is a working draft prepared for product, engineering, safety, privacy, and outside-counsel review. It is not published legal documentation and does not bind WRLDGATE or any user.

13 unresolved decisions are marked in the text below. Each must be resolved before publication.

This Privacy Policy explains how [WRLDGATE LEGAL ENTITY NAME] processes personal information in connection with WRLDGATE websites, accounts, WorldCards™, Worlds, VYRON™, and related services.

The final version of this Privacy Policy must reflect actual production practices.

1Information You Provide

Account Information

Depending on the final account system, WRLDGATE may process:

  • email address;
  • account identifier;
  • authentication information;
  • account creation information;
  • account recovery information; and
  • information needed to authenticate or secure your account.

ENGINEERING VERIFICATION REQUIRED: Confirm whether WRLDGATE processes passwords, passkeys, phone numbers, social-login identifiers, identity-verification information, or other authentication data.

Handle and WorldCard Information

WRLDGATE may process:

  • @handle;
  • display name;
  • profile image;
  • biography;
  • links;
  • WorldCard information;
  • World information; and
  • other fields you choose to provide.

Some of this information may be public.

User Content

WRLDGATE may process content you submit, including:

  • posts;
  • discussions;
  • comments;
  • media;
  • files;
  • links;
  • World content;
  • reports;
  • feedback; and
  • communications supported by the Service.

Communications With WRLDGATE

When you contact WRLDGATE, we may process the contents of your communication and information reasonably necessary to respond.

2Information Generated Through Use

Depending on implementation, WRLDGATE may receive or generate:

  • IP address;
  • browser type;
  • device type;
  • operating system;
  • timestamps;
  • session information;
  • authentication events;
  • security events;
  • pages or features accessed;
  • interactions with the Service;
  • referring pages;
  • crash information;
  • error logs;
  • diagnostic information;
  • approximate location inferred from IP address; and
  • performance information.

ENGINEERING VERIFICATION REQUIRED: Produce a production data inventory. Categories not actually collected must be removed, and omitted categories actually collected must be added.

3Public Information

Certain information may be made public when a user chooses or is informed that the relevant field is public.

Public information may include:

  • handles;
  • display names;
  • profile images;
  • public WorldCards;
  • public Worlds;
  • biographies;
  • links; and
  • public User Content.

FOUNDER + ENGINEERING DECISION REQUIRED: Define which fields are:

  • required;
  • optional;
  • public by default;
  • private by default;
  • discoverable within WRLDGATE; and
  • indexable outside WRLDGATE.

4VYRON™ and AI Information

When you use VYRON, WRLDGATE may need to process:

  • prompts;
  • questions;
  • uploaded files;
  • content intentionally provided to VYRON;
  • conversation context;
  • outputs;
  • tool/action requests;
  • interaction metadata;
  • safety signals;
  • account context where enabled; and
  • technical information necessary to provide the feature.

The final policy must specify the actual VYRON architecture.

Before launch, WRLDGATE must determine:

  • whether prompts are stored;
  • whether outputs are stored;
  • whether history exists;
  • retention periods;
  • deletion controls;
  • whether conversations are linked to accounts;
  • whether VYRON uses memory;
  • whether conversations are used for personalization;
  • whether prompts or outputs are used to improve WRLDGATE;
  • whether prompts or outputs are used for model training;
  • whether providers may use them for their own training;
  • whether humans may review conversations;
  • when human review may occur;
  • which AI providers receive information;
  • whether routing between providers occurs;
  • whether sensitive information is restricted;
  • safety-monitoring practices;
  • logging;
  • audit records; and
  • international transfers.

WRLDGATE must not state that VYRON information is “private,” “confidential,” “never reviewed,” “never stored,” “never used for training,” or “deleted after X days” unless those claims are supported by the actual system and vendor agreements.

5How WRLDGATE Uses Information

Depending on the implemented system, WRLDGATE may process information to:

Provide the Service

Including to:

  • create accounts;
  • authenticate users;
  • reserve handles;
  • maintain World IDs;
  • display WorldCards;
  • operate Worlds;
  • deliver requested functionality;
  • provide VYRON;
  • maintain sessions;
  • process requests; and
  • provide customer support.

Secure WRLDGATE

Including to:

  • detect suspicious activity;
  • protect accounts;
  • investigate compromise;
  • detect fraud;
  • prevent malware;
  • enforce access controls;
  • detect platform manipulation;
  • investigate abuse; and
  • maintain service integrity.

Personalize Features

Where implemented and disclosed, WRLDGATE may use information to provide:

  • remembered settings;
  • recommendations;
  • relevant World discovery;
  • personalized VYRON interactions; and
  • other personalized functionality.

FOUNDER DECISION REQUIRED: Identify every personalization input and output before publishing final language.

Understand and Improve WRLDGATE

Where implemented, WRLDGATE may use information to understand:

  • feature usage;
  • reliability;
  • errors;
  • product performance;
  • adoption;
  • user experience; and
  • platform health.

Enforce Rules

Information may be processed to investigate and enforce:

  • Terms of Service;
  • Community Guidelines;
  • copyright rules;
  • handle rules;
  • security rules;
  • fraud restrictions; and
  • other applicable policies.

Comply With Law

Information may be processed when reasonably necessary to:

  • comply with applicable legal obligations;
  • respond to valid legal process;
  • protect legal rights;
  • address emergencies;
  • preserve evidence; or
  • protect users or others from serious harm.

6Legal Bases Where Required

Where laws such as the GDPR require a lawful basis, the final Privacy Policy must identify the applicable basis for relevant processing.

Potential bases may include, depending on actual processing:

  • performance of a contract;
  • legitimate interests;
  • compliance with legal obligations;
  • consent; or
  • another basis permitted by applicable law.

COUNSEL REVIEW REQUIRED: Do not publish generic lawful-basis language without mapping each material processing purpose.

7How Information May Be Disclosed

Service Providers and Processors

WRLDGATE may use service providers supporting functions such as:

  • hosting;
  • infrastructure;
  • databases;
  • authentication;
  • email;
  • security;
  • content delivery;
  • analytics;
  • customer support;
  • error monitoring;
  • storage; and
  • AI functionality.

Providers should receive information only as appropriate for their functions and applicable contractual/legal arrangements.

FOUNDER + ENGINEERING + COUNSEL REQUIRED: Maintain an authoritative production vendor and subprocessor inventory.

At Your Direction

Information may be disclosed when you:

  • intentionally publish it;
  • share it;
  • connect another service;
  • enter an external destination;
  • authorize an integration;
  • instruct VYRON to perform a supported action; or
  • otherwise direct WRLDGATE to make a disclosure.

Legal and Safety Reasons

WRLDGATE may preserve or disclose information where reasonably believed necessary to:

  • comply with applicable law;
  • respond to valid legal process;
  • address serious safety risks;
  • investigate fraud;
  • investigate security incidents;
  • enforce WRLDGATE rules; or
  • protect WRLDGATE’s legal rights.

Business Transactions

Information may be transferred as permitted by law in connection with:

  • a merger;
  • financing;
  • acquisition;
  • restructuring;
  • bankruptcy;
  • sale of assets; or
  • similar corporate transaction.

Where required, appropriate notice will be provided.

8Sale, Sharing, Targeted Advertising, and Data Commercialization

FOUNDER + COUNSEL DECISION REQUIRED.

The final policy must state whether WRLDGATE:

  • sells personal information as defined by applicable law;
  • shares personal information for cross-context behavioral advertising;
  • uses targeted advertising;
  • uses advertising networks;
  • uses audience measurement;
  • personalizes ads;
  • uses World activity for advertising;
  • uses WorldCard information for advertising; or
  • uses VYRON interactions for advertising.

WRLDGATE must not publish a broad statement such as “we never sell your data” until each production vendor and data flow has been evaluated against applicable definitions.

Where required, WRLDGATE must provide applicable opt-out methods and recognize legally required preference signals.

9Cookies and Similar Technologies

WRLDGATE may use cookies or similar technologies for:

  • essential functionality;
  • authentication;
  • security;
  • session management;
  • preferences; and
  • other implemented purposes.

Analytics, advertising, behavioral profiling, or optional third-party cookies should not be represented as active unless actually implemented.

See the WRLDGATE Cookie Policy.

10Data Retention

WRLDGATE intends to retain personal information for periods reasonably connected to the purpose for which it is processed and legitimate security, legal, safety, fraud-prevention, and operational requirements.

FOUNDER + ENGINEERING + COUNSEL REQUIRED: Establish a documented retention schedule covering:

  • active accounts;
  • deleted accounts;
  • authentication records;
  • consent records;
  • IP/security logs;
  • VYRON interactions;
  • World records;
  • WorldCard records;
  • handle history;
  • moderation records;
  • reports;
  • appeals;
  • deleted content;
  • support communications;
  • analytics;
  • legal holds;
  • fraud records; and
  • backups.

Do not state specific retention periods until they are implemented.

11Account and Content Deletion

WRLDGATE intends to provide eligible users with an account-deletion process.

The final implementation must address:

  • where deletion begins;
  • verification;
  • waiting periods;
  • cancellation during a waiting period;
  • handle release or reservation;
  • Worlds;
  • WorldCards;
  • VYRON history;
  • User Content;
  • public links;
  • backups;
  • fraud/security records;
  • legal holds; and
  • completion timelines.

Certain records may be retained where required or permitted by law or reasonably necessary for security, fraud prevention, dispute resolution, rights enforcement, or other disclosed purposes.

12Privacy Rights

Depending on jurisdiction and applicability, individuals may have rights concerning personal information, which may include:

  • access;
  • correction;
  • deletion;
  • portability;
  • restriction;
  • objection;
  • withdrawal of consent;
  • information regarding processing;
  • opt-out from certain sale or sharing;
  • opt-out from certain targeted advertising; or
  • appeal of certain privacy-request decisions.

Not every right applies in every jurisdiction.

WRLDGATE may verify identity before fulfilling certain requests.

Requests may be submitted through:

[PRIVACY REQUEST URL / PRIVACY EMAIL]

COUNSEL + OPERATIONS REQUIRED: Implement an actual request intake, authentication, response, documentation, and appeal process where required.

13Children’s Privacy

WRLDGATE is not intended for users below its established minimum age.

FOUNDER + COUNSEL DECISION REQUIRED: Establish:

  • minimum age;
  • whether 13–17-year-olds are permitted;
  • jurisdiction-specific rules;
  • whether parental authorization is ever used;
  • neutral age screening;
  • underage-account handling; and
  • deletion procedures.

If WRLDGATE permits children under 13 in circumstances where COPPA applies, additional parental notice, consent, security, deletion, and data-handling requirements may apply.

WRLDGATE must not launch with an ambiguous child-access policy.

14Child Safety

Child-safety reporting and children’s privacy are separate matters.

WRLDGATE may process or preserve information relating to suspected child sexual exploitation or abuse when necessary to:

  • protect children;
  • enforce platform rules;
  • preserve evidence;
  • comply with applicable reporting obligations; or
  • cooperate with lawful authorities.

Access to highly sensitive child-safety material should be restricted to authorized personnel and handled according to dedicated procedures.

15International Users and Transfers

WRLDGATE may process information in countries other than the country where a user lives.

FOUNDER + COUNSEL REQUIRED: Before targeted international expansion, determine:

  • launch jurisdictions;
  • controller identity;
  • processor relationships;
  • storage locations;
  • international-transfer mechanisms;
  • adequacy decisions where applicable;
  • Standard Contractual Clauses where applicable;
  • UK transfer requirements;
  • representatives where required;
  • DPO requirements where applicable;
  • regional lawful bases;
  • regional privacy rights; and
  • regional age requirements.

WRLDGATE must not claim broad GDPR compliance merely because the Service is technically accessible from Europe.

16Security

WRLDGATE intends to use administrative, technical, and organizational safeguards appropriate to the nature of the Service and information processed.

No system can guarantee absolute security.

Specific claims must be verified before publication, including claims concerning:

  • encryption in transit;
  • encryption at rest;
  • password hashing;
  • key management;
  • access controls;
  • MFA;
  • penetration testing;
  • vulnerability scanning;
  • certifications;
  • audit logging;
  • backup encryption;
  • incident response; or
  • security monitoring.

ENGINEERING VERIFICATION REQUIRED.

17Changes to the Privacy Policy

WRLDGATE may update this Privacy Policy as products, technologies, vendors, practices, or legal obligations change.

The effective date will appear above.

Where required, WRLDGATE will provide additional notice or request additional consent for material changes.

Historical versions should be retained where reasonably necessary to establish what disclosures applied during particular periods.

18Contact

Privacy questions and requests:

[WRLDGATE LEGAL ENTITY NAME]

[PRIVACY EMAIL]

[MAILING ADDRESS]

[PRIVACY REQUEST URL]

WRLDGATE™, WorldCard™ and VYRON™ are trademarks, pending trademarks, service marks, or other protected brand assets designated by WRLDGATE.