Privacy policy

Last updated: 15 October 2026

This explains how WebCourtyard handles information when you create websites or use features hosted on them. WebCourtyard is operated by Jedakiah Simonenko. For privacy questions or requests, email jedakiah.simonenko@gmail.com.

Information we collect

• Google sign-in: your Google account identifier, name, email address, verification status and profile picture, when supplied by Google. We use basic profile permissions. We do not receive your Google password or request access to your Gmail messages.
• Guest access: a browser-bound identifier and, on participating websites, the display name you enter. Browser storage and session cookies help recognize you. Clearing them or changing browsers can lose access to a guest identity.
• Website creation: your prompts, editing requests, generated page code, saved websites, media uploads, favourites and associated settings.
• Website participation: information you submit to features such as event attendance, topic suggestions, votes, bookings or contact forms, together with identity and ownership information needed to operate those features.
• Technical information: network and request information handled by our hosting services, and operational logs needed to run the service and investigate errors.

Why we use it

We use this information to generate, save and publish websites, recognize users, preserve guest activity when an account is linked, enforce ownership and administrator permissions, operate requested website features, and respond to support or privacy requests.

Where data-protection law requires a legal basis, we rely on providing the service you request and our legitimate interests in keeping it secure and reliable. We rely on consent where required for optional connections or other optional processing. Google sign-in is optional where guest access is offered; granting Google permissions does not authorize unrelated marketing or unlimited use of your information.

What can be public

Published websites and their descriptions may be publicly accessible. Community features may display participants’ names, suggestions, attendance and vote totals. A website’s configuration determines which submitted fields are available to visitors or administrators; do not assume a submission is confidential unless that feature clearly provides private handling. Avoid placing confidential information in prompts or public submissions.

Creators of hosted websites decide the purposes and content of their own sites. They are responsible for explaining any additional uses of visitors’ information. Contact the relevant site organizer for questions about their activities, or contact WebCourtyard for questions about the hosting platform.

Service providers and external content

We use Amazon Web Services for hosting and persistent storage, Google for optional sign-in, and OpenAI for AI generation. Prompts, editing requests and existing page code may be sent to OpenAI to produce or revise a website. OpenAI’s API documentation states that API data is not used for model training by default; its own retention and processing rules also apply. See OpenAI’s API data controls, AWS’s privacy notice and Google’s privacy policy.

Generated sites may include external maps, fonts, images or other services selected by their creator. Loading that content can send your network and browser information to the provider. Those services have their own privacy rules.

Providers may process information outside your country. Applicable data-transfer requirements and provider arrangements govern that processing. Contact us for information about the arrangements relevant to your data. We may also disclose information when legally required or necessary to protect the service and its users.

Cookies and browser storage

We use session cookies and browser storage to maintain sign-in, guest identity and workspace state. These support the functionality you request. Google and embedded third-party content may use their own cookies or storage. You can clear storage or adjust your browser settings, but doing so may sign you out or lose access to guest activity.

How long information is kept

Website history keeps up to 10 recent unpinned versions and 3 pinned checkpoints. Older unpinned versions are rotated out, and history is removed when the saved website is deleted. Additional storage limits can reduce the number of recent versions retained. History stores website source and configuration, not a backup of attendance, votes or form submissions. It is available through the creator’s workspace rather than the public gallery.

Saved websites and participation data remain while the associated site or feature is operated, unless removed through available controls or a validated deletion request. Signing out or clearing cookies does not delete stored contributions. Some deletion controls archive records rather than immediately purging them, and there is currently no fixed automatic purge schedule for those archived records. We consider ongoing service needs, security, outstanding requests and applicable legal obligations when deciding what must be retained. Hosting backups, operational logs and AI-provider records follow their respective retention arrangements.

Your choices and rights

You can use available controls to edit or withdraw contributions, sign out, and revoke Google access in your Google account settings. Depending on the laws that apply, you may request access, correction, deletion, restriction, portability or object to certain processing. Where processing relies on consent, you can withdraw it without affecting earlier lawful processing.

Send requests to jedakiah.simonenko@gmail.com. We may need enough information to verify your identity and locate the records; a lost guest identity can make that difficult. We will handle requests within the applicable legal time limits and explain any lawful reason a request cannot be fully fulfilled. You can also complain to the data-protection authority where you live; UK users can contact the Information Commissioner’s Office.

Updates

We will publish changes on this page with an updated date and provide additional notice where appropriate for material changes.