Privacy Policy

Blipze, operated by Vadlamudi Vamshi Krishna (“Blipze”, “we”, “us”), is a social platform for people, Blips, polls, groups, topics and nearby conversations.

• Account data: email, authentication data, display name, username and avatar.
• Private product feedback: the category and message you submit, linked to your signed-in account, plus the submission time and limited browser details to help us respond and troubleshoot. The feedback form does not ask for a separate name or contact detail.
• Social content: Blips, images, polls, comments, groups and reports sent to social-content moderation.
• Activity: follows, reactions, votes, memberships, notifications and timestamps.
• Optional view counting: after you allow it and service counting is enabled, Blipze links eligible viewing activity to your signed-in account to help creators understand their reach through totals and unique-account counts. Blip appearances can include scrolls, repeats and your own views; eligible Flash openings can also contribute. Signed-out, undecided and declined accounts do not contribute optional views. This choice does not grant permission to disclose a named viewer list, and we do not use it for advertising or cross-site tracking.
• Preferences: language and selected topics. Nearby location is not saved.
• Private profile data: any address or verification details previously provided remain access-controlled and are not part of the public profile.

Your username, display name, avatar, Blips, public comments, public groups and aggregate social counts may be visible to others. Email, phone, residential address, authentication identifiers, exact location, moderation notes and private preferences are not exposed in the public profile or public search.

Product feedback is private and associated with your account; it is not a public Blip or an anonymous submission.

Ping is one-to-one messaging, not public content. We process message text, photos, voice notes, reply and shared-Blip references, reactions, participant identifiers, timestamps, requests, settings, private reading position and delivery state to deliver and secure conversations. Pings are not end-to-end encrypted: Blipze and its service providers can process their contents to operate the service, handle reports and meet legal obligations. Recipients can save or share what they receive outside Blipze. Using Download for a photo or voice note saves a separate copy on your device.

Read receipts start on for new accounts; existing accounts keep their previous setting. You can turn them off in Ping settings. Turning them on later does not disclose earlier reading. Delivery acknowledgements and private unread state still operate when read receipts are off; a delivery acknowledgement means a recipient client received the message, not that a person read it. An offline or closed app cannot acknowledge receipt; a sent message becomes delivered after a connected recipient app receives it, even without opening that chat. Read receipts reflect visible messages in the active chat. Until a request is accepted, its photos and voice notes stay hidden from the recipient and neither participant receives delivery/read receipts. Accepting a request does not follow the sender. Manage these choices in Ping settings.

Voice recording begins only when you select the microphone and permit access. You can record up to sixty seconds, preview or remove the note, then choose Send. Voice notes play inside the chat; there is no automatic transcription or background recording.

Message bodies, photos and voice notes remain as conversation history until a verified authored-content erasure request or account deletion, subject to applicable preservation requirements. Clear for me hides existing history only for you; Delete for me hides the selected message for you; Decline closes a request. These actions do not erase stored messages. Verified erasure removes your authored message bodies and photos and voice notes from normal in-app chat history, including the recipient’s in-app copy. It cannot recall screenshots, downloads or copies saved outside Blipze.

Technical records are separate from message bodies, photos and voice notes. Message and participant identifiers, content-derived fingerprints used to prevent duplicate sends, timestamps, receipt/request state and abuse, quota and cleanup records can remain after content erasure. Your hidden-message choices and reading position are private to your account; reactions are visible to the conversation participants. There is currently no automatic expiry for these records or reports; retention is reviewed separately for operation, safety, resolving reports and applicable legal obligations.

Reporting shares the selected received message’s text, sender details and attached photos or voice note still available with authorised moderators, not your whole conversation. A report keeps its saved text and details separately from ordinary chat history; erasing that history does not automatically erase the report. Report handling is reviewed daily, with monthly retention checks. Each case records its purpose and review or deletion date. Closed-case material is removed when its purpose and applicable preservation requirements end.

For access, correction or erasure, email support@blipze.com. We verify ownership, check preservation requirements and limit any disclosure of the other participant’s information. Clearing, declining or switching off receipts is not an erasure request.

Nearby is opt-in. If you choose to use your current location, the browser supplies coordinates for that request. Blipze compares them with public locality centroids on the server and does not store or display your device coordinates or save Nearby to your profile, cookies, or browser storage. You control the browser permission and can decline it. Topic preferences are private to your account, with a limited browser fallback for signed-out use.

Supabase Auth handles email/password and Google sign-in. Google sign-in uses the standard basic identity scopes needed to authenticate and create your profile; Blipze does not request Gmail, Drive, Contacts or Calendar access and never receives your Google password. Essential cookies and browser storage keep sessions and preferences working.

We use information to:

• create and secure accounts;
• publish and personalise the social experience;
• deliver Following, topic, group and Nearby feeds;
• use your private, explicitly selected interests and follows to arrange For You and discovery suggestions; browsing a topic does not save it as an interest, and optional view-count records are not used for this ordering;
• operate moderation, safety and abuse-prevention controls; and
• respond to feedback and improve reliability.

We do not sell personal information or share it for advertising.

Blipze uses Supabase for authentication, database, file storage and live updates; Vercel for hosting and delivery; Google when you choose Google sign-in; and a configured geocoding provider for coarse Nearby lookup. Each provider processes the limited data needed to deliver its service under its own terms and privacy policy.

When you allow Blip view counting and service counting is enabled, private unique-account associations remain while the Blip and account exist. Temporary impression receipts and request budgets expire after 24 hours and are removed by bounded maintenance with a 48-hour target. Permanent deletion removes linked records; non-identifying historical totals may remain. This feature does not store IP addresses, location or device fingerprints in its counting tables. Offline, restricted or failed requests may be missed. Hosting and security logs are separate and may process network information.

Choose or withdraw optional counting in View privacy. After an off choice saves, your future activity does not add optional views or account associations, and view totals on your own and others’ Blips and Flashes are hidden for your account behind “Views off”. Other people who allow counting can still add views to your content. Allowing later does not add earlier activity. Switching off does not erase earlier committed records or historical totals and does not delete your account. You can request access to or removal of your private view-count associations through support@blipze.com; we verify your identity first. Erasure preserves your saved off preference. If you later allow measurement and view a Blip after erasure, your account can be counted anew. These are historical impression/account totals, not verified people or an exact lifetime census; failed or excluded appearances may be missed.

Flash one-view delivery, access checks and expiry operate independently of optional analytics. Flashes are available for 24 hours; their delivery records follow the existing cleanup lifecycle. Opening a Flash does not, by itself, grant optional counting or named-viewer disclosure permission. A saved Allow choice cannot activate service counting while its separate global control is off.

We use transport encryption, access controls and database row-level security. No online service can guarantee absolute security. We keep data while an account is active and as reasonably needed to operate the service, preserve conversation and moderation integrity, prevent abuse, and meet legal obligations.

The former public civic-reporting product has been retired. Its issue records, images, lifecycle history and moderation evidence remain preserved in access-controlled backend storage for integrity and operational reasons, but they are no longer exposed as public Blipze routes, search results, profile tabs or notifications. Previously supplied civic-report coordinates may exist in those historical records; this is separate from the coarse-only Blipze Nearby feature.

• Update your public profile and topic preferences in the app.
• Manage content and social relationships using the controls provided.
• Allow or stop optional Blip/Flash view counting and choose whether to see view totals in View privacy.
• Withdraw browser location permission in your browser settings.
• Revoke Google access in your Google Account settings.
• Request correction or deletion by emailing support@blipze.com. Requests are subject to identity verification, legal obligations, safety, moderation and record-integrity needs.

Blipze is intended for people aged 18 and above. Contact us if you believe a child’s personal information was submitted without appropriate involvement from a parent or guardian.

Questions about privacy? Email support@blipze.com. You can also read our Terms of Service and Cookie Use notice.