Privacy Policy
Last updated: October 8, 2026
Who is responsible
Moore World Wide Enterprises, LLC, doing business as gigiii, is the controller for the processing described here.
2102 Quail Hollow Dr Bryan, Texas 77802 United States Represented by: Judson Moore, President & CEO Contact: hello@gigiii.com
EU representative (Article 27 GDPR): Judson Moore Contact: gdpr@gigiii.com
This notice applies to website visitors, people who previously submitted registration interest, members, public-event visitors and people who contact us. The separate Data Protection Roles and Limited Processor Terms explain the exceptional, limited circumstances in which gigiii may process data solely on a member's documented instructions.
Location suggestions
When profile location fields are empty, we use approximate country and city metadata supplied by our hosting provider from your internet connection to suggest a location. Our legitimate interest under Article 6(1)(f) GDPR is to make profile setup easier with minimal data. The country is editable; the city is not saved as your base until you select it. The suggestion is used for the current form only, without a separate IP or inferred-location record, tracking cookie or device GPS access. A suggested city is sent to our place-search provider only when you choose to search for it. Existing profile locations are preserved.
Data we process
| Category | Examples |
|---|---|
| Account and authentication | Name, email address, authentication-provider details, account role and session data. |
| Profile and marketplace | Profile descriptions, professional location, capacity, pricing, technical requirements, portfolio items and contact methods. |
| Bookings and events | Applications, requests, agreed terms, availability, holds, agreement and signature metadata, RSVP name/email/party size, and ticket-order metadata. gigiii does not receive card numbers. |
| Communications and support | Notifications, support requests, chat messages, problem reports and related metadata. Authorised problem reports may be copied to private GitHub Issues for triage. |
| Technical and security | IP address, browser and device information, server logs, cookies, session/security data and error/performance telemetry. |
| Location and forms | Place-search or address query data, map requests, and public contact form fields, previously submitted registration-interest fields, and anti-abuse data. |
| Consent and marketing | Cookie choices; consented advertising click and browser identifiers, public event/conversion data and widget context; and, where separately opted in, email, name, user ID, role/group and marketing-subscription state. |
The service is for adults and is not directed to people under 18. We do not knowingly collect children's data.
Why we process data
| Purpose | Legal basis | Retention |
|---|---|---|
| Account, authentication, profile, booking, RSVP and event services | Article 6(1)(b) GDPR | For the account or service relationship. An incomplete signup that has not accepted the Terms and this notice is anonymised after 7 days. |
| Operational notifications | Articles 6(1)(b) and 6(1)(f) GDPR | Read in-app notifications are eligible for deletion after 90 days. Completed email-outbox records are retained for 30 days; failed records for 90 days. |
| Loading optional Tawk.to support chat and its browser storage | Article 6(1)(a) GDPR and consent under Section 25(1) TDDDG | The widget stops loading when you withdraw Functionality consent. Tawk.to's visitor identifier may last up to six months; connection cookies last for the session. Accessible first-party cookies are cleared on withdrawal where possible. |
| Responding to support-chat messages you send | Article 6(1)(b) GDPR for support related to your account and our service | Tawk.to says chat records remain on its servers until deleted; it does not publish a fixed automatic expiration period. You can request deletion through the privacy contacts below. |
| Security, abuse prevention, moderation, error monitoring and service reliability | Article 6(1)(f) GDPR, our legitimate interest in a safe and reliable marketplace | For the period needed for the relevant purpose and the applicable log/provider-retention setting. |
| Legal, tax, accounting and claims records | Articles 6(1)(c) and, where needed, 6(1)(f) GDPR | For the applicable statutory retention or limitation period. |
| Consent-based analytics and host-owned GA4 on applicable public-event surfaces | Article 6(1)(a) GDPR and, where applicable, consent under national cookie law | Until consent is withdrawn or the provider's configured retention period expires. |
| Organizer advertising measurement on public event pages | Article 6(1)(a) GDPR and, where applicable, consent under national cookie law | Until consent is withdrawn or the organizer/provider's configured retention period expires. Requires separate Analytics and Marketing cookie choices. |
| Marketing emails | Article 6(1)(a) GDPR | Until consent is withdrawn or the marketing record is deleted under the provider's retention process. |
Account and booking data are needed for the relevant marketplace function. If you do not provide them, we may be unable to create an account, publish a profile or process a booking. Analytics, marketing and support chat are optional.
We do not make decisions based solely on automated processing that produce legal or similarly significant effects.
Recipients
We do not sell personal data. We disclose it only to:
- approved members, where necessary for the requested discovery, booking or RSVP feature. A member receiving disclosed information normally acts as a separate controller for its own use;
- event organizers and their advertising providers, only when the visitor has accepted Analytics and Marketing for organizer-controlled advertising tags on public event pages;
- the providers listed on Sub-processors and Service Providers, for hosting, database, authentication, file storage, email, anti-abuse, maps, diagnostics, analytics and operational support;
- pretix and the seller of record for paid tickets. The seller chooses any payment provider in pretix; gigiii neither selects that provider nor handles card payments; and
- public authorities or other recipients where disclosure is required by law or necessary to protect rights and safety.
International transfers
Some providers process data outside the EEA, including in the United States. Where required, we use an adequacy decision, EU Standard Contractual Clauses or another safeguard under GDPR Chapter V. Provider-specific location and transfer notes are available on Sub-processors and Service Providers. You may ask us for information about the applicable safeguard.
Account closure and retention
When you close an account, we irreversibly anonymise it rather than offering a routine hard deletion. We unpublish and scrub public profiles, events, contacts, links, media and availability. Confirmed, completed and cancelled booking history, including immutable agreement and invoice records, is retained only in a restricted legal archive where required for legal, accounting or claims purposes.
Your rights
You may request access, rectification, erasure, restriction, portability, or information about recipients and safeguards; withdraw consent at any time; and complain to your local data-protection supervisory authority. Contact gdpr@gigiii.com or hello@gigiii.com. We normally respond within one month.
Right to object
Where we process your data under Article 6(1)(e) or (f) GDPR, you may object at any time on grounds relating to your particular situation. You may object to direct marketing at any time. We will stop the affected processing unless compelling legitimate grounds override your interests, rights and freedoms or the processing is required for legal claims.
Cookies and tracking
We use strictly necessary cookies and device access for authentication, security and form anti-abuse. Optional analytics through Google Tag Manager, Google Analytics 4, Microsoft Clarity and Vercel Analytics / Speed Insights run only with consent. On public event pages, organizer-controlled advertising tags such as Meta Pixel require separate Analytics and Marketing choices. These tags may receive the event URL, click and browser identifiers, and allowlisted conversion details such as the public event ID and RSVP quantity, but not guest names or email addresses from gigiii. Marketing-email consent is separate. See the Cookie Policy.
On signed-in pages, we load Tawk.to for support chat only after you accept the Functionality cookie category. Tawk.to may receive browser and connection data and any information you submit in the chat, and may use cookies or local storage to maintain the conversation. You can withdraw this choice in Cookie Preferences. See the Cookie Policy and Sub-processors and Service Providers.
Changes and contact
We may update this notice and will communicate material changes by email or prominent platform notice. For privacy questions or to exercise rights, contact gdpr@gigiii.com or hello@gigiii.com.
Optional event-news subscriptions
Public RSVP and gigiii-native paid/free ticket forms offer a separate, optional, unchecked choice for gigiii event news and recommendations. Attendance, payment, ticket delivery and required messages do not depend on it. The choice applies only to the submitting email, not additional party members, and is independent of cookie choices. Submitting a valid RSVP or ticket form with a new checked choice subscribes the submitting email to the same gigiii newsletter audience used by account onboarding and settings, without an additional email confirmation, payment or ticket issuance. An abandoned payment does not revoke the newsletter opt-in. Checkout context indicates interest, not a completed purchase. An explicit new choice may renew an earlier newsletter subscription; delivery suppression remains respected. Historical requests retain their original separate email-confirmation requirements.
We retain the normalized email/name, consent purpose and copy version, language, server timestamps, RSVP/order reference, confirmation/withdrawal state, and the event ID/title/city/country for consent evidence and relevant recommendations. Event location describes the event, not your home. Loops receives only the latest submitted event context and permitted contact fields, not attendance access tokens or payment details. Earlier event contexts remain locally. Existing member identity and unrelated lists are preserved. Withdrawal prevents stale requests from re-enrolling you. You can withdraw via the marketing email preference link; leaving a later checkbox unchecked is not a withdrawal. Cancellation or refund does not itself withdraw marketing consent. Historically unconfirmed requests expire after seven days and their evidence is deleted thirty days after expiry. Active context is retained until withdrawal or erasure under our privacy-request process; after withdrawal, retained evidence is restricted to consent/accountability handling and a minimal suppression record prevents stale work from re-enrolling you. Required attendance emails remain independent.
Public traffic sources and campaigns
With Analytics consent, Gigiii measures public profile/event views and sources, campaign labels and their association with confirmed RSVPs and native paid orders. A random first-party session identifier and bounded acquisition context are stored in browser sessionStorage. The session expires after 30 minutes of inactivity; closing the tab also ends its storage. The database keeps source measurements and RSVP/order source snapshots for 90 days, then deletes/clears them through scheduled cleanup. Operational attendance and payment records follow their separate retention policy. Withdrawal clears acquisition storage and stops further tracking; already collected source records remain subject to the 90-day period.
This optional device storage/access uses consent under §25(1) TDDDG; subsequent measurement and source linkage use consent under Article 6(1)(a) GDPR. Referrers are reduced to hostnames. Campaign tags must not contain personal data. This feature does not store raw advertising click IDs or send attendee names/emails, payment credentials or full referrer URLs to analytics. Source context may go to the existing configured Google/event-organizer analytics destinations with Analytics consent, and to Meta only with both Analytics and Marketing consent. Anonymous session IDs stay with Gigiii and its existing Vercel/Neon processors. Owners see aggregates with small-group protections, not attendee-level sources. Host-site widget consent does not grant consent on Gigiii. Provider retention and privacy-rights contacts remain as described in this notice and the provider list. You may decline this measurement and still RSVP or buy tickets.