Vagabond Dynamics LLC

Privacy

Effective August 5, 2026

What this founding version collects

If you join the founding list, we store the email address you provide, your selected interest, consent, and the submission time. We do not request payment information on this site and do not sell personal data.

Member accounts and game progress

A free member account stores the email address you register with, a salted password hash, adult confirmation, session-token hashes, roster, squad, free guild-mark balance, mission outcomes, and reward history. Accounts created before email sign-in shipped keep signing in with their original handle. Every account also holds an internally generated handle used only to identify your account in our systems; it is not derived from your email and is not shown to other members. The raw password, raw session token, and your email address are never shown in public site UI. The raw password and raw session token are not stored. Game progress is private to the account.

Life Quest

Life Quest is a private, real-world task tracker inside your account. We store only your current task text, its inferred category, the three-step plan generated from your own squad, an optional location note you may add when marking it complete, and the completion time. We keep one row per account: setting a new task overwrites the previous one, so no personal task history accumulates. The location note is plain text you type; it is never a device location read, and it is never required to complete a task. Completion is entirely self-reported -- there is no automatic verification. Your task title, plan, and completion status are private to your account: never put in page URLs, server logs, analytics, the public feed, or error messages. No external AI, model, or third-party API ever receives your task text. We also record, per account and UTC calendar day, whether a free guild-mark reward was already granted that day, so the reward cannot be claimed twice. You can replace or clear your current task at any time, which deletes the stored task, plan, and location note.

Location-based Guild Beacons

Location is requested only when you choose Find nearest Beacon or Refresh location. Your browser sends its current latitude, longitude, and accuracy for a one-time proximity calculation. The game database does not store those raw coordinates or maintain a movement trail.

We store the derived Beacon code, the verification time, local squad influence, Beacon level, and missions completed there. Location access can be denied in your browser, but Beacon missions require a fresh proximity check.

After a proximity check, your browser loads a street map directly from OpenStreetMap's tile servers to show your position next to the Beacon. That request tells OpenStreetMap the approximate area of the map tiles displayed on screen, plus the normal request metadata every web request carries, such as your IP address and referring page. OpenStreetMap is a third party we do not control; see openstreetmap.org/copyright for their terms. Your exact coordinates stay in your browser and are never included in that tile request, in the game database, or in any analytics we collect.

Anonymous activity counts

We record first-party daily totals for visits, successful shares, founding-list signups, character dossier opens, and spotlight views. The metric table contains only a date, event category, public release or character key, and a count. It does not contain an email address, IP address, user agent, cookie identifier, or per-visitor browsing history. Session storage prevents duplicate counts during a visit. Local storage remembers the last public release viewed so the site can show what changed when you return.

Private hero participation

If you create a hero, the member account owns the private hero identity, guide, timezone, reminder hour, goals, habits, check-ins, XP, streak, and autonomous dispatch history. We do not attach IP address, user agent, or public profile visibility to this record. Hero data is available only after authentication as that member.

Weight-management participation records chosen routines and completion, not a public weight, calorie target, diagnosis, medication, or treatment plan. You can export or permanently delete the private hero record.

Private R18 Vault

The R18 Vault is a separate authenticated adult-edition surface for original fictional characters age 21 or older. The server stores only your adult attestation, entitlement state, private progression, approved scene manifests, and short-lived asset grants. Detailed sexual preferences, kink boundaries, intensity ceiling, STOP-contract choice, and hypnosis-fantasy confirmation remain in this device's local storage. They are not synced, exported to analytics, added to URLs, written to logs, or included in the public Guild feed.

Every preference begins blocked. New choices added to an older profile also begin blocked, and the site cannot silently make a choice more permissive. Approved scene assets are delivered through member-bound, expiring private URLs only after authentication, adult attestation, entitlement, region, progression, character-boundary, and current consent checks pass. Withdrawing R18 consent clears the local profile and revokes active asset grants without deleting the Guild account.

Email delivery and suppression

Daily-drop delivery records provider message IDs, bounded attempt counts, delivery status, and verified bounce or complaint events. Unsubscribe, bounce, complaint, and provider-suppression events place the address on a suppression list so future sends stop.

How it is used

We use the address only for the notices selected when you join, such as Infinite Guild daily drops and Guild Pass opening. The first real delivery remains approval-gated until Vagabond has a verified sender domain and the exact preview is approved. Every delivered daily drop includes an unsubscribe link; routine releases run automatically afterward with bounded retries.

Infrastructure

The site is hosted on managed cloud infrastructure. Operational world data contains no customer identity. Founding-list records are separate from the public story feed. Aggregate activity counts are separate from both the public story feed and founding-list records.

Changes

This notice will be revised before paid memberships or any third-party measurement service is activated. Material changes will be dated here.