Information you provide
When you use Met, we may collect and store:
- Contact details you scan or type (name, title, company, email, phone, website)
- Context you add (where you met someone, conversation notes, tags)
- Follow-up drafts you generate or edit
- Your own identity card (name, role, company, phone, email) if you choose to fill it in
This information is stored on your device and, where applicable, synchronized with Met's backend to support account-based features.
Account and authentication
Met supports sign-in via Apple and Google. When you sign in:
- Sign in with Apple, we receive your Apple-issued identity token and optional name/email. Apple may hide your real email address behind an anonymized relay.
- Sign in with Google, we receive an OAuth access token and your Google profile email. We do not access your Gmail inbox. The Gmail scope is used only to send a follow-up email you explicitly compose and initiate inside Met.
Session tokens are stored securely on your device and in our database. They are used only to authenticate API requests from your app.
Gmail integration
If you connect Gmail, Met requests the gmail.send permission. This allows Met to send an email on your behalf only when you tap "Send via Gmail" on a draft you have reviewed. Met does not read, index, or store any emails from your inbox.
Google Calendar integration
If you connect Google Calendar, Met requests calendar.readonly access. This is used solely to suggest relevant events on the "Add Context" screen when you are saving a new contact. Met does not store your calendar events beyond an in-memory cache used to populate suggestions during an active session.
Generated content
Follow-up email drafts and contact parsing are generated using OpenAI's API. The contact details and context you provide are sent to OpenAI to generate a draft. We use OpenAI's API in a way that prohibits them from training on your data. You should not include sensitive personal information (e.g., health data, financial account numbers) in notes or context fields.
Subscriptions and payments
Met Pro subscriptions are handled through Apple's App Store via StoreKit. We do not collect or store your payment card information. Purchase history and subscription status are managed by Apple. We track only whether your subscription is active, using Apple's receipt validation.
Local notifications
If you grant notification permission, Met may schedule a local reminder (on-device only) to follow up with a contact approximately three days after you saved them. These reminders are generated and stored entirely on your device, no notification content is sent to our servers.
Apple Contacts access
If you grant Contacts permission, Met can import contacts you select, or add a scanned contact to your iPhone's address book. We request access only when you initiate one of these actions. We do not silently scan or sync your entire address book.
Camera access
Met uses the camera to scan business cards, badges, and QR codes. Camera frames are processed locally using Apple's Vision framework. No camera footage is transmitted to our servers.
Analytics and error reporting
Met uses two third-party services for operational telemetry so we can catch bugs and understand how the app is used in aggregate:
- Sentry, receives reports of unhandled errors and crashes. Reports include a stack trace, device model, iOS version, and app version. Reports do not include the contents of your contacts, notes, drafts, or session tokens.
- PostHog, receives anonymized product-usage events (for example: "a contact was captured," "a follow-up draft was generated"). Events are keyed by your server user id, not by email. Session recording is disabled.
Neither service sells data. Both are covered by data processing agreements. If you prefer to opt out, email support@sailquery.com.
Service providers
We rely on the following processors to operate Met. None of them sell your data; all are bound by contractual data-processing obligations.
- Apple, Sign in with Apple, StoreKit, iCloud, App Store Connect.
- Google, Sign in with Google, Gmail API (send-only), Google Calendar read-only.
- OpenAI, contact parsing and follow-up draft generation. Configured to prohibit training on your data.
- Neon, managed PostgreSQL hosting our sessions, share cards, Gmail OAuth tokens, and bad-scan reports.
- Vercel, serverless function hosting for the Met backend at
api.mettree.com.
- Sentry, crash / error reporting (see above).
- PostHog, product analytics (see above).
Data retention and deletion
Your contacts and drafts are stored on your device. If you use an account-backed feature, related data may be stored in our database. You can delete your account at any time from the Me tab in the app, this sends a request to our backend that cascades through and deletes your user row, session tokens, share card, and connected Gmail / Calendar tokens before wiping local data. If the server deletion fails, the app will surface the error and leave your local data intact so you can retry. Bad-scan telemetry (OCR feedback) is retained for 30 days and then purged.
Children's privacy
Met is not directed at children under 13. We do not knowingly collect personal information from children.
Changes to this policy
We may update this policy as the product evolves. Material changes will be communicated via the app or this page. The effective date at the top of this page reflects when the current version was published.
Contact
Privacy questions or data requests: support@sailquery.com