The Antiquity Guild
The Guild's commitment to your information, in plain language.
If you join as a Member: a username you choose, an email address, a hashed password, your monthly contribution amount and tier name, and (if Stripe is used) a Stripe customer reference. If a Representative gave you a code when inviting you, that code is recorded.
If you serve as a Representative: a handle, an email, a hashed password, your SCAS allocation and usage totals, your Oath affirmation timestamp, and the contracts and retroposity acts you author.
If you receive aid as a Neighbor: a handle, optionally an email, a hashed password. Cases linked to your account hold the title and what was provided, but no identity beyond what you choose to share with your Representative.
The three capacities (Member, Rep, Neighbor) are walled in the database. The system has no way to know a single person holds accounts in more than one capacity.
To protect accounts, the Guild records sign-ins and failed sign-in attempts, and attempts to reach the operator admin area, each with the connecting network address (IP) and a timestamp. This is protection, not surveillance: it lets the Guild see a break-in attempt instead of missing it. It is never sold, never profiled, never used for advertising, and never linked across the walled capacities.
Because the Guild refuses security theater, there are no forced password-complexity rules and no lockouts that punish you for a typo. The substrate watches quietly instead. As a Member, you can see your own sign-in history any time on your dashboard — the same record the Guild keeps is yours to read.
Your records are held directly by the Guild, in its own custody as an institution — not by any individual (see § Guild Custody & Access). Nothing lives on a third-party cloud database service, and no outside company holds a copy of your records.
One unavoidable third party touches your data when you join as a paying Member: Stripe, the payment processor. Stripe holds the card or bank details necessary to process a contribution; the Guild only sees the resulting customer reference and amount. This is acknowledged as a bridge dependency in the Guild's long-horizon infrastructure plan; when capacity allows, Stripe will be replaced by a Guild-native payment path.
The Living Book is explicit:
Sign in to your member dashboard. Use the Export My Data link to download everything the Guild holds about you as JSON, or Delete My Account to remove it permanently.
Member Sign In Become a MemberSign in at the Rep workspace. Export includes your contracts, referral codes, and retroposity ledger entries.
Rep Sign InIf you have a registered Neighbor account (a Quiet Account), sign in to view, export, or delete your case data. Pseudonymous aid recipients have no account to manage.
Neighbor Sign InIf you submit a report at /report, no login is required and no identifying data is collected by the form. You receive a receipt code; the Guild handles every report with confidentiality per Living Book § Termination Policy & Process.
Material changes to how the Guild handles data are recorded in the public Change Log per Living Book § Edits & Amendments. The Guild does not silently change its data commitments.
← Return to the Guild Hall