Updated October 1, 2026

Privacy at Bynesh

What we collect, why we collect it, how we protect it, and the controls you have.

Your data rights Delete your account

Pluria is now Bynesh

Bynesh is the new name for Pluria. This policy covers accounts and data from Pluria as well as new Bynesh accounts.

Account and sign-in data

What: Your email and password (handled by our sign-in providers), your phone number, any Google or Apple account you’ve connected, the browsers and devices where you’re signed in, and a record of how you’ve signed in before.
Why: So you can create an account, sign back in, recover access if something goes wrong, get security notifications, and so we can stop people abusing the service.
Required or optional: A phone number, confirmed with a code we text you, is required to finish setting up an account. A confirmed email address is also required before you can vote or publish polls. Google and Apple details are only collected if you sign in with those services.
Public or private: Private. Your sign-in and recovery details never appear on your public profile.
GDPR / legal basis: Needed to provide the account you asked for, plus a legitimate interest in keeping it secure — and legal obligations when they apply.

Profile and content data

What: Your @username, display name, first and last name, avatar and cover image, bio, pronouns, interests, languages, occupation and education (if you add them), website, social links, the polls you publish, the comments and reactions you make, the people you follow, the messages you send in conversations (including to Pages, whose team members can read them), and a timestamp for what you create.
Why: So we can run your public profile, your publishing tools, search, credit you on polls, moderate the platform, and build the public poll pages.
Required or optional: Your @username is required so we have a stable way to identify you. The other profile fields are optional — you can skip them or edit them anytime. Sending messages is optional.
Public or private: What you publish and the profile fields you fill in can be public. Drafts, our moderation notes, abuse signals, and internal review records stay private. Messages are private to the conversation and, for a Page, to its team. If a message or conversation is reported, our moderators may review it.
GDPR / legal basis: Needed to provide profile and publishing features, plus a legitimate interest in moderation, safety, and keeping the service fair.

Demographics and eligibility

What: Your confirmation that you’re 13 or older, your age range, the country you live in, and your gender (if you choose to share it).
Why: To confirm you’re old enough to use Bynesh, to show results by region, to adjust the app for the country you’re in, and to make demographic breakdowns more accurate. For voting, this information is counted separately from your individual answer.
Required or optional: Confirming you’re 13+, your age range, and your country are required to create and use an account. Gender is optional. We don’t need your full date of birth to sign you up.
Public or private: Your age confirmation stays private. Country, age range, and gender stay private too — unless you choose to show them on your profile.
GDPR / legal basis: Needed to provide the service and for our legitimate interest in age checks, regional features, and keeping results fair. If local law treats one of these fields as sensitive, sharing it stays optional.

Voting privacy data

What: A private record that your account voted on a poll, the one-time pass we use to make sure the same person can't vote again, and the counts that make up each poll's totals. The answer you picked is not stored next to your account.
Why: So each person votes once, so we can show you a "you voted" state, so we can tell you in the app when results are in (if you turn that on), and so the totals count everyone who was allowed to vote.
Required or optional: Required when you vote. Starting a vote needs a connection. If the connection drops partway through, the app keeps an encrypted copy and tries again, and the vote only counts once we confirm it.
Public or private: The fact that you voted is private. Poll pages show totals, never an answer tied to your account.
GDPR / legal basis: Needed to provide voting itself, and a legitimate interest in keeping each poll honest and protected from repeat voting and abuse.

How your vote stays private walks through what happens when you vote.

Notifications, contact, and support

What: Your notification preferences, any notification connections saved for your account, any emails you send to support, your account-help requests, and public contact details (like your website or public email) if you choose to share them. Push notifications aren’t available yet, so your alerts appear in the app’s inbox. When we turn push on, we’ll need a code from Apple or Google that lets our push provider reach your phone, and push stays off until you turn it on.
Why: So we can show the alerts you ask for in the app’s inbox, send important account messages, respond to your support requests, and let you decide which contact details appear on your public profile.
Required or optional: Push notifications (when they’re available) and marketing emails are optional. Sending us a support message is optional too — but if you do, we’ll handle it.
Public or private: Support messages always stay private. Contact fields only show on your profile if you choose to turn them on.
GDPR / legal basis: Needed for account messages, with your consent for optional notifications and marketing, and a legitimate interest in running support and keeping the service working.

Purchases and billing

Bynesh doesn’t sell anything today. This section covers records from purchases made in the past, and any paid plan we add later.

What: Which product you bought, whether your subscription is active, whether it was paid through Apple or Google, the purchase reference for that transaction, any restore attempts, a link to manage the subscription, whether the subscription is for you or for a Page, and any support emails about the purchase.
Why: So we can confirm that a purchase is active, apply it to the right person or Page, help you restore it, prevent fraud, answer billing questions, and meet our tax, accounting, and dispute obligations.
Required or optional: Only collected if you make or restore a purchase, or get in touch about billing.
Public or private: Private. Billing and purchase information never appears on your profile or on public pages.
GDPR / legal basis: Needed to provide what you bought, plus a legitimate interest in fraud prevention and support — and legal obligations for financial records where they apply.

Device, diagnostics, analytics, and ads

What: Information about your device and app — like the install ID, IP address, IP-derived approximate location, app version, error reports if you choose to send them, language, basic device information, app interactions, advertising data, and device or account identifiers. On Android this may include the advertising ID. On iOS, Bynesh may ask for App Tracking Transparency permission before Google Mobile Ads can access the IDFA; you may decline and still use the app.
Why: So the app stays stable, we can fix app errors, reduce fraud, show a limited number of ads and see how they perform, and improve the app. When mobile ads are on, Google Mobile Ads receives the limited device, interaction, diagnostic, identifier, and advertising information it needs for ads, analytics, and fraud prevention. We never send poll text, the answers you pick, your age, country or gender, or your account ID to target ads.
Required or optional: Mobile ads are shown only to signed-in users whose resolved age range is 18 or older. They are requested as non-personalized ads. The app checks Google's consent status before starting the ads SDK or requesting an ad, and provides ad privacy choices where Google marks them as required. Basic stability and anti-fraud processing remains necessary for the service to work. Error reports are off unless you turn them on in the app's settings. When on, they are linked to your account, include error categories, code locations and app versions (and, on Android 11 or later, fixed codes for app crashes), exclude error messages, photos and private answers, and are scheduled for deletion after seven days. The app has no separate crash-reporting service, and app analytics are not turned on.
Public or private: Private. None of this appears on your public profile.
GDPR / legal basis: Legitimate interest and contract for security and fraud prevention; your consent for error reports and where it’s required for ads.

Cookies and browser storage

What: Cookies that keep you signed in, short-lived browser storage used while you approve a sign-in, and local storage that remembers your choices. The website doesn’t show ads, so no advertising partner stores anything in your browser. Some requests are checked by a bot-protection script from our hosting provider (Vercel BotID) that runs in your browser to detect automated abuse.
Why: So we can keep you signed in securely, finish a sign-in you started, and remember choices such as your language.
Required or optional: Security and sign-in cookies are needed for anything that needs you to be signed in. Everything else is optional.
Public or private: Private. What your browser stores isn’t public.
GDPR / legal basis: Needed to keep sign-in secure, and a legitimate interest in running the site.

What is public and what is not

Private: Your sign-in details, age confirmation, phone number, verification recordings, the record that you voted on a poll, your conversation messages, support messages, our review notes, device and fraud-prevention information, and any requests you make for your data.
Can be public: Your username, display name, avatar, website, social links, the Pages you post as, the polls and posts you publish, and poll totals.
Public only if you turn it on: Your country, age range and gender show on your profile only if you choose. When a breakdown would expose too few people, we hide it. None of this is ever linked to the answer you picked.

Identity verification

We aren’t offering identity checks for personal accounts at the moment. This section covers the checks people completed before, and applies again if we bring them back.

If you choose to verify your identity, we ask you to agree first. We then collect a short front-camera video, a preview frame, a record of the steps you completed, the reviewer's decision, and a note of which consent version you agreed to.

We also tie the verification to your specific app install so one person can't make multiple verified accounts on the same device. The recordings are used to confirm your identity, prevent fraud, handle disputes, and let moderators review unusual cases. They are never used for advertising and never appear on your profile.

Verification is always optional. We only keep what we still need for review, fraud prevention, disputes, or legal reasons.

Phone permissions and optional features

Camera: Only used when you choose to take a photo, record a video, or scan a QR code to sign in on the website.
Microphone: Only used when you choose to record a video.
Photos and media library: Only the photos or videos you choose to upload. Sharing a result image uses your phone's share sheet; Bynesh does not save it to your photo library.
Location: Bynesh does not ask for your device's location. The country on your profile is the one you choose; the app may suggest it from your phone's region setting. Approximate location derived from your IP address is described under "Your device and ads".
Push notifications: Not available yet. Your alerts appear in the app's inbox. When push is turned on, it will only be used if you allow notifications on your phone.

You control these permissions on your device. If you turn one off, your account still works — but features that need that permission won’t.

How long we keep things, and deletion

Once your deletion request is accepted and recorded, your public profile and your public polls, comments and posts are hidden. If you ask by email, we may need to confirm account ownership first; sending the email does not itself hide the account. Someone on our team deletes the account — sign-in details, profile, saved settings and uploaded files — within 30 days of your request. You can sign back in to cancel only before permanent deletion starts. Once it starts, cancellation and restoration are no longer available, even while other deletion steps are still being completed.

Copies of deleted data can stay in our backups for a limited time, until those backups expire.

A few records may be kept to protect past polls and prevent fraud: the fact that votes were cast, the counts behind poll totals, and fraud-prevention logs. These records do not link your individual answer to your account. Messages you sent to other people or to Pages may stay in their conversations, and content you posted for a Page stays with that Page. Verification recordings, review decisions, and the link between a verification and a device may also be kept while we still need them for moderation, fraud prevention, disputes, or legal obligations.

Retained security and deletion records may still relate to you; they are not necessarily anonymous. You can ask which records remain, why they are needed, and the retention period or criteria that apply to them.

Billing support records, proof of an active subscription, and a small amount of financial or fraud evidence may stay too — where we need them for refunds, disputes, tax, or accounting. Remember: deleting your Bynesh account does not on its own cancel an Apple or Google subscription.

If you’d like us to delete your verification or process a consent withdrawal before the full account is closed, email account@pluria.org.

Deleting your account explains the whole process.

The companies we work with

To run Bynesh we use trusted partners for things like sign-in, cloud hosting, storing data, error reports you choose to send, checking app-store purchases, sending messages, customer support, moderation tools, and ads when they are on.

Each of those partners only handles the data they need for their job, under their own terms and security rules, and — where it applies — under our instructions. Apple and Google handle payment details directly for any app-store purchase. For mobile advertising, see how Google uses information from apps that use its services.

What you can choose

Use the privacy controls in the app to decide what appears on your public profile.
Ask us to delete your account in the app, or email account support for a copy of your data or any other privacy request. Downloading your data in the app isn’t available yet, and tapping that option doesn’t send us a request.
Add or remove ways to sign in and optional contact details in your account settings.
Turn off optional permissions on your phone whenever you want.
If you subscribed in the past, manage or cancel it through Apple or Google.
In the mobile app, open Account → Privacy & data → Ad privacy choices whenever Google marks the regional privacy-options form as required. You can also change Apple's tracking permission in iOS Settings.
Read your data rights for the rights you have under GDPR.

Get in touch

For privacy or account questions, email account@pluria.org. For everything else, email support@pluria.org.