Fanaraa Privacy Policy

Fanaraa is operated by Fanaraa for Technical Solutions and Innovation, a registered Palestinian company responsible for the processing described here; its registered Arabic name appears in the Legal Notice. This policy covers Fanaraa's website, app and related professional spaces. Fanaraa supports discovery of works, profiles, taste, social interaction and creator and team activities. For privacy requests use the Data Rights Requests page or privacy@fanaraa.com, with support@fanaraa.com as a fallback; see the Legal Notice for published operator information.

Data includes email, username, display name and authentication information, plus any profile image, biography, date of birth, gender, country, language, interests, links and professional details you provide. Google sign-in supplies the identity and account information needed for that sign-in route. Required and optional fields depend on the form; do not send your Google password to Fanaraa.

We process content you publish or send, including reviews, ratings, lists, posts, images, clips, comments, messages and attachments. We may also process support tickets, reports, rights evidence, representation details, professional applications and order, transaction and reward records when you use those features. Do not send identity documents or full financial details unless requested through an appropriate secure route.

Connections may record your IP address, browser information sent with requests, request and session identifiers, login and usage times, and authentication successes or failures. These records support sessions, abuse detection and troubleshooting. An IP address can indicate a network or approximate region; it is not precise GPS location.

When notifications are enabled, we process the platform, app push token or browser subscription and its keys, a random installation identifier, enabled status and activity, sending and delivery acknowledgement times where available. The random identifier helps manage a notification device when its token changes; it is not an IMEI. You can refuse or revoke notification permission in device or browser settings and manage devices and categories in available settings.

The Android app does not require camera, microphone, precise location or contact-book access for its current core features. Selecting a file to upload shares the file you choose; it does not grant unrestricted access to your device. Permission needs must be explained when a feature requests them.

We process interactions, searches, content preferences, viewing signals and active browsing intervals associated with your account to support discovery, recommendations, statistics, community features and abuse prevention. Account activity measurement differs from optional advertising tools on public pages; rejecting marketing cookies does not stop every operational account record.

Profile information, content and activity are visible according to the feature and available visibility settings. This may include online status, last seen, read receipts, lists and birthday information where settings allow. Public pages may be indexed by search engines or shared outside Fanaraa. Review settings before publishing; changing them does not recall copies others have already saved.

Messages and attachments are stored to deliver them to participants and provide conversation history, notifications and safety controls. Fanaraa does not describe these conversations as end-to-end encrypted. Content may be processed automatically to detect abuse or malicious files; authorised staff may review information relevant to a report, support request or security investigation within their permissions.

Some content review paths use OpenAI to process text or images and assess safety. When you use an automated agent feature, inputs and context needed to generate a response may be processed by its provider. Automated systems can make mistakes; you can request a decision review through Support or appeals. Do not place secrets or highly sensitive information in content you send to these features.

Data is used to provide requested features, secure accounts, improve the service, enforce rules and handle rights claims, disputes and legal obligations. Where a purpose requires consent, such as an optional advertising integration or device permission, you can manage that consent separately. Accepting the terms does not waive statutory privacy rights.

Technical services used include AWS for hosting, file storage and email delivery depending on the service path; Google for sign-in and advertising when enabled; Expo and operating-system notification delivery services such as Firebase Cloud Messaging on Android; and OpenAI for the AI paths described above. Each service receives data needed for its function; a notification may include a title or content excerpt depending on its type and settings.

Authorised team or workspace members may access information needed for their role. We may disclose information in response to a valid legal request or to protect rights and safety, considering necessity and scope. Technical providers may operate in countries other than yours; processing locations depend on the provider and service setup. Ask through the privacy channel about transfer arrangements and safeguards; we do not claim certification or guaranteed data residency in a particular country.

Where applicable law requires a processing basis, we distinguish providing the service you requested and performing the contractual relationship, legitimate interests in account protection, fraud prevention and service improvement balanced against your rights, compliance with a legal obligation, and consent for optional purposes that require it. You can ask which basis applies to a particular purpose or object where the law permits. Refusing processing necessary for sign-in or content delivery may prevent that feature from working; rejecting optional advertising does not mean closing your account.

Account and content data is retained to operate the account and related features while its purpose continues. Sessions and verification tokens expire according to their type; expiry does not necessarily erase the record immediately. Cookie choices are stored for up to 180 days. Security, acceptance, report, rights and transaction records may be retained when needed to document an action, resolve a dispute or meet a legal obligation, with use limited to that purpose.

Erasure of messages and files depends on the deletion type, conversation policy and whether a file is linked to other content. File and backup removal may take additional time; we do not promise instant deletion from every copy. When requesting deletion, ask which data remains, why it is retained and when retention will be reviewed. Turning off notifications or signing out does not delete your account.

We use authentication, permissions and controls for sessions and private file access. Passwords are stored as verification hashes. No service can guarantee absolute security; protect your email and device, enable available account security features and do not share login codes or private file links.

You can edit available profile and privacy settings and request access, a copy, correction or deletion of data, object to or restrict processing, and withdraw consent where applicable. Rights, lawful bases and mandatory deadlines depend on applicable law and your circumstances; this text does not restrict your right to complain to the competent supervisory authority. We may verify your connection to the account to protect your data and others' rights. See Data Rights Requests for practical steps.

Fanaraa is intended for people aged at least 13, subject to higher local requirements. Report underage accounts or risks to a child without sending exploitative material. Privacy updates are published with a clear date; any new purpose or additional permission must be explained before use where required.