Who this policy covers
This policy describes the EzGathr team's handling of information on this demonstration website, including product exploration, demo accounts, planning tools, and inquiries. Reach the team responsible for the site through our privacy contact form.
Information you provide
- Inquiries: your name, email, optional organization, selected topic, and message, including investor and privacy inquiries.
- Demo activity: details you enter in gathering drafts, registrations, venue requests, listings, uploaded photos, and other available workflows, together with account identifiers and action history.
- Demo profiles: choosing a demo profile on the sign-in page creates a new account for you: a fresh copy of a sample account. Anything you do with it — a listing you publish, a gathering you post — is real, shared data other visitors can find through ordinary search, exactly as if it were any other listing or gathering on the site.
- Planning tools: checklist progress and venue comparisons. Optional browser saving keeps these on your device. Following a generated search link sends its search criteria to the site; downloading or sharing a comparison creates a separate copy you control.
Some demo sign-in options are shared test identities that other people using the same account, or an authorized workspace role, may see activity on; a demo profile you start yourself is your own account, not shared with other visitors at the same time, though what you do with it can still become visible to others through search, exactly as described above. Use fictional details in every demo workflow. Do not upload real guest lists, private addresses, payment card details, identity documents, sensitive personal information, or photos of people without permission. Your contact inquiry may contain real reply details; keep its message limited to what we need to respond.
Information collected when you visit
The site and its hosting services process technical information such as IP address, requested pages, browser or device information, timestamps, errors, and request identifiers to deliver the site, investigate problems, and limit abuse. Cookies support sign-in, form security, and temporary status messages. Our Cookies & browser storage policy explains these and the optional local saving tools.
How we use information
We use information to operate and evaluate the demo, preserve workflow state, respond to inquiries, troubleshoot failures, protect accounts and services, and meet applicable legal obligations. An investor inquiry is used to handle that conversation. Registration, RSVP, venue interest, and contacting us are not consent to unrelated marketing.
Who can receive information
- The EzGathr team and service providers supporting hosting, storage, diagnostics, and site operation, as needed for those tasks.
- People with access to the relevant demo account or workspace. Published listing or gathering content may be visible to visitors; anyone with an unlisted page link can pass it on.
- Authorities or other recipients when disclosure is required by law or necessary to address fraud, abuse, or threats to rights and safety.
The current demo does not include advertising trackers or a feature that sells personal information or shares it for targeted advertising.
A public demo activity endpoint exposes inquiry record identifiers, topic categories, timestamps, and processing status. It excludes your name, email, organization, and message.
Pages with maps request map images directly from OpenStreetMap's servers. Those requests expose your IP address and browser request information to that provider. See the OpenStreetMap Foundation privacy policy. Other external sites you choose to visit apply their own policies.
Retention and security
Demo records may remain until they are changed, removed, or the demo is reset. Some deployments of this demo reset on a recurring automatic schedule, clearing demo profiles and what they created and starting the demo fixtures over; where that applies, the sign-in page states roughly when. This is a housekeeping measure for a demo environment, not a data-deletion service you can rely on for a specific record, and not every deployment runs it. Contact inquiries and operational records may be retained for follow-up, troubleshooting, security, and applicable legal needs; this demo does not have a published fixed retention period. Browser-saved planning data remains until you remove it or your browser clears it. Backups and logs may have separate retention cycles.
We use technical controls to restrict access and protect the site, but no system can guarantee security. Shared demo accounts are unsuitable for confidential information. Service providers may process information outside your state or country; this policy does not promise storage in a particular region.
Your choices and requests
You can browse public pages without signing in, leave optional fields blank, and disable or remove browser-saved planning data. Use the privacy contact form to request access, correction, or deletion of information you submitted. Identify the relevant email, page, or activity without sending identity documents. We may need proportionate verification before acting.
Depending on where you live and which laws apply, you may also have rights to obtain a copy of your data, object to or restrict certain processing, withdraw consent, or appeal a decision on a request. We will handle applicable rights and response deadlines as required by law. To ask us to reconsider a response, use the same form and identify the earlier request. You may also contact your relevant privacy regulator. Removing a saved copy in your browser does not delete server records or copies you shared with others.
Children
The demo is intended for adults aged 18 or older and is not directed to children under 13. Do not submit children's personal information. If you believe a child has provided personal information, contact us so we can investigate and arrange appropriate removal.
Changes
We will update the date above when this policy changes. Material changes to data use will be explained on the site, and additional notice or consent will be provided where required. A live service may need different disclosures before it launches.