Terms of Service — Sentinel

Draft — private alpha / pre-launch
Effective date: [EFFECTIVE DATE]

These Terms of Service (“Terms”) govern access to and use of Sentinel, a Discord-based staff, moderation and ER:LC management service.

Sentinel is currently operated under the Sentinel project name.

Certain formal operator and contact details will be completed before Sentinel enters public or commercial operation.

Operator: [OPERATOR DETAILS — TO BE COMPLETED BEFORE PUBLIC/COMMERCIAL LAUNCH]
Contact: [SUPPORT OR LEGAL CONTACT EMAIL]

By installing, authorising, accessing or using Sentinel, you agree to these Terms where they apply to you.

1. About Sentinel

Sentinel is designed for Discord communities using Roblox Emergency Response: Liberty County (“ER:LC”).

Depending on the features enabled by a community, Sentinel may provide tools including:

staff shift management;
active shift and shift history features;
leave-of-absence and reduced-activity management;
moderation and punishment records;
Discord-to-Roblox identity verification;
ER:LC server integration;
ER:LC roster and player information;
observed playtime tracking;
playtime rewards;
staff and administrative tools;
guild configuration and permissions;
operational logging and audit records.

Sentinel may add, change, restrict, replace or remove features as the service develops.

Some functionality may be experimental or limited during development, alpha or beta periods.

2. Installing Sentinel

A person who installs or authorises Sentinel in a Discord server confirms that:

they have authority to install or authorise applications for that server;
they are permitted to configure Sentinel and grant the permissions required for the features they enable; and
they accept these Terms in connection with installing and administering Sentinel.

Installing Sentinel does not mean that the installer accepts these Terms on behalf of every member of the Discord server.

Individual users may separately become subject to these Terms when they directly access or use Sentinel.

3. Community Responsibility

Sentinel provides administrative tools. Sentinel does not operate or control the Discord communities that use it.

Server owners and authorised administrators are responsible for:

deciding which Sentinel features to enable;
assigning appropriate roles and permissions;
deciding which staff members may access administrative features;
configuring channels, logs, rewards and other settings;
ensuring their use of Sentinel is appropriate for their community;
reviewing actions performed by their own staff; and
correcting community records where necessary.

Sentinel may provide technical permission controls, but communities remain responsible for their own configuration decisions.

4. Moderation and Punishment Decisions

Sentinel may assist communities with creating, displaying or storing moderation and punishment records.

Sentinel does not independently decide whether a user should be warned, suspended, banned or otherwise punished.

Those decisions are made by the relevant Discord community and its authorised staff.

Sentinel is therefore not responsible for the substance, fairness or accuracy of a community’s moderation decision merely because Sentinel was used to record or process part of that decision.

5. Roblox Account Verification

Sentinel may allow users to link their Discord identity with a Roblox account.

Where available, Sentinel uses official Roblox authentication together with Sentinel’s own Discord identity verification and security checks.

Users must not:

attempt to link an account they do not control;
impersonate another user;
interfere with the verification process;
manipulate authentication responses;
attempt to bypass verification protections; or
cause another person’s Discord identity to become linked to the wrong Roblox account.

Sentinel may reject or expire a verification attempt where security checks are not satisfied.

6. ER:LC Integration and Credentials

Certain features may require an authorised community administrator to connect Sentinel to an ER:LC server.

Supported ER:LC credentials are designed to be:

encrypted while stored;
excluded from ordinary Discord output;
excluded from intentional application logging; and
accessible only where required to perform authorised ER:LC operations.

Community administrators are responsible for:

using credentials they are authorised to use;
protecting those credentials outside Sentinel;
replacing credentials if compromise is suspected; and
complying with relevant third-party rules and API requirements.

When Sentinel is removed from a Discord guild, its current architecture disables active tracking, clears active observations and removes the guild’s stored encrypted ER:LC connection.

Historical records may be retained separately as described in the Privacy Policy.

7. Playtime Tracking

Sentinel may provide observed ER:LC playtime tracking.

Playtime tracking is disabled by default.

An authorised server administrator must enable it before Sentinel begins tracking observed playtime for that community.

Observed playtime is based on information available to Sentinel and may not represent a perfect or complete record of the time a person spent in an ER:LC server.

Communities should not treat observed playtime as an infallible attendance record where exact timing is required.

8. Acceptable Use

You must not use Sentinel to:

violate applicable law;
gain unauthorised access to accounts, systems, servers, credentials or data;
bypass Sentinel permissions, authentication, verification or security controls;
access or infer information belonging to another community without authorisation;
deliberately exploit vulnerabilities;
intentionally interfere with Sentinel’s availability or operation;
submit malicious requests or intentionally overload the service;
impersonate another person;
provide credentials you are not authorised to use;
facilitate fraud, harassment or unlawful activity; or
expose private security information belonging to Sentinel or its users.

Good-faith security reports should be sent privately to:

[SECURITY CONTACT / REPORTING METHOD]

9. Multi-Community Isolation

Sentinel is designed as a multi-tenant service where data and configuration are associated with individual Discord guilds.

Users must not attempt to access or modify information belonging to another community unless they are legitimately authorised to do so.

Sentinel may restrict access to affected features where necessary to investigate or resolve security issues.

10. Suspension and Restriction

Sentinel may suspend or restrict access where reasonably necessary to:

protect the service or its users;
investigate suspected abuse;
prevent unauthorised access;
respond to a violation of these Terms;
maintain stability;
comply with legal obligations; or
protect third-party systems.

Serious security abuse may result in immediate restriction.

11. Third-Party Services

Sentinel depends on third-party services including Discord, Roblox and ER:LC-related systems.

Sentinel does not control those services.

Changes, outages, rate limits, authentication failures, API changes or discontinued functionality may cause Sentinel features to become unavailable, delayed or inaccurate.

Use of those services remains subject to their own terms and policies.

Sentinel is an independent service and is not endorsed by or affiliated with Discord, Roblox, ER:LC or their respective operators unless explicitly stated otherwise.

12. Availability

Sentinel is provided on an evolving basis.

Continuous or uninterrupted availability is not guaranteed.

Temporary or permanent interruptions may result from:

maintenance;
software defects;
infrastructure problems;
third-party outages;
security incidents;
API changes; or
development changes.

Users should not rely on Sentinel as the sole copy of information they are independently required to retain.

13. Changes to Sentinel

Sentinel may modify or remove features for reasons including:

product development;
reliability;
security;
third-party API changes;
legal requirements;
abuse prevention; and
operational constraints.

Where a change materially affects personal information handling, the Privacy Policy will be updated where appropriate.

14. Sentinel Plus

Sentinel may offer paid functionality under names such as Sentinel Plus in the future.

No payment, subscription, cancellation, renewal or refund terms are created by this section alone.

Commercial terms will be introduced before paid services become available.

15. Intellectual Property

Original Sentinel software, branding, website design, documentation and other original materials are protected by applicable intellectual-property rights.

These Terms do not transfer ownership of Sentinel or its intellectual property to users or communities.

Third-party names, trademarks and materials remain the property of their respective owners.

16. Privacy

Sentinel processes personal information as described in the Sentinel Privacy Policy.

That policy explains:

what information Sentinel may process;
why it is processed;
how account verification works;
how playtime tracking works;
how ER:LC credentials are handled; and
how information may be retained.

17. Security

Sentinel uses technical and organisational safeguards intended to protect the service and the information it processes.

No online service can guarantee absolute security.

Users and administrators are responsible for protecting their own:

Discord accounts;
Roblox accounts;
ER:LC credentials;
devices; and
authentication information.

Suspected security issues should be reported privately to:

[SECURITY CONTACT / REPORTING METHOD]

18. Disclaimers

To the extent permitted by applicable law, Sentinel is provided on an “as available” basis.

Sentinel does not guarantee that:

every feature will always be available;
third-party information will always be complete or current;
observed playtime will always be exact;
every community configuration will be suitable;
Sentinel will identify every misuse or administrative mistake; or
every third-party integration will continue operating indefinitely.

Nothing in these Terms excludes rights or responsibilities that cannot legally be excluded.

19. Limitation of Liability

To the extent permitted by applicable law, the Sentinel operator will not be responsible for indirect or consequential losses arising solely from:

Sentinel becoming unavailable;
third-party service failures;
inaccurate third-party data; or
decisions independently made by a Discord community or its staff.

Nothing in these Terms limits or excludes liability where doing so would be prohibited by law.

This section may be updated when Sentinel’s final legal operator and commercial arrangements are established.

20. Changes to These Terms

These Terms may be updated as Sentinel develops.

Material changes may be communicated through:

the Sentinel website;
the Sentinel Discord service;
the support Discord; or
another reasonable method.

The effective date shown at the top identifies the current published version.

21. Ending Use of Sentinel

A community may stop using Sentinel by removing it from its Discord server.

Where available, administrators may also disconnect associated integrations.

Removing Sentinel does not necessarily cause the immediate deletion of every historical record.

Data handling following removal is described in the Privacy Policy.

22. Governing Law and Operator Details

The governing law, jurisdiction and formal operator arrangement will be completed before public or commercial launch.

[GOVERNING LAW / JURISDICTION — TO BE COMPLETED BEFORE PUBLIC/COMMERCIAL LAUNCH]

Sentinel will not represent itself as an incorporated company unless such an entity actually exists.

23. Contact

Questions about these Terms may be sent to:

Sentinel
[OPERATOR DETAILS — TO BE COMPLETED BEFORE PUBLIC/COMMERCIAL LAUNCH]
[CONTACT EMAIL]