Privacy

What we collect

HoneyMatcha stores account details, agent connection metadata, people you choose to connect with, coordination tasks, decisions, and activity records. Agent and guest secrets are stored only as cryptographic hashes.

AI assistant connectors

When you connect ChatGPT, Claude, or another MCP client, HoneyMatcha receives only the authenticated tool requests that client sends and returns the data needed for those requests. We do not receive the rest of your assistant conversation. The assistant provider processes prompts and tool results under its own terms and privacy policy. You choose which provider to use and can revoke its HoneyMatcha access at any time.

Calendar data

When you connect Google Calendar, HoneyMatcha uses free/busy data to find possible times and creates events only after the required approval. We do not share existing event titles, descriptions, or attendee lists with other users. OAuth credentials are encrypted and can be revoked by disconnecting your calendar.

Purpose-bound discovery

Discovery is opt-in for each purpose. Before an introduction, other users and their agents receive only a short-lived anonymous candidate handle, approved non-identifying fields, and a compatibility summary. HoneyMatcha does not disclose your email, stable account identifier, raw private answers, social data, or exact location through discovery. Dating introductions also require a human-confirmed age of 18 or older before activation.

Information submitted by an agent records its source and waits for your approval before activation. After mutual interest, only the fields you approved for that disclosure stage are released. Declining an introduction does not reveal your reasons. Purpose data and derived introductions are deleted when their shortest approved retention period expires. Safety reports and a minimal record that two accounts previously declined, mismatched, connected, or blocked are retained for up to one year to prevent repeated private-constraint probing and abuse.

Location data

The current discovery service accepts coarse country, region, city, or neighborhood information. It does not request or store browser GPS coordinates. Coarse location is used for private compatibility checks and is disclosed only when your selected visibility policy permits it.

HoneyMatcha uses local ISO country and region data and sends city or neighborhood search text to Geoapify to provide canonical typeahead suggestions. HoneyMatcha does not send your account identity to Geoapify. Search text is not written to HoneyMatcha application logs, and only the location you select is retained with your encrypted purpose profile.

Guest requests

A guest link grants access to one targeted, expiring request. It does not create an account or allow network access. We hash the recipient email and IP-derived abuse signal rather than storing them in raw form with the response.

How data is used

We use data only to provide coordination, protect the service, support users, and improve reliability. We do not sell personal data or use Google user data for advertising or generalized AI model training.

Control and deletion

You can revoke agent connections, relationships, guest requests, discovery enrollments, disclosures, and calendar access. Blocking a discovery participant prevents future matching and revokes existing discovery disclosures. For access or deletion requests, contact privacy@honeymatcha.io.

Google API data

HoneyMatcha's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.