Draft — pending legal review

This page is not yet in force. Acceptance is not required at checkout until Auctor LLC publishes an effective version. Version 2026-08-20-draft.

Privacy Policy

Auctor LLC · Hiroba · Last revised 2026-08-20

1. Who we are

This Privacy Policy describes how Auctor LLC (“Auctor,” “we,” “us,” or “Hiroba”) handles personal information when you use Hiroba at hiroba.io and related APIs.

THIS DOCUMENT IS A DRAFT PENDING LEGAL REVIEW AND IS NOT YET IN FORCE. It is published for transparency and legal review. Contact support@hiroba.io with questions.

Hiroba helps show Organizers manage vendor tables, tickets, floor plans, check-in, and communications. Organizers are independent businesses. When an Organizer emails you about their show, that Organizer is also a controller of the information they hold about you.

2. Information we collect

Organizer accounts: name, email, password (stored by our auth provider), optional phone, website, bio, logo, and Stripe Connect identifiers. Staff invitations use email and role.

Vendors: name, email, optional company, phone, specialty, bio, website, social handles, avatar, table preferences, waitlist notes, and payment-related status for shows. Organizers may store internal notes, ratings, no-show flags, and a “do not invite” flag about Vendors they work with.

Attendees / ticket buyers: name, email, phone (often required by the checkout UI), optional home address (street, city, state, ZIP), ticket records, QR tokens, check-in history, and marketing-consent choices. Address is collected only on the full checkout page (not the embed) and is currently used to store and prefill your profile — not for advertising targeting.

Payments: we store amounts, fees, status, Stripe payment/charge/transfer/refund/dispute identifiers, promo and tracking references, and related descriptions. Card numbers and full payment credentials are collected and stored by Stripe, not by Hiroba.

Usage and device: approximate logs needed to operate the Service (IP address and user agent when you accept legal terms; email delivery events; error reports). Browser local storage holds session tokens, attribution references, favorites, and similar client state listed in Section 8.

Floor plans and venues: layout data, uploaded images, and (if enabled) assistant chat content related to editing a plan.

Waitlist subscribers: if you ask us to tell you when Hiroba opens, we store the email address you give us and, only if you choose to add them, your name, the show or organization you run, and the general area you run shows in. We also record which page you signed up from, a coarse label for how you reached us (for example “search” or “social” — never the referring web address itself), any campaign reference already stored in your browser, and which version of the wording you agreed to. We do not create an account for you, and this record is not linked to any Organizer, Vendor or Attendee record.

3. Sources

We collect information directly from you, from Organizers who invite or register Vendors, from Stripe payment events, from email delivery events (bounces, complaints, deliveries), and from your browser when you use public pages and portals.

4. How we use information

We use personal information to: provide and secure the Service; process purchases, refunds, and payouts; issue tickets and vendor badges; run door check-in; send transactional email; send promotional email only with appropriate consent; prevent fraud and abuse; comply with law; improve reliability (including error monitoring); and communicate about the Service.

We do not sell personal information for money. We do not use attendee home addresses for marketing segmentation in the product today.

6. How we share information

We share information with:

• Organizers — so they can run shows you bought into or applied to (rosters, ticket status, vendor applications, messages).

• Other users where you choose to publish it (for example vendor public profiles on a show page).

• Service providers listed in Section 7.

• Authorities when required by law or to protect rights, safety, and security.

• A successor entity if we undergo a merger, acquisition, or asset sale, subject to this Policy’s standards.

Door volunteers receive only what they need for check-in (names, tables, badge tokens) — not full financial ledgers.

7. Service providers (sub-processors)

• Stripe — payment processing, Connect accounts, disputes, and payouts.

• Amazon Web Services — Cognito (authentication), RDS (database), S3 (files), SES and SNS (email and delivery events), EC2 (API hosting), Amplify/CloudFront (website hosting).

• Sentry — error monitoring. Our browser client is configured to avoid sending default PII and HTTP bodies, and to scrub credential-bearing URL tokens (including volunteer door links and unsubscribe tokens). Server-side error monitoring may include request context needed to diagnose failures; we minimize what we send where practical.

• Google Maps Platform — address autocomplete when Organizers enter venue or event addresses (not used for attendee home-address entry).

• Anthropic — floor-plan assistant. When that feature is enabled, organizer plan context and chat instructions are sent to Anthropic to propose edits. The feature may be disabled until we configure it; we disclose it here so turning it on does not expand processing without notice.

Providers may only process data as needed to provide their services to us.

8. Cookies and local storage

Hiroba’s own auth uses tokens in browser local storage rather than first-party advertising cookies. Examples include: organizer Cognito token; vendor and attendee portal session tokens; tracking attribution (smatic_track_ref, typically 7 days); favorites (smatic_favs_*); offline check-in queue data; and UI preferences.

Third parties such as Stripe Checkout, Google Maps, and Sentry may set their own cookies or similar technologies when their components load. We do not operate a Meta Pixel or similar advertising pixel in the product.

9. Retention

We keep personal information only as long as needed for the purposes above, including:

• Account and profile data — while your account is active and for a reasonable period afterward for security, disputes, and legal compliance.

• Payment and transaction records — for the period required for tax, accounting, fraud prevention, and card-network dispute windows (often several years).

• Legal acceptance records — retained as evidence of agreement to a specific document version; they are not automatically deleted when a profile is removed.

• Marketing consent and email suppressions — while needed to honor your choices and protect sending reputation.

• Organizer activity logs — retained for security and account integrity; a specific deletion schedule for logs is still being finalized.

• Vendor ratings and Organizer notes — retained as the Organizer’s operational records for the shows they run.

When information is no longer required, we delete or de-identify it where feasible.

10. Your rights and requests

Depending on where you live (including under CCPA/CPRA and similar laws), you may have rights to access, correct, delete, or obtain a copy of personal information, to opt out of certain sharing, and to appeal a refusal.

How to exercise: email support@hiroba.io with the email address you use on Hiroba and the request type. We will verify your identity reasonably and respond within the time required by law.

Honesty about deletion today: Hiroba does not yet offer a self-serve account-deletion button. Deletion and export requests are handled manually. We will delete or de-identify personal information we are not required to keep for law, security, fraud prevention, accounting, disputes, or enforceable agreements. Payment history and acceptance logs may need to be retained or scrubbed rather than fully erased.

We will not discriminate against you for exercising privacy rights.

If an Organizer holds information about you independently (for example their own email list), contact that Organizer as well.

11. Security

We use industry-standard measures appropriate to a small production system (encrypted transport, access-controlled hosting, scoped credentials, and monitoring). No method of transmission or storage is 100% secure.

12. Children

Hiroba is not directed to children under 13, and we do not knowingly collect personal information from children under 13. Organizers selling tickets to all-ages events should ensure their own compliance with applicable youth privacy rules.

13. U.S. focus

We operate primarily in the United States. If you access the Service from elsewhere, you understand your information may be processed in the U.S. where laws may differ.

14. Changes

We may update this Policy. We will post the revised version here with an updated version identifier. Material changes may also be communicated in-product or by email where appropriate.

15. Contact

Auctor LLC

Email: support@hiroba.io

Web: https://hiroba.io

Privacy requests: support@hiroba.io with subject line “Privacy request”.

Note: A physical mailing address for CAN-SPAM and privacy notices will be added to this Policy and to promotional email footers once confirmed for Auctor LLC.