Privacy, without the mystery.

This policy applies to the PikkMe iOS friends beta, the PikkMe website, and related support interactions. PikkMe is currently operated by Dorukhan Bozkurt in the Netherlands. Participation in the beta is limited to adults aged 18 or older.

We process information you provide or create in PikkMe, including:

• a Firebase account identifier and account creation timestamps;
• your display name, username, biography, optional profile photo, profile settings, and notification preferences;
• daily challenge photos and submission metadata; profile-photo uploads and associated safety checks;
• if you enable phone notifications, a push delivery token associated with your account and device platform, plus delivery status and preference records;
• Pikks, follows, comments, replies, comment likes and pins, optional captions, place labels, and tags you type for an entry, private direct/group messages, group names and optional group photos, shared-entry references, chat photos and voice notes you choose to send, blocks, reports, automated content-safety signals, moderation records, and beta feedback;
• an Apple account identifier and Apple-provided relay email if you choose Sign in with Apple;
• limited technical information needed to operate, secure, diagnose, and improve the service, such as app version, device platform, operating-system version, timestamps, error information, and network-request metadata such as an IP address.

PikkMe requests camera access to capture a fresh daily entry. You can separately choose a profile photo, private chat photo, or private group photo from your library; this does not allow library uploads to daily challenges. Only the image you select is uploaded, not your whole library. Profile, chat, and group photos are re-encoded to remove embedded metadata. Profile and group photos are checked for safety before display. Microphone access is requested only when you tap the voice-note control; recording is limited to the foreground chat and one minute. You may manually add a caption, general place label, and tags to an entry; these are public with that entry, but PikkMe does not request or read precise device location. An owner-only preparation tool can also import curated Studio images. PikkMe does not run third-party advertising or sell personal information. Some features may be available only in newer beta builds.

We use information to create and recover accounts; check uploaded public photos and profile, comment, reply, or message text for safety; deliver direct/group messages, chat photos, voice notes, and shared-entry cards only to current conversation members; operate daily challenges, voting, comments, social features, leaderboards, and winners; send reminders and activity notifications you enable; detect manipulation or abuse; investigate reports; enforce our rules; answer support requests; and maintain the reliability and security of the beta.

Your camera, profile-photo, and group-photo uploads remain private while their file and automated safety checks are completed. After approval, your username, display name, biography, profile photo, submitted entries, optional captions, place labels and tags, comments, replies, comment reactions, challenge results, and social counts can be visible to other signed-in testers. Group names and group photos are available only to current members of that group. Direct/group messages, entry cards, chat photos, and voice notes are available only to current conversation members; they are not public, but a specifically reported message and its safety context can be reviewed by authorized PikkMe moderation systems. Reports, blocks, account-recovery details, push delivery tokens, automated safety signals, beta feedback, and a moderator's optional reply to a reporter are private. Recipients can still save or reshare what they receive, so do not send information you do not want them to keep.

Build 19 offers optional remote notifications for the daily lens, results, Pikks, comments and comment reactions, replies, followers, private messages, quiet digests, and completed report or feedback reviews. If you enable them, we register a delivery token for your signed-in account and send limited notification text and routing identifiers through Expo and your platform notification provider. Notifications are grouped and may show a username and activity type on your lock screen. PikkMe does not put a challenge photo, comment body, reply body, private-message body, or moderator response in these remote activity notifications.

You can turn off individual categories or all phone notifications in PikkMe, and control lock-screen previews in your phone settings. In-app Activity remains available if you decline. Switching accounts detaches the registered token from the old profile; account deletion removes its registered devices and pending delivery records. Turning notifications off stops delivery but does not itself delete your account or in-app Activity.

PikkMe uses Google Firebase and Google Cloud for authentication, database services, server functions, photo storage, and automated photo safety analysis through the EU Cloud Vision endpoint; Expo for application builds and remote push delivery; Apple for TestFlight, Apple Push Notification service, device-local notifications, and optional Sign in with Apple; Google Firebase Cloud Messaging for remote notifications on supported Android builds; Cloudflare for the PikkMe domain and related network services; and OpenAI Sites for this public information website. These providers may process information in countries outside your own under their applicable safeguards and terms.

Entries and related activity may remain available as challenge history and winner records while your account exists. Messages and their media remain in a direct or group conversation unless you hide or leave it, a sender deletes their account, or moderation removes a reported message. Leaving a group immediately removes your access. Safety records are retained while needed to investigate and prevent misuse. You can permanently delete a non-owner account inside PikkMe from Profile → Account & recovery → Delete account. For an Apple-protected profile, PikkMe first asks you to reauthenticate and revokes the associated Apple authorization. The deletion process removes the Firebase account, profile, usernames, entries, stored photos, votes, saved Pikks, comments, follows, notifications, reports, safety records, feedback, transfer records, sent chat-media files, and message identity associated with that account; authored messages are redacted so remaining participants' threads are not silently rewritten. Limited records may be retained where required by law, to resolve a dispute, or to protect the service from fraud or abuse.

You can edit your profile, replace or remove your profile photo, disable reminders and activity notifications in PikkMe or your phone settings, report content or a profile photo, block and unblock real accounts, protect a guest profile with Apple on iOS, and delete your account. Depending on where you live, you may also have rights to request access, correction, restriction, objection, portability, or deletion. Send a request through the in-app beta feedback form or visit Support.

We use authentication, access controls, storage restrictions, server-side voting, rate limits, and private moderation tools designed to protect the beta. No system can guarantee perfect security. We may update this policy as the product changes and will post a new effective date here. For privacy questions, use the in-app beta feedback form or email privacy@pikkme.app.