Use AI with your records?

AI summarises conversations, finds promises and refreshes relationship summaries. New notes, this person’s profile notes and past conversation records are sent to Google Gemini. Audio, card or note images and questions are also sent when you use those tools; translation sends text to Google.

Your choice is remembered for this account. You can change it in Settings. You can still save notes and add promises without AI.

Turning AI off prevents new processing. Requests already sent may finish; existing notes and summaries are kept.
Back

Privacy Policy

Last updated: 2026-10-17

People Person is a personal contact-management app built by Jason Hong. This Privacy Policy explains what data we collect, how we use it, and your rights.

1. Information We Collect

We collect the names, phone numbers and email addresses of phone contacts you explicitly select. We do not read your entire address book or send these contacts to AI.

Contacts shared from other apps (as a file or as text) are processed on your phone. If your phone cannot receive them directly, our server reads them in memory without storing them and returns them to your phone. Only people you select on the review screen are saved. Shared content can only be opened for 10 minutes. Expired content is cleaned up when you open the app.

Contacts you pick in the Android app's contact picker are encrypted on your phone and pass briefly through our server. The decryption key is used only on your phone and is never sent to the server, so the server cannot read them. The encrypted data is deleted as soon as it is picked up, cannot be picked up after 10 minutes, and is removed during regular cleanup. It is never included in backups. Only the people you select on the review screen are saved to your account.

  • Account info: email address and a hashed password (we never store the plain password).
  • Contacts you add: names, phone numbers, email addresses, social handles, addresses (city/country), birthdays, photos, free-form tags, and notes you write about people you meet.
  • Meeting voice recordings: when you tap the microphone, the resulting audio file is uploaded to our server for transcription via Google Gemini, then deleted from disk immediately after transcription finishes. Transcripts and AI summaries remain in your account.
  • Business card and note photos (OCR): when you choose photo recognition with AI processing enabled, the selected image is sent to Google Gemini for text extraction. Note photos are resized and image metadata is removed before transmission. These OCR images are not saved as server files. You can review and edit extracted note text before adding it to a record; it is saved only when you save the record.
  • Profile shares (Collect from friends): when a friend submits the form via your share link, the data they shared is stored in your account, encrypted at rest. Friends can refuse any field.
  • Push subscription tokens (optional): if you allow notifications, we store the browser-issued push subscription endpoint.
  • App activity: high-level events (signup, login, meeting logged and contact import stages, paths and counts) are recorded against your account for product analytics and audit logging. Import metrics contain no contact names, phone numbers, email addresses or contact content. These events are deleted with your account. No third-party analytics SDK is embedded.
  • Crash reports (optional): when error reporting (Sentry) is configured by the operator, we send the error type, the code location (file, function, line) and the app version. We do not send request contents, cookies, headers, your notes, names, emails, photos, audio, or program variables.

2. How We Use Your Data

  • To run the app: store and display your contacts, meeting notes, reminders, and other personal records.
  • Transcription & AI summaries & OCR: audio, text, and images are sent to Google Gemini for processing. Google's processing is governed by their Generative AI Terms.
  • Push reminders: when reminders are due, we send an encrypted push notification to your device.
  • Account communications: verification, password reset, and "friend submitted profile" notifications are sent via the Gmail API on the operator's Workspace account.
  • Audit log: login attempts and sensitive actions (2FA enrollment, account deletion) are logged for security review.
  • Connections between users: If you ask to connect with someone, or accept a request, each of you sees only the card details the other chose to share, and only after both agree. If you allow it, people who know your exact sign-in email can find your app membership through saved-contact suggestions or exact-email search. Connection requests show the requester’s display name and field categories, but no contact values before mutual acceptance. You can end a connection or block someone at any time. Details already saved in the other person's list stay in their list. Blocking and reporting records a selected reason to prevent abuse. The other person is not notified. Administrators see report counts, not reporter identities; reports are deleted if either account is deleted.

3. Third Parties

  • Google Gemini API — receives audio (for transcription), images (for OCR), and text (for summaries). Subject to Google's AI / API terms.
  • Google Workspace (Gmail API) — used to send transactional emails on the operator's domain (jason@peopleperson.me).
  • Railway — our hosting provider. Data at rest lives on Railway's managed infrastructure.
  • Cloudflare — DNS, CDN, DDoS protection and Turnstile signup checks. Receives connection metadata. When configured, private R2 storage also holds database and contact-photo backups for disaster recovery.
  • Sentry (optional) — receives anonymized stack traces if the operator has configured it.
  • We do not sell your data to advertisers or third parties. We do not embed advertising SDKs. We do not use your data to train AI models.

4. How Your Data Is Protected

  • All traffic to the app uses HTTPS.
  • Passwords are stored as salted, one-way hashes using Werkzeug. Password-reset tokens are HMAC-hashed in the database.
  • Your own profile and shared card submission data are encrypted using Fernet with a server-side secret. Contact names, contact notes, meeting records, and transcripts are not individually encrypted in the database.
  • Sessions use HTTP-only, SameSite=Lax cookies.

5. Your Rights

  • Access: view all your data inside the app at any time.
  • Edit: modify any contact, meeting, profile, or note.
  • Export: download your contacts, meeting records, follow-ups, profile and exported settings as JSON (Settings → Privacy & data → Export). Photo files are not embedded in this JSON export. Contact us if you need a copy of your photos.
  • Delete: remove individual records, or permanently delete your entire account (Settings → Privacy & data → Delete Account). Account deletion erases your contacts, meetings, profile, integration tokens, and push subscriptions immediately and irreversibly. If you cannot open the app, you can request deletion at peopleperson.me/account/delete.
  • EU / UK users (GDPR): you have the right to access, rectify, erase, restrict processing, port, and object. Use the in-app controls above or email us.
  • California users (CCPA/CPRA): you have the right to know what data we collect, the right to delete, and the right to opt out of sale (we do not sell data).

6. Data Retention

  • Your data lives in our database until you delete it.
  • Audio files: temporary files are removed when transcription processing finishes, including handled failures. Audio recordings are not included in our database or photo backups.
  • Business card images: deleted immediately after OCR (not persisted).
  • Legacy calendar connections: the calendar feature has been removed. If your account still holds a stored token from it, it is deleted when you delete your account.
  • After account deletion: data is removed from active databases immediately. Backups are retained for up to 30 days for disaster recovery and then purged.

7. Children

People Person is for adults and is not directed at anyone under 18. Every signup path, including Google and Microsoft sign-in, requires you to confirm that you are 18 or older. If you believe a child has created an account, contact us and we will remove it.

8. International Data Transfers

The app is hosted in the United States (Railway). If you access it from outside the US, your data is processed in the US. By using the app you consent to this transfer. We rely on Standard Contractual Clauses for transfers from the EU/UK.

9. Security Practices

  • HTTPS/TLS everywhere
  • Sensitive profile fields encrypted at rest with Fernet (AES-128)
  • Optional TOTP two-factor authentication
  • Login rate-limiting + audit log
  • Sessions: HTTP-only, SameSite=Lax cookies, Secure flag in production
  • CSRF protection: double-submit cookie + header on every state-changing request

10. Changes

We may update this policy from time to time. Material changes will be communicated via the app or email at least 7 days before they take effect.

11. Contact

For privacy questions, data requests, or to exercise GDPR/CCPA rights, email jason@peopleperson.me.

Please confirm