Privacy Policy

1. Who we are

Peep is the data controller, operating from Turkey. Contact: support@peep.house.

2. What we collect

• Account: your Privy user ID, how you signed in (an email address, or a Google or X account ID; with X, also your X handle and profile photo), and the address of your embedded Solana wallet.
• Terms: the version of the Terms of Use you accepted, when, and your confirmation that you are 18 or older.
• Profile: handle, display name, bio, links, avatar, cover and the look you chose.
• What you post: Peeps, comments, group messages, group calls and reports you file.
• Groups: groups you create or join, join requests and paid joins (amount and transaction signature).
• Trading: swaps you make through Peep (token, amounts, time and transaction signature) and the Peep audience you choose for them.
• Activity on Peep: who you follow, your watchlist, search and filter requests sent to our services, Peep subscriptions, notification-read status, the invite you joined with and how many people joined with yours, and the XP and Peep Score worked out from your activity.
• Profile photos and a group's own image you upload: checked by Peep's own image classifiers on Peep's own servers; no third party sees them for this. Covers are not checked by Peep's classifiers. Peep stores a new copy of the checked image, without location or other metadata. Images, GIFs and link previews sent in a group chat are delivered and stored by Stream and are not checked by Peep's classifiers.
• Refused images under zero tolerance: when an upload is refused as possible child sexual abuse or terrorist content, the file as uploaded, its fingerprint (hash), your account ID, the time and the result of the check are kept in a restricted store that only Peep's moderation can open, for review and for reporting to the authorities. Peep compares new profile photos and group images with these fingerprints; a match is refused and handled the same way, whichever account uploads it.
• Technical data: request logs (time, path, result) and abuse counters keyed by a hashed account ID. Our hosting providers process your IP address to deliver pages and requests.
• On the web: Error reports and usage events: when something breaks, the error (its message and where in the code it happened), the page as a route template such as /u/[handle], and your browser, OS, language and time zone; and a few product steps (sign-in finished, wallet ready, first SOL balance seen, a trade sent, settled or failed with its token and a SOL range, Discover or a token page opened, a Peep posted, a follow, a group joined) under an ID derived from your account by a one-way hash, with your browser, OS, language, time zone, screen and window size, and random device and visit IDs that are not stored and change on every full page load. Wallet addresses, transaction signatures, emails, handles, invite codes, tokens and query strings are removed before anything leaves, and no session is recorded.
• On Android: Privy processes sign-in and embedded-wallet information, including account identifiers and device/network information. Its services may derive approximate location from an IP address. Profile and group-image uploads use only the images you select with Android's system picker; the app does not request access to your location, contacts, microphone or camera.
• Android diagnostics and analytics: builds with Sentry enabled send scrubbed errors and device/app context. Builds with PostHog enabled send application lifecycle events and technical properties under an anonymous identifier reset on each launch. SDK installation or session identifiers can still exist without an advertising ID. These services receive direct network connections from Android, unlike the web relay described below; this can expose a connection's IP address to the service.

We never ask for or store your private key, recovery method or password; Privy handles sign-in secrets. Peep on the web runs no advertising trackers. It sends error reports to Sentry and a few product analytics events to PostHog through Peep's own servers, without your IP address, wallet address, email or handle (section 5).

Android's Sentry and PostHog integrations start only when configured in that app build. Peep disables their session replay, screenshots and view hierarchy collection, and scrubs account identifiers, wallet addresses and credentials from events. Android analytics does not create person profiles or identify your Peep account. A build-time setting is not a user opt-out, and scrubbing does not remove network information a service receives when accepting a connection.

3. Public blockchain data

Solana transactions are permanent and visible to anyone: wallet addresses, swaps, transfers, tips and paid joins. Neither we nor anyone else can delete them. Choosing who sees a trade on Peep doesn't change what Solana shows.

4. How we use it

• To run Peep: sign you in, open your account, show your feeds and profile, build your swaps, run groups and chat.
• To keep Peep safe: check uploaded profile photos and group images automatically on Peep's own servers, handle reports, limit abuse and investigate incidents.
• To report child sexual abuse material and terrorist content to the competent authorities (such as the NCMEC CyberTipline and the police) and answer their lawful requests.
• To work out the public figures described on How Peep numbers work.
• To understand app usage and diagnose errors through the web and configured Android analytics and error-reporting services described here.
• To meet legal duties and enforce the Terms of Use.

We don't sell personal data, and we don't use it to train third-party AI models.

5. Who processes it

The Sentry and PostHog rows without an Android label describe the web/server configuration. Android uses the separate integrations described above. Group messages from Android go directly to Stream using a user session issued by Peep. Chat is not end-to-end encrypted.

Market data comes from third-party market data providers, launchpads and Jupiter through Peep's servers. Requests can include token identifiers or public wallet addresses needed for the requested data; a public wallet address may still identify a person. For wallet history and positions, Peep's servers send that wallet's address to Mobula, Peep's wallet history provider. On the web, token logos and banners on market lists and token pages, and pictures of public posts in the market feed, load through Peep's servers, so the sites that host them do not see your IP address. Other web images (group call cards, your wallet's token icons, search results, profile photos) load directly from their hosts. Android token images also load directly from their hosts, which can see the connection's IP address.

When you open an X post preview, Peep's server retrieves the public post from X's oEmbed service and briefly caches its author, text and date. This request does not forward your Peep account, wallet details or browser credentials to X. Opening the source link takes you to X, where its Privacy Policy applies.

Image and text checks run on Peep's own servers; no third party receives your images for them. Peep uses no known-image matching service today; if it starts to, this policy will name it before it applies.

Authorities: we disclose data when the law requires it, and we report child sexual abuse material and terrorist content we find to the competent authorities with the material and the account details needed.

6. Browser and Android storage

Browser storage keeps your Privy session (set by Privy), a note that this browser was signed in, your settings, a copy of your watchlist and the Terms version you accepted. None of it is used for advertising. Sentry and PostHog set no cookies and store nothing in your browser.

Android keeps the sign-in session and local app state needed to operate your account, including settings, cached lists and pending-operation recovery information. The app excludes its data from Android backup and device-to-device restore. Its current notification inbox is inside the app; it does not register an Android push-notification token. Signing out or uninstalling does not request deletion of your server-side account.

7. Security

Peep's configured app services use HTTPS/TLS; the Android app disallows cleartext network traffic. Access controls limit account data to authorized users and services, and server credentials are not distributed with the app. Providers apply their own storage and backup protections. These measures are not a promise of end-to-end encryption or perfect security. If a breach affects you, we will tell you and the authorities within the time the GDPR and KVKK require.

8. How long we keep it

Provider retention and backup expiry depend on the configured service and legal requirements; this policy does not promise a fixed erasure deadline for every provider or copy. Contact support@peep.house to ask about retained data or the progress of a deletion request.

9. Delete your Peep account

You can request deletion of your Peep account and associated personal data without installing the app or signing in here. Request account deletion by email, or write to support@peep.house with the subject "Delete my Peep account". The link opens a draft; nothing is sent automatically.

Tell us the Peep handle or sign-in email for the account and whether you want the account and associated data deleted or only particular content removed. We may ask you to verify that the account is yours before acting. Never send a password, one-time code, private key or recovery phrase. This page does not put account details into its links.

Android also offers an account deletion action in its account safety controls. Before deleting an account, resolve any funds or access you need to keep, and export your wallet through the supported web security flow if needed. Deleting an account does not transfer funds or erase a Solana wallet's public history.

The current automatic action removes Peep profile and related account records and removes or de-identifies supported membership, referral and XP records. Some records for groups you still administer remain. It also requests removal of profile media and marks the Stream chat user and messages deleted. Stream's stored records are not permanently erased by that action, and chat or media cleanup can fail even when other account records have been removed.

The automatic action does not delete the authentication identity held by Privy. A success message is therefore not confirmation that every provider record or backup has been erased. Use the email request above for remaining personal data or cleanup that has not completed. Reports, legally required records and restricted moderation evidence may be retained as described here; on-chain records remain public permanently. We answer privacy requests within 30 days. This is a response period, not a guarantee that every provider copy disappears within 30 days.

10. Your rights

Depending on where you live, you can ask for a copy of your data, correct it, delete it, receive it in a portable format, object to or restrict processing, and withdraw consent. You can also complain to your data protection authority (in Turkey, the KVKK Authority; in the EU, your national authority).

Write to support@peep.house, or use Delete your Peep account. We answer within 30 days. On-chain data can't be deleted.

11. Age

Peep is for people 18 and older. If you believe someone younger has given us data, write to support@peep.house so we can investigate and handle the removal request, including any provider-held data.

12. International transfers

Some providers (Privy, Stream, Helius and Jupiter) process data in the United States. We rely on standard contractual clauses and the providers' own transfer safeguards where they are required.

13. Changes

We may update this policy. Material changes are announced in Peep at least 14 days before they apply, and the date at the top always shows the current version.

14. Contact

Questions, complaints and requests: support@peep.house.