Privacy and data controls

Each customer organization has a separate tenant boundary for memberships, records, assets, missions, connections, and employee access. Cross-organization access is denied by server-side authorization.

Browser microphone access is controlled by your device. Royal Awake listens only while the supported RoyalOS session is open and enabled. Raw audio is not intentionally stored by the wake interface; the recognized command becomes conversation text.

Only add information you want the organization’s authorized employees to use. Knowledge, memories, and uploaded assets should remain scoped to the correct workspace. Account administrators should review and remove outdated records.

RoyalOS support access should require customer consent or an approved, time-limited support session. Active support access must remain visible and every action must be audited.

Use your organization records and account tools to export company data. Contact support for account-level deletion, legal retention questions, or a complete data request.