1. Scope
This policy applies to VivaRec and the VivaRec-operated services that link to this page (collectively, the “Services”). It describes how information may be handled when you sign in, connect a supported platform, or use online features.
Meta and Steam are separate services operated by their respective companies. Unless explicitly stated otherwise, VivaRec is not owned, operated, or endorsed by Meta or Valve. Their own privacy policies also apply when you use their platforms.
2. Meta Quest/Oculus IDs and Steam IDs
Depending on the version and features you use, VivaRec may receive or process a platform identifier so the service can recognize the same account across sessions.
Meta Quest / Oculus
If a supported Meta Quest build or Meta sign-in flow provides an account or application-scoped user identifier, VivaRec may use that identifier to associate requests with a VivaRec account and to support account-related features. The exact identifier available depends on the integration and Meta's platform rules.
Steam
If you use a Steam version or Steam authentication, VivaRec may process your SteamID to identify your Steam account, associate it with service data, and support compatible features.
These identifiers are not passwords. Do not send us your password, authentication codes, access tokens, or other secret credentials through support messages. If the service uses authentication tokens internally, they should be handled separately and protected as secrets.
3. How we use identifiers and other information
Where applicable, information may be used to:
- recognize your account and authenticate requests;
- link your platform account to VivaRec account or player records;
- provide multiplayer, matchmaking, room, progression, or other requested service features;
- maintain service integrity, prevent abuse, investigate errors, and enforce service rules;
- debug crashes, diagnose compatibility issues, and maintain or improve the Services; and
- respond to support requests and comply with applicable legal obligations.
We do not claim to use platform IDs for advertising or to sell them. If that practice ever changes, this policy should be updated before the change takes effect where required.
4. Other data that may be processed
Depending on the features you use and how the service is configured, VivaRec may also process:
- basic account or player data associated with your identifier;
- game version, platform, connection status, and gameplay/service requests needed to operate features;
- technical logs such as timestamps, error details, and security events; and
- information you choose to include in a support request.
Only list data categories that your implementation actually collects. If you do not collect an item above, remove it. If you collect IP addresses, voice data, analytics, or payment data, describe that accurately here.
6. Storage and security
VivaRec should use reasonable technical and organizational safeguards to protect stored information from unauthorized access, loss, misuse, or alteration. Access should be limited to people and systems that need it to operate or maintain the Services.
No internet service or storage method can be guaranteed completely secure. Do not publish database files, server logs, signing keys, API secrets, authentication tokens, or private configuration files in public repositories or support channels.
Add the actual hosting region, database/storage arrangements, and security practices here if you want to make more specific promises.
7. Data retention
Information should be kept only for as long as reasonably necessary to provide the Services, maintain security, resolve disputes, or meet applicable legal obligations. Retention periods can vary by data type and by operational or legal requirements.
This template does not set a specific deletion schedule. Add your actual retention periods and explain how account or identifier deletion requests are handled before publishing.
8. Your choices and privacy requests
You can stop using VivaRec at any time. You may also contact us to ask what information associated with your platform identifier is held, or to request correction or deletion, subject to applicable law, technical limitations, and records that must be retained.
To help us locate a record, you may be asked to provide the relevant platform and public account identifier. Never send a password, access token, or other secret credential. We may need to verify a request before acting on it.
Depending on where you live, you may have additional privacy rights under local law.
9. Children's privacy
VivaRec is not intended to collect personal information from children in a way that violates applicable privacy laws. If you believe a child has provided personal information improperly, contact us using the details below so the matter can be reviewed.
Set an appropriate minimum-age policy and any required parental-consent process for your actual audience and jurisdictions before publishing this page.
10. Changes to this policy
This policy may be updated as VivaRec's features, platform integrations, or legal requirements change. The effective date at the top indicates when this version was last put into effect. Material changes should be communicated through an appropriate channel where required.
11. Contact
For privacy questions or data requests, contact the VivaRec team:
Email: REPLACE-WITH-YOUR-PRIVACY-EMAIL@example.com
Replace the placeholder above with an email address you control before making this page public.