SHD.build RESURGENCE DATA & TOOLS
NewsDatabaseBuildsGuidesBuilder
SIGN IN →

SHD NETWORK POLICY

TERMS & PRIVACY.

Effective July 27, 2026. These terms set the rules for using SHD.build and explain what information we process to operate and secure the service.

01 · SERVICE02 · ACCOUNTS 03 · USER CONTENT04 · CONDUCT 05 · PRIVACY06 · COOKIES 07 · RETENTION08 · THIRD PARTIES 09 · DISCLAIMERS
01

THE SERVICE

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.

02

ACCOUNTS & SECURITY

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.

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.

03

USER CONTENT

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.

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.

Community Oversight may hide or remove profile biographies, profile messages, avatars, builds, guides, comments, or other user content that violates these terms or presents a safety, privacy, legal, or abuse risk. Removing content does not remove related moderation, audit, or legal records when SHD.build must retain them.

SHD.build may screen user content with local rules and OpenAI’s moderation API before or after publication. Automated classification can publish clean content or hold flagged content for Community Oversight; an authorized human makes the final decision on held or reported content.

04

COMMUNITY CONDUCT

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.

05

INFORMATION WE PROCESS

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, public biography, profile visibility, public authored-content summaries, profile messages, 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.

A public Agent profile displays your public display name, avatar, assigned site-role names, biography, public builds, published guides, recent public discussion, and profile messages. SHD.build does not display role permissions, descriptions, or direct permission grants on public profiles. Other signed-in users may post messages on a public profile when their account has permission to do so. Profile messages display the author's public identity and may be removed by their author or Community Oversight.

You may hide your Agent profile from public discovery and prevent new profile messages. Hiding a profile does not remove your display name or avatar from public builds, guides, or comments you authored. It also does not make existing public content anonymous.

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.

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.

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.

When automated content screening is enabled, SHD.build sends submitted text, Guide images, or custom avatar images to OpenAI’s API for safety classification. SHD.build does not include your password, authentication tokens, or private sign-in credentials in that moderation request. We retain the resulting category scores, flags, request reference, content hash, local-rule matches, and review outcome as needed to operate moderation, investigate abuse, and document decisions.

After SHD.build sends content to OpenAI, OpenAI controls its processing under its then-current service terms, privacy policy, data controls, and SHD.build’s OpenAI account settings. Those rules may permit retention, human safety review, or use for model improvement, including when data sharing has been enabled. OpenAI currently states that API data is not used to train or improve its models unless the API customer opts in, and that default abuse-monitoring logs may be retained for up to 30 days, subject to stated exceptions. SHD.build cannot guarantee that OpenAI’s terms or practices will remain unchanged. Review OpenAI’s API data controls, Services Agreement, and privacy policy for the current rules governing API content.

06

ESSENTIAL COOKIES

SHD.build currently uses only first-party cookies needed for authentication, sign-in protection, and anonymous Guide ratings or reports. We do not 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.

COOKIEPURPOSEDURATIONPROTECTION
shd_visitorProvides a random pseudonymous browser identity for Guide ratings, duplicate report suppression, and abuse limits. The database stores only a domain-separated SHA-256 hash of the cookie value.Up to one year.HTTP-only, SameSite=Lax, Secure in production.
shd_sessionMaintains your sign-in and associates requests with your server-side session.Up to 30 days, or until sign-out or session invalidation.HTTP-only, SameSite=Lax, Secure in production.
shd_discord_oauth_stateValidates a Discord sign-in or linking response and helps prevent request forgery.Up to 10 minutes; SHD.build removes it after processing the callback.HTTP-only, SameSite=Lax, Secure in production; limited to the Discord authentication path.

After repeated anonymous rating or reporting activity, SHD.build may display a Cloudflare Turnstile challenge. The server sends the challenge token and request address to Cloudflare for verification. Cloudflare processes that information under its own terms and privacy policy. SHD.build does not store the raw address as the rating or report identity.

Your browser stores dismissal of the informational notice in local storage under shd-essential-cookie-notice. 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.

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.

07

RETENTION & DELETION

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.

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. Account deletion removes the public biography and makes the Agent profile unavailable. SHD.build may keep public builds, guides, and comments under a “Deleted Agent” attribution so community references remain intact. SHD.build may retain backups and records for a limited period when fraud prevention, dispute resolution, or law requires them.

08

THIRD-PARTY SERVICES

SHD.build may connect to OpenAI for content safety classification, Discord and future identity providers for sign-in, and email services for message delivery. 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.

09

FAN-SITE & LEGAL DISCLAIMER

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.

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.

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.

Copyright owners and authorized agents may use our DMCA & Copyright Policy and copyright request form. Send other questions through Contact Us.

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.

For authoritative information about Ubisoft intellectual property, consult Ubisoft’s official Terms of Use and the official The Division Resurgence site.

SHD.build RESURGENCE DATA & TOOLS

Independent builds, guides, game data, news, and community intelligence for The Division Resurgence.

COMMUNITY NETWORKJOIN SHD DISCORD ↗
CONTACT USBUY ME A COFFEE ↗DMCA & COPYRIGHTTERMS & PRIVACYCOOKIE POLICYDATA RETENTION

UNOFFICIAL FAN SITE · NOT AFFILIATED WITH OR ENDORSED BY UBISOFT. TOM CLANCY’S THE DIVISION, THE DIVISION RESURGENCE, UBISOFT, AND RELATED INTELLECTUAL PROPERTY ARE OWNED BY UBISOFT AND/OR ITS LICENSORS.