FAMILIAR PROTOCOL
Privacy notice
Effective August 1, 2026
This private-alpha technical policy is not a final public-launch policy. Contact justin@cyberelf.link for privacy or account-data requests.
Data handled
Guest play uses opaque client and player credentials. Account play stores a username, password hash, session-token hash, familiar ownership, certification reports, match participation, public match events, content reports, and security anomalies. Request logs contain request IDs, route/status/latency data, and hashed network identifiers; they must not contain plaintext player or session tokens.
Purposes
Data is used to provide accounts, ownership, matchmaking, deterministic battles and replays, abuse prevention, support, deletion/export, reliability measurement, and balance analysis.
Optional AI generation
AI generation is disabled by default. If the deployment owner enables it, the familiar concept and generation schema are sent to the configured OpenAI API at creation time. Model calls never occur during match resolution.
Sharing and sale
The service does not sell personal data. Data may be processed by the hosting, database, monitoring, and optional model providers selected by the deployment owner, subject to their contracts and the owner's published subprocessor list.
Your controls
Signed-in users can export their stored account data and delete their account from the Identity panel. Deletion anonymizes ownership references needed to preserve public match integrity and replay evidence. Content reports can be submitted from a match.
Retention and security
The service expires sessions, matchmaking tickets, invites, and abandoned match state according to deployment configuration. The owner must publish concrete retention periods and a restore/deletion procedure. Credentials are hashed at rest and transport must use HTTPS/WSS in public deployments.
Contact
Email justin@cyberelf.link or use the instructions on the support page.