Privacy Policy

Search uses only the profile fields you publish for discovery: name, gender, age, country, locale, and occupation. These fields may appear in public card pages and anonymous search matching.

Contact and sensitive fields can be marked as paid and deployed to CDR. The server stores metadata such as field type, label, price, CDR state, vault UUID, and transaction hash. It should not store paid plaintext values.

Mobile fields require code verification before CDR deployment. Email is fixed to your signed-in email and can be deployed without an additional verification step. Verification providers may process the destination address or phone number solely to send and confirm the code.

Buyer requests store reusable search parameters, selected field types, selected anonymous match references, totals, payment status, and export logs. Pre-purchase search responses do not expose paid contact values.

You can turn CDR off for a field to hide it from search, or keep CDR on to list it for paid access. Account deletion and advanced privacy controls are placeholders during the hackathon phase.