Peeka (peeka.pics) is a photo Q&A community run by an independent developer and operated by Gergedan LLC. This page explains what information we collect and how we use it. It is short because the service is simple.
What we collect
- Email address — when you sign up or sign in, and to send you account-related email.
- Birth year — used only to confirm you are 18 or older. With it we record when you agreed to the Terms and Community Guidelines, and which version.
- Account details — your username and profile information such as your bio, location, website, and avatar. If you installed the app from someone's profile link, we also note whose link it was.
- Content you create — the topics you write, the photos you post as answers and the details you add to them (such as a title, note, place, or link), your comments, the questions you send to other people, and the feedback and reports you send us. Photo location metadata (EXIF) is removed when you upload.
- Questions you send — when you ask someone a question anonymously, they and other users do not see who asked. We still store the sender with the question so we can act on abuse reports.
- Basic technical data — our server keeps standard logs (such as IP address and request times) for security and debugging.
- Usage data — in the mobile app, we collect when the app is opened or closed; actions such as sign-ins, likes, bookmarks, follows, comments, posts, and shares; the steps of posting a photo, including when one is left unfinished; which feed tab you use and how recent the answers you see are; and which languages you read, to understand how the app is used and improve it. Search queries are used to show results; we record only how many results a search returned, never what you typed, and we do not keep a search history.
- Device data — if you allow notifications, a push token so we can reach your device. Analytics events and crash reports include basic device details such as the device model, operating system, app version, and language.
- Approximate location — we use your IP address to determine your country, and record it with the topics and questions you create. We never collect your precise location.
How we use it
- To run the service — sign you in, show your content, and let people interact.
- To send transactional email — sign-in links, notifications, and account-related messages. We do not send marketing email.
- To keep the service safe and fix problems.
We do not sell your data, and we do not run ads or advertising analytics.
Who else sees it
We use Resend to deliver email. Your email address is shared with them only so the message can be sent. Photos are stored in object storage (Cloudflare R2). We use PostHog for product analytics and to monitor errors on our servers, and GlitchTip to receive crash reports from the app.
If you sign in with Google, Google confirms your identity and shares your email address with us. Push notifications are delivered through the Expo push service and Firebase Cloud Messaging, which receive your push token and the notification text.
To protect sign-in and account requests from automated abuse, we use Cloudflare Turnstile, on the website and on the app's sign-in screen. When you request a sign-in link or a similar account email, Turnstile runs a check in the background and processes information about your device and browser to tell people from bots. Its handling of that information is described in the Cloudflare Turnstile Privacy Addendum.
Anything you post publicly on Peeka — photos and answers — is visible to other users.
Cookies
We use a single session cookie to keep you signed in. We do not use tracking or advertising cookies.
Keeping and deleting your data
We keep your data for as long as your account exists. You can delete your account and the data tied to it at any time at peeka.pics/account/delete, which the app's settings also open, or by emailing us. You confirm the request through a link we email you. To remove your content but keep your account, use peeka.pics/account/wipe. We also honor requests to access or remove your personal data.
Changes
If this policy changes, the date at the top of this page will be updated.