Privacybeleid

Effective augustus 26, 2026. This policy explains what WatchTower records, why it is needed, and the choices available to customers and visitors.

Account and Owner Data

WatchTower uses account, linked-avatar, location, machine, subscription, Linden-dollar payment, delivery, staff-role, configuration, and support records to provide private dashboards, verify access, operate purchased features, prevent abuse, and help resolve problems. Passwords, setup keys, machine tokens, and Discord webhooks must never be posted publicly or included in screenshots.

Visitor and Terminal Records

On land an owner manages or is authorized to monitor, an authenticated terminal may record information Second Life makes available to nearby scripted objects: avatar UUID, username, display name, active group tag, account age, payment-information status (never payment details), shared viewer language, position, account level, body-shape setting, script counts, allocated script memory, script time, render weight, animated attachment count, available attachment slots, location, machine, and timestamp. Optional security tools may also store access-list entries, alerts, actions, and incident notes. Optional chat-relay features may process nearby chat that the configured in-world object can hear. WatchTower does not bypass Second Life permissions or collect private messages from outside the configured feature.

Owner Notice and Lawful Use

Customers must use WatchTower only where they have authority and must provide any visitor notice or consent required by applicable law, venue rules, or Second Life policy. WatchTower data must not be used to stalk, harass, discriminate, impersonate, or monitor a place without authorization.

Visibility and Sharing

Customer dashboards and operational records are private to authorized account users and staff. Data may be processed by hosting, email, security, monitoring, or Discord services needed for enabled features, disclosed when legally required, or reviewed to protect users and the service. FlaroCity does not sell personal information or use WatchTower records for third-party advertising.

Retention

Compact arrival and visitor history is retained according to the purchased plan, from 90 days through a maximum of five years. Raw snapshots, health telemetry, security logs, and temporary request data use shorter operational limits. Purchase, entitlement, delivery, refund, fraud-prevention, and support records may be kept longer when reasonably needed for redelivery, accounting, disputes, security, or legal compliance. Backups expire through normal rotation.

Your Choices

Customers can review linked locations and machines, disable optional integrations, limit staff access, and request correction, export, or deletion through private support. Visitors may contact FlaroCity about WatchTower-held information using their avatar UUID and the approximate location and time. Some payment, security, incident, or legal records may need to be retained or de-identified.

Security, Age, and Changes

WatchTower uses access controls, scoped credentials, encrypted transport, and audit records, but no service can promise absolute security. Users must meet Second Life age and account requirements; WatchTower is not directed to children under 13. Material policy changes will be posted here with a new effective date.

Support and Privacy Requests

Customers can open a private support ticket after signing in. Include useful setup details, avatar UUID, location, and approximate time, but never send a password, setup key, token, or private webhook.