feat: add prelaunch site controls and refresh branding
This commit is contained in:
JB
+246
-12
@@ -1,13 +1,19 @@
|
||||
<svelte:head>
|
||||
<title>Terms & Privacy — SHD.build</title>
|
||||
<meta name="description" content="Terms of service, privacy practices, and fan-site disclaimer for SHD.build."/>
|
||||
<title>Terms & Privacy | SHD.build</title>
|
||||
<meta
|
||||
name="description"
|
||||
content="Terms of service, privacy practices, and fan-site disclaimer for SHD.build."
|
||||
/>
|
||||
</svelte:head>
|
||||
|
||||
<main class="legal-page">
|
||||
<header class="legal-hero">
|
||||
<p class="eyebrow"><span></span> SHD NETWORK POLICY</p>
|
||||
<h1>TERMS & <em>PRIVACY.</em></h1>
|
||||
<p>Effective July 25, 2026. These terms describe the rules for using SHD.build and the information processed to operate and secure the service.</p>
|
||||
<p>
|
||||
Effective July 25, 2026. These terms set the rules for using SHD.build and explain what
|
||||
information we process to operate and secure the service.
|
||||
</p>
|
||||
</header>
|
||||
|
||||
<div class="legal-layout">
|
||||
@@ -19,15 +25,243 @@
|
||||
<a href="#disclaimers">09 · DISCLAIMERS</a>
|
||||
</nav>
|
||||
<article class="legal-document">
|
||||
<section id="service"><span>01</span><div><h2>THE SERVICE</h2><p>SHD.build is an independent community service for The Division Resurgence, including loadouts, guides, community-maintained game data, news, and discussion. By accessing or using it, you agree to these terms. If you do not agree, do not use the service. Features may change, be suspended, or be discontinued as development continues.</p></div></section>
|
||||
<section id="accounts"><span>02</span><div><h2>ACCOUNTS & SECURITY</h2><p>You are responsible for activity performed through your account and for maintaining control of your authentication methods. You must provide accurate information, may not impersonate another person, and may not attempt to access another account. We may restrict accounts to protect users, enforce these terms, or comply with law.</p><p>Available authentication methods may include passkeys, verified email magic links, local username and password credentials, Discord, and other providers added later. Third-party authentication remains subject to that provider’s terms and privacy practices.</p></div></section>
|
||||
<section id="content"><span>03</span><div><h2>USER CONTENT</h2><p>You retain ownership of original content you submit. You grant SHD.build a non-exclusive, worldwide, royalty-free license to host, reproduce, format, display, and distribute that content as necessary to operate the service. You represent that you have the rights required to post it.</p><p>Builds, guides, and comments may remain available after account deletion under a “Deleted Agent” attribution so community references are not broken. You may not upload unlawful, infringing, malicious, or privacy-invasive content.</p></div></section>
|
||||
<section id="conduct"><span>04</span><div><h2>COMMUNITY CONDUCT</h2><p>Do not harass others; publish illegal or infringing material; distribute malware; evade access restrictions; scrape or overload the service; manipulate ratings; spam; or exploit security vulnerabilities. Community Oversight may remove content, restrict access, or preserve relevant records when reasonably necessary for safety, support, abuse prevention, or legal obligations.</p></div></section>
|
||||
<section id="privacy"><span>05</span><div><h2>INFORMATION WE PROCESS</h2><p>Account data may include internal account identifiers, private login username, public display name, password hash, verified email, linked-provider identifiers and profile details, passkey public credentials, avatar, roles, permissions, builds, guides, favorites, ratings, comments, notification messages, read state, and delivery preferences. Passwords are stored only as salted Argon2id hashes. Private passkey material remains on your authenticator.</p><p>For login security and support, events may include the time, success status, authentication provider, IP address, user-agent string, normalized browser, operating system and device type, approximate country/region/city when supplied by the hosting proxy, failure reason, automated risk flags, provider or passkey credential reference, associated session identifier, and session end time or reason. We do not sell this information. It is used for authentication, abuse prevention, troubleshooting, moderation, and account support.</p><p>Contact submissions include the sender’s name, reply email, destination, subject, message, account identifier when signed in, and submission time. Copyright requests may additionally include claimant contact details, identified works and URLs, attestations, and electronic signature. These records are shared only with authorized recipients and retained as reasonably necessary to respond, document action, resolve disputes, enforce policy, and meet legal obligations.</p><p>Browser and email notification delivery is optional except that operational ISAC notices remain available in the in-app inbox. Email frequency is configurable by notification category and defaults to off. OAuth and email providers process information under their own policies.</p></div></section>
|
||||
<section id="cookies"><span>06</span><div><h2>ESSENTIAL COOKIES</h2><p>SHD.build currently uses only first-party cookies that are strictly necessary to provide authentication and protect sign-in flows. We do not currently use analytics, advertising, behavioral-tracking, or personalization cookies. These essential cookies cannot be disabled through a preference control. You may prevent cookies through your browser, but account sign-in will not function correctly.</p><div class="legal-table-wrap"><table class="legal-table"><thead><tr><th>COOKIE</th><th>PURPOSE</th><th>DURATION</th><th>PROTECTION</th></tr></thead><tbody><tr><td><code>shd_session</code></td><td>Keeps you securely signed in and associates requests with your server-side session.</td><td>Up to 30 days, or until sign-out or session invalidation.</td><td>HTTP-only, SameSite=Lax, Secure in production.</td></tr><tr><td><code>shd_discord_oauth_state</code></td><td>Validates a Discord sign-in or linking response and helps prevent request forgery.</td><td>Up to 10 minutes; removed when the callback is processed.</td><td>HTTP-only, SameSite=Lax, Secure in production; limited to the Discord authentication path.</td></tr></tbody></table></div><p>The informational notice remembers its dismissal in browser local storage under <code>shd-essential-cookie-notice</code>. It is not sent with web requests and can be removed through your browser’s site-data controls. OAuth state remains in a short-lived HTTP-only cookie because it must be securely validated by the server and unavailable to browser scripts.</p><p>If non-essential technologies are introduced later, this policy and the site’s consent controls will be updated before those technologies are enabled where consent is required.</p></div></section>
|
||||
<section id="retention"><span>07</span><div><h2>RETENTION & DELETION</h2><p>IP addresses, user-agent strings, normalized device information, and credential references in login history are retained for no more than 30 days, then automatically removed from the event. Non-sensitive facts such as event time, provider, outcome, failure category, and whether a session was created may remain for security and support history.</p><p>Deleting your account removes active sessions, credentials, verified email, provider profiles, passkeys, permissions, and uploaded avatar. You may also select immediate purging of retained login-event history during self-deletion. Public contributions may remain attributed to “Deleted Agent.” Backups and records required for fraud prevention, dispute resolution, or law may persist for a limited period where applicable.</p></div></section>
|
||||
<section id="third-parties"><span>08</span><div><h2>THIRD-PARTY SERVICES</h2><p>SHD.build may connect to Discord, email delivery services, and future identity providers. Their services are governed by their own terms. Links to other sites do not imply endorsement. You authorize the minimum provider data requested when choosing a linked sign-in method.</p></div></section>
|
||||
<section id="disclaimers"><span>09</span><div><h2>FAN-SITE & LEGAL DISCLAIMER</h2><p>SHD.build is an unofficial fan-created service and is not affiliated with, endorsed by, sponsored by, or approved by Ubisoft Entertainment or its affiliates.</p><p>Tom Clancy’s The Division, Tom Clancy’s The Division Resurgence, Ubisoft, and related names, trademarks, logos, characters, artwork, game data, and other intellectual property are owned by Ubisoft and/or its licensors. Their use is for identification, commentary, and community reference. No ownership is claimed.</p><p>The service and community information are provided “as is” and “as available,” without warranties of accuracy, availability, fitness for a particular purpose, or non-infringement to the extent permitted by law. Build data may become outdated after game updates. SHD.build is not responsible for third-party services or decisions made using community content.</p><p>Copyright owners and authorized agents may use our <a href="/dmca">DMCA & Copyright Policy</a> and <a href="/contact?team=dmca">copyright request form</a>. Other questions may be sent through <a href="/contact">Contact Us</a>.</p><p>These terms may be updated as the service changes. Material revisions will be identified by a new effective date. Nothing here limits rights that cannot legally be waived.</p><p>For authoritative information about Ubisoft intellectual property, consult Ubisoft’s official <a href="https://www.ubisoft.com/legal/documents/termsofuse/en-US" rel="external">Terms of Use</a> and the official <a href="https://www.ubisoft.com/game/the-division/resurgence" rel="external">The Division Resurgence site</a>.</p></div></section>
|
||||
<section id="service">
|
||||
<span>01</span>
|
||||
<div>
|
||||
<h2>THE SERVICE</h2>
|
||||
<p>
|
||||
SHD.build is an independent community service for The Division Resurgence. It
|
||||
includes loadouts, guides, community-maintained game data, news, and discussion.
|
||||
By accessing or using SHD.build, you agree to these terms. If you do not agree, do
|
||||
not use the service. We may change, suspend, or discontinue features as development
|
||||
continues.
|
||||
</p>
|
||||
</div>
|
||||
</section>
|
||||
<section id="accounts">
|
||||
<span>02</span>
|
||||
<div>
|
||||
<h2>ACCOUNTS & SECURITY</h2>
|
||||
<p>
|
||||
You are responsible for activity through your account and for keeping control of
|
||||
your authentication methods. You must provide accurate information. You may not
|
||||
impersonate another person or attempt to access another account. We may restrict
|
||||
accounts to protect users, enforce these terms, or comply with law.
|
||||
</p>
|
||||
<p>
|
||||
SHD.build may offer passkeys, verified email magic links, local username and
|
||||
password credentials, Discord, and other authentication providers added later.
|
||||
Each third-party provider applies its own terms and privacy practices.
|
||||
</p>
|
||||
</div>
|
||||
</section>
|
||||
<section id="content">
|
||||
<span>03</span>
|
||||
<div>
|
||||
<h2>USER CONTENT</h2>
|
||||
<p>
|
||||
You retain ownership of original content you submit. You grant SHD.build a
|
||||
non-exclusive, worldwide, royalty-free license to host, reproduce, format, display,
|
||||
and distribute that content as necessary to operate the service. You represent that
|
||||
you have the rights required to post it.
|
||||
</p>
|
||||
<p>
|
||||
SHD.build may keep builds, guides, and comments available after account deletion
|
||||
under a “Deleted Agent” attribution to preserve community references. You may not
|
||||
upload unlawful, infringing, malicious, or privacy-invasive content.
|
||||
</p>
|
||||
</div>
|
||||
</section>
|
||||
<section id="conduct">
|
||||
<span>04</span>
|
||||
<div>
|
||||
<h2>COMMUNITY CONDUCT</h2>
|
||||
<p>
|
||||
Do not harass others; publish illegal or infringing material; distribute malware;
|
||||
evade access restrictions; scrape or overload the service; manipulate ratings; spam;
|
||||
or exploit security vulnerabilities. Community Oversight may remove content,
|
||||
restrict access, or preserve relevant records when reasonably necessary for safety,
|
||||
support, abuse prevention, or legal obligations.
|
||||
</p>
|
||||
</div>
|
||||
</section>
|
||||
<section id="privacy">
|
||||
<span>05</span>
|
||||
<div>
|
||||
<h2>INFORMATION WE PROCESS</h2>
|
||||
<p>
|
||||
We may process internal account identifiers, private login username, public display
|
||||
name, password hash, verified email, linked-provider identifiers and profile
|
||||
details, passkey public credentials, avatar, roles, permissions, builds, guides,
|
||||
favorites, ratings, comments, notification messages, read state, and delivery
|
||||
preferences. SHD.build stores passwords only as salted Argon2id hashes. Private
|
||||
passkey material remains on your authenticator.
|
||||
</p>
|
||||
<p>
|
||||
For login security and support, we may record the time, success status,
|
||||
authentication provider, IP address, user-agent string, normalized browser,
|
||||
operating system and device type, approximate country, region, and city when the
|
||||
hosting proxy supplies them, failure reason, automated risk flags, provider or
|
||||
passkey credential reference, associated session identifier, and session end time
|
||||
or reason. We do not sell this information. We use it for authentication, abuse
|
||||
prevention, troubleshooting, moderation, and account support.
|
||||
</p>
|
||||
<p>
|
||||
When you contact us, we collect the sender’s name, reply email, destination,
|
||||
subject, message, account identifier when signed in, and submission time. Copyright
|
||||
requests may also include claimant contact details, identified works and URLs,
|
||||
attestations, and electronic signature. We share these records only with authorized
|
||||
recipients and keep them as long as reasonably necessary to respond, document
|
||||
action, resolve disputes, enforce policy, and meet legal obligations.
|
||||
</p>
|
||||
<p>
|
||||
Browser and email notification delivery is optional. Operational ISAC notices
|
||||
remain available in the in-app inbox. You can configure email frequency by
|
||||
notification category, and email delivery defaults to off. OAuth and email
|
||||
providers process information under their own policies.
|
||||
</p>
|
||||
</div>
|
||||
</section>
|
||||
<section id="cookies">
|
||||
<span>06</span>
|
||||
<div>
|
||||
<h2>ESSENTIAL COOKIES</h2>
|
||||
<p>
|
||||
SHD.build currently uses only first-party cookies that are strictly necessary for
|
||||
authentication and sign-in protection. We do not currently use analytics,
|
||||
advertising, behavioral-tracking, or personalization cookies. Because these cookies
|
||||
are essential, SHD.build does not offer a preference control for disabling them.
|
||||
You may block cookies through your browser, but account sign-in will not function
|
||||
without them.
|
||||
</p>
|
||||
<div class="legal-table-wrap">
|
||||
<table class="legal-table">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>COOKIE</th>
|
||||
<th>PURPOSE</th>
|
||||
<th>DURATION</th>
|
||||
<th>PROTECTION</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>shd_session</code></td>
|
||||
<td>
|
||||
Maintains your sign-in and associates requests with your server-side
|
||||
session.
|
||||
</td>
|
||||
<td>Up to 30 days, or until sign-out or session invalidation.</td>
|
||||
<td>HTTP-only, SameSite=Lax, Secure in production.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>shd_discord_oauth_state</code></td>
|
||||
<td>
|
||||
Validates a Discord sign-in or linking response and helps prevent
|
||||
request forgery.
|
||||
</td>
|
||||
<td>Up to 10 minutes; SHD.build removes it after processing the callback.</td>
|
||||
<td>
|
||||
HTTP-only, SameSite=Lax, Secure in production; limited to the Discord
|
||||
authentication path.
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<p>
|
||||
Your browser stores dismissal of the informational notice in local storage under
|
||||
<code>shd-essential-cookie-notice</code>. Your browser does not send this value with
|
||||
web requests. You can remove it through your browser’s site-data controls. We keep
|
||||
OAuth state in a short-lived HTTP-only cookie so the server can validate it without
|
||||
exposing it to browser scripts.
|
||||
</p>
|
||||
<p>
|
||||
If we introduce non-essential technologies, we will update this policy and the
|
||||
site’s consent controls before enabling those technologies where consent is
|
||||
required.
|
||||
</p>
|
||||
</div>
|
||||
</section>
|
||||
<section id="retention">
|
||||
<span>07</span>
|
||||
<div>
|
||||
<h2>RETENTION & DELETION</h2>
|
||||
<p>
|
||||
We retain IP addresses, user-agent strings, normalized device information, and
|
||||
credential references in login history for no more than 30 days. After 30 days, we
|
||||
remove those fields from the event. We may retain non-sensitive facts such as event
|
||||
time, provider, outcome, failure category, and whether the event created a session
|
||||
for security and support history.
|
||||
</p>
|
||||
<p>
|
||||
When you delete your account, SHD.build removes active sessions, credentials,
|
||||
verified email, provider profiles, passkeys, permissions, and uploaded avatar. You
|
||||
may also select an immediate purge of retained login-event history during
|
||||
self-deletion. SHD.build may keep public contributions under a “Deleted Agent”
|
||||
attribution. SHD.build may retain backups and records for a limited period where
|
||||
applicable when fraud prevention, dispute resolution, or law requires them.
|
||||
</p>
|
||||
</div>
|
||||
</section>
|
||||
<section id="third-parties">
|
||||
<span>08</span>
|
||||
<div>
|
||||
<h2>THIRD-PARTY SERVICES</h2>
|
||||
<p>
|
||||
SHD.build may connect to Discord, email delivery services, and future identity
|
||||
providers. Each provider applies its own terms. Links to other sites do not imply
|
||||
endorsement. When you choose a linked sign-in method, you authorize SHD.build to
|
||||
request the minimum provider data needed for that method.
|
||||
</p>
|
||||
</div>
|
||||
</section>
|
||||
<section id="disclaimers">
|
||||
<span>09</span>
|
||||
<div>
|
||||
<h2>FAN-SITE & LEGAL DISCLAIMER</h2>
|
||||
<p>
|
||||
SHD.build is an unofficial fan-created service with no affiliation to Ubisoft
|
||||
Entertainment or its affiliates. Ubisoft does not endorse, sponsor, or approve
|
||||
SHD.build.
|
||||
</p>
|
||||
<p>
|
||||
Ubisoft and/or its licensors own Tom Clancy’s The Division, Tom Clancy’s The
|
||||
Division Resurgence, Ubisoft, and related names, trademarks, logos, characters,
|
||||
artwork, game data, and other intellectual property. SHD.build uses them for
|
||||
identification, commentary, and community reference and does not claim ownership.
|
||||
</p>
|
||||
<p>
|
||||
SHD.build provides the service and community information “as is” and “as
|
||||
available,” without warranties of accuracy, availability, fitness for a particular
|
||||
purpose, or non-infringement to the extent permitted by law. Game updates may make
|
||||
build data outdated. SHD.build is not responsible for third-party services or for
|
||||
decisions that users make based on community content.
|
||||
</p>
|
||||
<p>
|
||||
Copyright owners and authorized agents may use our
|
||||
<a href="/dmca">DMCA & Copyright Policy</a> and
|
||||
<a href="/contact?team=dmca">copyright request form</a>. Send other questions
|
||||
through <a href="/contact">Contact Us</a>.
|
||||
</p>
|
||||
<p>
|
||||
SHD.build may update these terms as the service changes. We will identify material
|
||||
revisions with a new effective date. Nothing here limits rights that cannot legally
|
||||
be waived.
|
||||
</p>
|
||||
<p>
|
||||
For authoritative information about Ubisoft intellectual property, consult
|
||||
Ubisoft’s official
|
||||
<a href="https://www.ubisoft.com/legal/documents/termsofuse/en-US" rel="external"
|
||||
>Terms of Use</a
|
||||
>
|
||||
and the official
|
||||
<a href="https://www.ubisoft.com/game/the-division/resurgence" rel="external"
|
||||
>The Division Resurgence site</a
|
||||
>.
|
||||
</p>
|
||||
</div>
|
||||
</section>
|
||||
</article>
|
||||
</div>
|
||||
</main>
|
||||
|
||||
Reference in New Issue
Block a user