Contact SAFFER Support without signing in.
Account & data deletion →01Who is responsible and how to contact us
SAFFER, operated under the SafferStudio name by the SAFFER team in Iraq, is responsible for the processing described in this notice. Contact SAFFER Support at [email protected] for privacy questions, corrections, access or deletion requests, complaints and appeals. You can contact us without a SAFFER account. This is SAFFER’s notice, not Meta’s, a game developer’s or an external store’s privacy policy.
02One service, different features
This notice covers saffervr.com and the SAFFER Meta Quest application. They share account identity and supported account records; changing or deleting a shared account can affect both. The website provides discovery, reviews, saved items, account/support tools and a local USB installer. The Quest app additionally provides the social posts, private messages, groups, studio/developer channels and voice-room features available in its version. A feature described here is not a promise that it exists on every device or website page. Third-party purchases and a separately authorized SAFFER Backups/Google Drive connection have additional notices.
03Information you provide
Account data includes your email, authentication and recovery records, chosen display name and username, avatar, biography and links, private birth date/age, country of residence, device preferences and account settings. Your country is self-reported, not verified nationality or GPS location. Birth date and email are not public profile fields. We use this information for account access, eligibility, security, profile presentation, device guidance and support. Authentication is handled through Supabase; support staff do not need your password, one-time code or recovery secrets.
04Content, messages and social connections
We store content you choose to submit: posts, comments, reviews, reactions, votes, message text and attachments, group/channel information and membership, followed accounts, saved items, wishlist entries and reports. We also process message delivery/read state and notification preferences to operate the chosen features. Public content and permitted public profile fields can be seen by others; private conversations are limited by access controls. A recipient can copy, forward or screenshot content. Blocking, editing or deleting does not recall copies already held by others. Messages are not advertised as end-to-end encrypted.
05Photos, videos and device permissions
Media is processed when you select it for an available upload feature, such as a profile image, community post, chat attachment, support case or an authorized managed listing. File names, formats, sizes and embedded metadata may accompany a file; original high-resolution files can retain identifying or location metadata. Remove sensitive metadata before uploading. Account role and technical limits determine which formats and video uploads are available. Gallery selection is different from camera capture. Android media permissions depend on the OS and picker; refusing an optional permission can prevent that feature without granting us access through another route.
06Headset inputs and sensor boundaries
The current Quest experience is a 2D application controlled through supported system pointer/controller or hand input. Ordinary interface interactions do not imply collection of raw eye tracking, body tracking or spatial room maps by SAFFER. Gallery access and microphone use have the specific purposes stated here. The legacy camera-review capability is separately disclosed below; future immersive or sensor features require a fresh explanation and any necessary permission.
07Live voice, background calls and local testing
With microphone permission and your voice controls, the Quest app captures microphone audio for transmission to participants through SAFFER’s LiveKit-based voice infrastructure. Room/account IDs, presence, mute state, connection data and moderation actions support the call. SAFFER’s room feature does not include routine server-side recording of conversations. Separately, the explicit voice-effects test records a short microphone sample in device memory for local playback; the test implementation does not upload that clip, and clears it after playback or cancellation. Other participants or system recording tools may record what they hear. A call can remain active when you switch apps; use Mute or Leave rather than assuming that hiding the window stops the microphone. Device/OS restrictions can interrupt background audio.
08Age, camera verification and earlier test builds
SAFFER accounts are intended for people aged 13 or older, subject to higher local or feature-specific requirements. Birth-date entry is a declaration, not identity verification. Camera-based identity-document verification has been deferred for the planned public release. Some earlier Quest test builds still contain a separate camera age-review flow; do not submit identity documents through it or through ordinary chat/email. If you previously used that flow, its submitted document images, capture code, request and decision records can exist in restricted review storage. Contact Support to request access or deletion; postponing the feature does not itself erase previous records. This notice does not turn on camera access or claim that old APK permissions have already been removed.
09Website USB installation
The optional website installer uses browser-authorized USB/ADB access to a device you control. It reads connection, model, battery and storage information to show installation status and transfers the APK you select from your computer directly to the headset. That local installer does not upload the APK or its displayed device diagnostics to Supabase. An ADB trust key and recent-install history are stored locally in your browser. Previously authorized connected devices may reconnect automatically. Disconnect in the tool, revoke USB debugging authorizations on the headset and clear site data to remove local trust. Clearing a queue does not uninstall apps.
10Diagnostics, security and website measurement
Hosting, authentication and delivery systems process technical requests, including IP addresses, timestamps, browser/device information, errors and abuse-prevention records. Some sign-in/rate-limit identifiers are hashed; that does not make all records anonymous. In this website update, optional measurement is off until you allow it on the Cookies & Storage page. When allowed, website measurement records public-page/game views and store/download clicks with a session token, broad browser/device category and available country/device preference context. The measurement table does not store raw IP addresses, although infrastructure logs can. Detailed website events are configured for cleanup after 90 days; daily totals without session tokens support longer historical comparisons. Published game totals and restricted developer/owner breakdowns have different audiences. This is not a promise that no analytics occurs.
11Discovery, preferences and guest sessions
Available discovery features use categories, viewed content, followed accounts, feedback and saved preferences to order recommendations. Optional personalization controls can reset or disable the supported signals; they do not erase every operational log. Quest guest-session counting uses a random session token, a server-side hash and timestamps rather than a guest name/email. Configured cleanup removes inactive session records after 24 hours and retains guest daily aggregates for 90 days. Such counts estimate sessions, not unique people. Infrastructure request data can still be processed when browsing as a guest. Country information is not precise-location tracking.
12Advertisements, sponsorships and external media
SAFFER includes advertising or sponsored placements. Sponsored material must be identified as such, and an ad is not an independent recommendation. Published promotions and first-party page/click measurements can be used to understand reach. We do not sell personal information or use private message contents, voice audio, identity documents or USB diagnostics to target advertisements. This notice does not authorize adding cross-site tracking or collecting an Advertising ID. Any later advertising technology that changes data collection requires an updated disclosure and the separate choices required by law and platform rules. Loading remote images or videos, or following an external link, sends network information to the hosting/destination provider.
13Support, reporting and staff operations
Support and safety processing includes your request text, attachments you choose, relevant account/content/room identifiers, timestamps, assigned staff, decisions and necessary evidence. Where Meta User Reporting is activated, Meta handles the reporting interface and may supply the report and user-submitted evidence to the developer through its configured inbox. This is separate from routine voice recording. Staff duty tools record shift times, presence estimates and confirmed administrative and personal account actions during a shift, including limited references/snapshots; the duty log does not copy private chat or call contents. Staff can read their own duty history and owner access is broader under role controls. We restrict evidence access to the assigned purpose, not unrestricted staff browsing.
14Service providers and recipients
Supabase supports authentication, database and uploaded-file storage. Cloudflare delivers the website and related security/network services. SAFFER’s configured LiveKit-based servers and relay infrastructure transport calls. Email providers deliver account/support correspondence; an email sent to our Gmail support address is processed by Google’s email service. Cloudflare Turnstile can process anti-abuse challenges where enabled. Authorized SAFFER staff process support and moderation data, and other users receive the content you choose to share with them. Meta, game stores and external media hosts also process data for their own services under their notices. We do not automatically copy ordinary private conversations to an AI provider as part of messaging or voice. A separately offered AI feature requires its own clear explanation of the provider, content sent and choice before use.
15Processing purposes and legal grounds
We use the relevant data to provide requested accounts, content and communications; administer your settings and entitlements; protect the service; measure its operation; respond to support, safety and rights requests; and meet binding obligations. Where EEA/UK data-protection rules apply, necessary account/feature delivery relies on performing the requested service/contract, security and proportionate operational administration rely on legitimate interests balanced against your rights, legally required handling relies on legal obligation, and optional processing requiring consent relies on your separate choice. Consent is not inferred from reading this page or accepting unrelated terms. You can withdraw an optional consent without affecting prior lawful processing. We do not describe an unneeded purpose as essential merely because it is useful to us.
16International processing and lawful disclosures
Data can be processed in Iraq and in the countries where hosting, communications and support providers operate; not all data is stored in Iraq or in one region. Where transfer rules apply, appropriate legal safeguards must support the relevant transfer, and you may ask us about them. We may disclose limited necessary data to comply with a binding lawful request or protect users from serious harm, subject to applicable law and Meta’s restrictions on platform/device data. A change of operator does not permit unrelated use; affected users must receive required notice and protections.
17Retention and deletion limits
We retain account/content records while needed to provide the requested feature, and remove or de-identify data when it is no longer needed. Requests, disputes, security evidence and legally required records may require a limited additional period tied to their purpose, not indefinite retention by default. Configured cleanup periods above describe the relevant tables, not every provider log. Local preferences and USB history remain until changed or cleared. Voice-test clips are temporary memory data. Backups, where operated, have separate rotation/recovery handling; deletion requests are also applied to restored data before normal reuse. We do not promise instant erasure from backups or recipients’ devices. We will explain any justified retention relevant to your request and delete data without undue delay as required by law and platform obligations.
18Your choices and rights
All users can request access, correction or deletion through Support, regardless of country and without a fee for submitting a deletion request. Use available profile/privacy controls, block and mute controls, personalization resets and notification settings. Where applicable, you may also request a portable copy, restrict processing, object to processing based on legitimate interests, withdraw consent, use an authorized representative, or complain to your local data-protection authority. Some rights have lawful exceptions; we explain a refusal and available review route. Discovery ranking orders recommendations using the available signals; it does not grant or remove your legal rights. Contact us for human review of an account restriction.
19A deletion route without signing in
Email [email protected] with the subject “SAFFER data deletion request”. State your username or account email, whether you want the shared account or specific data deleted, and a contact address for the reply. Do not send passwords, authenticator codes or identity-document images. We may proportionately verify ownership, explain consequences, and confirm the request outcome within applicable time limits. You can instead use Settings → Privacy → data requests where available. Creating a request is not instant erasure. Uninstalling SAFFER, deleting browser storage or closing a support ticket does not delete the shared server account. Deleting it can affect both website and Quest access; external-store purchases follow that store’s process.
20Young users and safety reports
We do not intend to provide SAFFER accounts to children under 13. A higher age or guardian involvement can be required by applicable law or the selected service. If you believe we hold a child’s information improperly, contact Support so we can restrict the account, investigate and take appropriate deletion or protective action. Parents/guardians may contact us about a child’s data. Do not send child-abuse material or unnecessary identity documents as evidence. A minimum-age statement does not replace safeguards for teens or any legal duty triggered by actual knowledge.
21Security and incident handling
We use access controls, authenticated sessions and protected service connections to limit unauthorized use. No online service or backup can be guaranteed secure or continuously available. Report suspected compromise or a vulnerability privately to Support; do not access other people’s data to demonstrate it. Where an incident creates notification duties, SAFFER will provide the legally and contractually required notices. Neither a staff badge nor a premium plan gives permission to inspect another user’s private data.
22Publication, versions and acknowledgement
This dated shared notice is published for both website and Quest use. Material changes are identified with a new version and additional notice or consent where required. We retain historical policy text and do not relabel an old acknowledgement as acceptance of new wording. Reading or scrolling this page creates no acceptance record and grants no optional device, tracking or marketing permission. Earlier app builds may display an earlier version until their policy publication is updated; the published notice does not silently modify their code. Contact Support about any discrepancy.
Game visit counter update
Website 2.8.7 update — 22 October 2026: game-page visits are counted automatically without a confirmation button. This is separate from optional general-page and store/download-click measurement, which remains controlled by your website measurement choice. A separate random catalog session token supports the three-second cooldown after leaving a counted game visit; staying on a page does not add repeated visits. The server keeps private hashed cooldown state and aggregated public totals; visitor identities are not listed in the dashboard. Existing event retention and account security rules continue to apply.