← Back to Yaaber

Privacy

Effective 20 October 2026

The short version: Yaaber can be used as a guest. Guest interests stay in your browser. If you sign in, Yaaber stores your profile settings, topic preferences, saved reels and reports so they can follow your account.

Account age checks

New registrations, including invitation activations, ask for your date of birth to check that you are at least 16. The date is sent securely to our server for this check. It is not saved to your account or shown to other members. This initial check relies on the information you provide; it does not independently verify age. Existing accounts are not rechecked by this update.

Information we process

When you create an email account, we process your email address, display name and password to authenticate you; the account database stores a salted password hash rather than the password itself. When supported sign-in services are used, we receive an account identifier, email address and available name. Session records keep you signed in. We store the interests you choose and signals you deliberately create in Yaaber, such as likes and saves. Yaaber does not receive your Facebook, Instagram or Google password.

Reel discovery preferences

Yaaber uses approximate city, region and country supplied by its hosting service to suggest nearby content. You can choose a different city or worldwide discovery in Your interests. We do not request GPS access. Searches and discovery requests send the selected place and topics to YouTube; video location does not tell us where its viewers live. Dietary preferences are your selections and are not inferred religion or verified restaurant certification.

When feed learning is enabled, actual foreground playback, quick skips, likes, saves and broad topics from searches adjust your recommendations. Paused, buffering and background time do not count as watching. Guest preferences and topic scores stay in browser storage. Signed-in preferences and topic scores are linked to your account; guest behaviour is not automatically imported. We do not store a raw search history for this feature. Turn learning off in Your interests to stop using and collecting behavioural signals; explicit preferences continue to apply. Account deletion removes account preferences and scores; clearing browser data removes guest preferences.

Connected YouTube accounts

If you choose to connect YouTube, Yaaber requests read-only access and analyses accessible subscriptions and liked videos to infer broad interest categories. Google does not provide watch history through this API. Yaaber stores the resulting topic scores and an encrypted authorization token so you can refresh them later.

In addition to disconnecting YouTube in Yaaber, you can revoke Yaaber’s access to your Google account through Google’s security permissions page.

Connected Facebook accounts

If you choose to connect Facebook, Yaaber requests basic profile access and, where Meta approves the permission, your liked Pages. Yaaber uses Page names and categories to infer broad interests. Meta does not provide Yaaber with your private feed, browsing history, Facebook password or private messages. Yaaber stores the resulting topic scores and an encrypted authorization token.

Yaaber connections and messages

If you choose a username, other signed-in Yaaber members can find your username and display name by searching the beginning of your name, username or email address. Your email is not shown in member search. We store connection requests, private messages, shared reel and news links, read status, blocks and reports. Direct conversations use participant and connection access controls; group conversations are available to their authorised participants. Text messages are not end-to-end encrypted. Optional audio and video calls use WebRTC in the browser or supported native app and require your permission to access a microphone or camera. Yaaber does not record calls; temporary connection information is stored to establish them and is cleared on hang-up or later cleanup. Call availability and background operation depend on the app version, enabled features, permissions and device settings. WebRTC connection setup may disclose network addresses to the other participant and to connection or relay providers. Optional call and message notifications can alert an enabled device while the app is closed. Message alerts show the sender’s name and the type of shared content; tapping an alert opens its conversation. Enabling alerts stores an encrypted-notification endpoint and device keys, linked to your current login session. Signing out disables that session’s alerts. Your browser or operating system’s push service delivers the encrypted notification. On Android, native call notifications use Firebase Cloud Messaging. When native call registration is enabled, Firebase creates an installation identifier and messaging token; Yaaber stores the token and registration information linked to your account session to deliver call alerts. Firebase also processes service and app/device information needed to operate messaging. Notification delivery depends on device settings and connectivity. You can turn off notifications in device settings. Signing out revokes Yaaber session access; it does not by itself promise deletion of identifiers held by notification providers. Deleting your account also removes your connections and their conversation history.

Problem reports

When you choose Report a problem and press Send, Yaaber privately stores your contact email, the description you enter and the technical details shown in the form: feature, a general error code, app release, browser family, device type and time. We do not automatically include conversations, passwords, recordings, full browsing addresses or screenshots. Signed-in members may explicitly attach a PNG or JPEG screenshot; review it for private information first. Guests provide a contact email and can submit text only. Signed-in reports use the supplied contact email or the account email so support can reply. Reports are accessible only to the Yaaber owner and, for signed-in reports, the reporter. A short reference and private dashboard link are sent to support@yaaber.com, without your report text, identity or screenshot. There are no automatic follow-up messages. New and in-progress reports remain available until resolved or your account is deleted. Resolved report content and screenshots are removed after 90 days through bounded cleanup; unsent draft text stays only in this page until it is closed or the account changes. Minimal submission and email-deduplication records may remain to prevent duplicate messages. Account deletion also removes your problem-report content and screenshots.

Posts, profiles, family and communities

We store the profile information, photos, videos, posts, comments, wall notes, messages and attachments you choose to submit. We also store your connections, family relationships, organisation follows and community participation. Visibility depends on the audience and access controls for the feature. Review the audience before sharing; other participants may retain copies of content they can access.

Usage analytics

Yaaber uses Google Analytics to measure visits and feature use, such as opening content, signing in and sharing. Google processes device and browser information, interactions, page information and analytics identifiers such as cookies. IP addresses can be used to derive approximate location. Guest browsing can also generate analytics measurements. Custom feature events use limited categories rather than message bodies. Google's own service settings and policies govern its processing. These measurements help us understand usage and improve the service.

Account emails

Account invitations, welcome messages and password-reset emails are delivered through our email service provider. Invitation and delivery records help us prevent duplicate messages and manage access. Support reports may include the contact email you supply so support can respond.

Content providers

Reels and news are fetched from third-party services such as YouTube and The Guardian. Opening or playing their content may send those providers device and network information, identifiers and viewing interactions under their own policies. Embedded YouTube content may display advertisements. See Google Privacy Policy. Hosting, storage, email delivery and notification providers also process data needed to provide Yaaber. These providers may process information outside your country.

Delete your Yaaber account and data

In Yaaber, sign in, open Profile, then the account menu, choose Delete Yaaber data and confirm. You can also request account deletion without installing the app: email support@yaaber.com from your registered email address with the subject “Yaaber account deletion”. We may need to verify account ownership before acting. Never send your password. This request covers the account and associated Yaaber profile, preferences, stored content, messages, connections and notification registrations; minimal security, abuse-prevention and delivery-deduplication records may remain. Provider-held data and copies already retained by recipients are subject to their own controls.

Retention and other controls

Account and social data are kept while needed to provide the feature or until removed through its controls or account deletion. Support-report retention is described above. If deletion fails or you need help with remaining data, contact support@yaaber.com.

You can use Yaaber without signing in, change your interests, disconnect YouTube or Facebook, clear browser data, or delete your Yaaber profile from Account. Disconnecting removes the provider token and imported signals. Account deletion removes Yaaber’s stored profile, preferences, saves, connected-account tokens and reports.

Contact

For privacy questions or account-deletion assistance, contact support@yaaber.com or use the feedback/report controls inside Yaaber.