Nova Privacy Policy

1. Use Nova responsibly

Do not use Nova to harm other people, disrupt the service, evade a lawful restriction, distribute malware, or access accounts and systems without permission.

2. Accounts and Social

Keep your credentials private. You are responsible for activity from your account. Nova may restrict accounts or devices used for abuse, harassment, spam, or attempts to compromise the service.

3. Content

Only share content you have the right to share. Public and reported content may be reviewed for moderation and security.

4. Service changes

Nova may update, limit, or discontinue features to protect users, meet technical requirements, or improve the service.

5. No guarantee

Nova is provided as available. Availability, compatibility, and uninterrupted proxy access cannot be guaranteed.

6. Data you provide

Nova stores account details, profile fields, settings, friendships, groups, messages, reports, and other information you choose to submit.

When you use Nova Social or staff workflows, this can also include voice-room membership and signaling metadata, room chat, support activity, game/social state, staff Tasks and Requests, task assignment and resolution data, moderation reasons, and related account or resource identifiers.

7. Account and authentication data

Nova stores the information needed to operate an account, such as username, account/profile information, roles or plan status, and account status. Passwords are not stored as readable passwords; Nova stores derived password hashes and salts. Authentication sessions may be associated with a hashed device identifier and can remain valid for up to 30 days unless revoked earlier.

8. Browser security records

Nova logs sanitized destination URLs and one-way hashes of random device identifiers. Sensitive URL fields, credentials, and URL fragments are removed before storage.

When Nova records proxy-navigation diagnostics, the record can include the signed-in account when available, a hashed device identifier, a cleaned URL/domain, result, reason, incident identifier, and time.

9. Retention

Standard navigation logs expire after 14 days, security incident records after 90 days, and administrative audit records after one year.

Voice-room event and staff-entry records are configured to expire after 90 days. Chat moderation event records are configured to expire after 30 days unless the underlying feature stores a separate record for a different purpose. Staff Task and Request records currently do not have an automatic expiration period.

10. How data is used

Data operates account, Social, personalization, moderation, security, device bans, and service reliability features. Nova does not sell personal information.

Data is also used to operate staff Tasks and Requests, enforce role-based permissions, investigate reports, troubleshoot voice or proxy issues, and create accountability records for high-impact staff actions.

11. Your choices

Guests can browse without an account. Settings can be kept on-device, profile fields can be edited, recent local activity can be cleared, and signed-in users can sign out at any time.

Clearing local browser data does not remove server-side records that Nova needs for account security, moderation, staff accountability, abuse prevention, or operation of features.

12. Voice rooms and live audio

Nova stores voice-room metadata needed to run rooms, such as room membership, admission state, host/moderation state, signaling, room chat, and room events. Microphone audio is transported between participants for live communication; Nova's room system uses signaling information to establish those connections.

13. Developer and Owner voice access

Developers and Owners have elevated voice-room access for administration, moderation, troubleshooting, and support. They can bypass normal admission, room locks, private-room restrictions, and capacity limits.

Developers and Owners can also use Vanish mode. In Vanish mode, that staff member is hidden from the normal visible room member list and visible participant count for regular users and Admins. Vanish does not make the staff member anonymous to Nova: the backend records the staff account's room presence and a staff voice event for accountability. Other Developers and the Owner may be able to see staff presence that ordinary users and Admins cannot see.

14. Staff Tasks and Requests

Nova Control includes a staff workflow system. Admins can create requests for Developers or the Owner, and Developers/Owner can create or assign tasks. Task records can include the creator, assignee or assigned role, title, description, task type, priority, status, due date, affected username or resource, requested action, resolution, completion time, and completing staff member.

Creating a Task or Request does not itself bypass permissions. The staff member completing an action must still have the server-side authority required for it. Do not place passwords or other unnecessary secrets in task descriptions or resolution notes.

15. Password resets and account actions

Authorized Developers or the Owner can perform account actions that are above an Admin's authority, including password resets for accounts below their staff level. Nova replaces the stored password hash and salt; it does not need to reveal the old password. Password-reset and other high-impact staff actions can create audit information so the action can be traced to the staff account that performed it.

16. Moderation, reports, and device controls

Nova may store reports, support tickets, chat restrictions, voice restrictions, device bans, moderation events, reasons supplied by staff, and related account identifiers. Nova may use hashed or pseudonymous device identifiers to enforce sessions, rate limits, abuse prevention, and device bans.

17. Role-based staff access

Nova's current staff hierarchy is User → Admin → Developer → Owner. Admins focus on moderation and can request higher-authority actions. Developers have Admin abilities plus elevated system/staff powers. The Owner has the highest authority. Staff access is controlled by role on the server; hiding a control in the interface is not treated as the security boundary.

18. Administrative audit records

Administrative actions can create audit records containing the acting staff account, action, target type or identifier, reason, metadata, and time. Access to these records is restricted by Nova's staff-role hierarchy.

19. Changes to this policy

Nova may update this policy when features, retention periods, staff powers, technical requirements, or legal obligations change. The effective date and policy version at the top identify the currently shipped policy text.