Privacy Policy
A static, read-only evidence archive. There are no accounts, nothing to log into, and no forms. We collect as little as the web allows, and never sell it. Below is exactly what gets processed when you visit, who processes it, and how to ask for a correction or removal.
In short
- No accounts, no sign-ups, no forms. There is nothing for you to submit.
- No advertising, no ad trackers, no cross-site tracking. We never sell data.
- No tracking cookies. Our host sets one security cookie for its bot check; otherwise, on-device storage holds only your own preferences, recent searches and reading place.
- Visitor analytics are cookieless and aggregate: totals only, never individuals.
- The site keeps nothing about you on its own servers. Your IP address is seen only by our host, Cloudflare, in its connection logs.
- We can't identify individual readers, and we don't try to.
Who this covers
This policy applies to the Titanite Accords website at titaniteaccords.com. It does not cover third-party services we link out to, such as Discord, which keep their own policies.
The site is published in the public interest as a documentary archive, operated by the maintainers of Titanite Accords ("we", "us"). It is not affiliated with, or operated on behalf of, any government agency. Any seals or insignia in the interface are decorative.
What we don't do
To be unambiguous, the site does not:
- require or offer accounts, registration, or sign-in;
- collect names, emails, phone numbers, or payment details from visitors;
- serve advertising, or embed any advertising or marketing tracker;
- use cookies or storage to follow you across other websites;
- build advertising profiles, fingerprint your device, or sell visitor data to brokers.
What we process when you visit
- Connection & security logs. Our host and CDN, Cloudflare, automatically processes basic connection data such as your IP address, request time, the page requested, and your browser user-agent. This delivers pages, defends against abuse, and keeps the service running, under Cloudflare's privacy policy.
- Bot check. On each page view, Cloudflare runs a small script, served from this site's own address, that tells browsers from automated traffic. It keeps its result in one cookie, described below.
- Aggregate analytics. We use Cloudflare Web Analytics. It is cookieless, keeps no client-side state, does not fingerprint visitors, and reports only aggregate figures.
- Web fonts. Typefaces are served by this site. Loading them sends no request to a font service.
- Images in the archive. Profile pictures, custom emoji and server icons are stored and served by this site. Your browser makes no request to Discord, and Discord is not told that you are reading the archive. Images Discord still hosted for the original exports, such as link previews and expired attachments, are not loaded at all. Where no stored picture exists, the picture is simply left out.
- Archived media. Where the archive serves media, it is delivered with a
no-referrerpolicy. - On-device storage. A few small values, like your theme, zoom and spacing preferences, the view and sort order you chose, where you stopped reading the analysis, recent on-site searches, and a flag for choices you've confirmed, live only in your browser. They are never transmitted to us.
Cookies and local storage
The site's own pages set no cookies. Our host, Cloudflare, sets one: cf_clearance, which holds the result of its bot check. The site's pages cannot read it, it stays with this site rather than being shared across others, and it expires after a year unless you clear it.
The only other browser storage is the on-device preference data described above, which exists solely to make your own visit nicer. It is not a tracking mechanism, and it is never sent to us. Because the one cookie is for security and nothing here follows you across sites, we believe no consent banner is required, and we'd rather not interrupt you with one.
Service providers
The stack is deliberately small. The providers that may process visitor data are:
- Cloudflare, Inc. Hosting, content delivery, security (including the bot check and its cookie), file storage for the archive’s media, and cookieless Web Analytics. (Privacy policy)
We use no advertising networks and no behavioural-tracking services.
Your rights and legal bases
Depending on where you live, for example under the EU/UK GDPR or the CCPA, you may have rights to access, correct, or delete personal data about you. Because the site itself stores nothing that identifies a visitor (no account, no contact details, nothing on its own servers), there is usually no personal data of yours for us to retrieve or erase. Where we do process limited data, we rely on our legitimate interest in running a secure, public-interest archive and preventing abuse.
If you believe the site holds personal data about you, contact us below and we'll respond in good faith. Requests about a person named or documented in the published archive are handled separately, under Published Material.
Data retention
- Cloudflare's operational and security logs follow Cloudflare's own retention schedule.
- The site’s own storage holds nothing about visitors. Article reactions, and the salted hashes their rate limit kept, were removed on 26 September 2026 and deleted the same day.
- On-device preferences stay in your browser until you clear them.
Published material: corrections & removals
This is an evidence archive, so some pages document identifiable people. All such material was obtained lawfully and is published for documentary, public-interest purposes. Sensitive personal information is redacted as a matter of policy.
- If you are featured and believe something is inaccurate, wrongly redacted, exposes sensitive personal information, or should be removed, contact us with the specific page and the issue.
- We aim to acknowledge a request within a few days and reach a decision within 14 days. Where the archive's public-interest purpose weighs against removal, we'll explain our reasoning rather than ignore you.
- Requests involving the safety of a minor, or the exposure of sensitive personal data, are our highest priority.
Corrections made. Dated, newest first. A correction is listed here the day it goes live.
- 22 Oct 2026. One ISS inquiry file taken down in full, with its 94 indexed messages. The totals now read 114 channels and 50,402 messages.
- 9 Oct 2026. The Updates account of a public discussion now refers to members of the site’s team by role, not by username; the quotations are unchanged. Working notes removed from the site’s source code.
- 30 Sep 2026. Three accounts in the ISS exports now appear under codes (“Member-” and four characters). Their usernames, Discord IDs, profile pictures and Roblox profiles are removed. Where their names were typed, a marker stands in their place: “Name”, or “Potential name” for a name that is also an everyday word. In bot posts about them, Roblox profile links and unrecognised handles are removed too. The analysis and one Updates article use the codes. Two of the three had appeared under two display names each, so the index now counts 100 persons, not 102.
- 27 Sep 2026. Page descriptions and footers no longer call the ISS exports “unmodified”: they are published as exported, with personal information redacted where identified. The Updates articles no longer call the archive’s release a leak in our own words, and the board no longer claims to map every connection. Two stale figures corrected: the persons count (101; the index counts 102) and one channel total (116; now 115).
- 27 Sep 2026. This policy corrected: the reaction hashes it still mentioned had already been deleted; a missing profile picture is left out, not drawn as an initial. Our host’s bot check sets a year-long cookie on every visit, which this policy did not say; it now does.
- 26 Sep 2026. One ISS inquiry file taken down in full, with its 37 indexed messages. The totals now read 115 channels and 50,496 messages.
- 26 Sep 2026. The stated ages of people who were minors at the time removed: one on the ISS landing page, five in the analysis, four in the framework.
- 26 Sep 2026. Two Discord account ids quoted in the analysis redacted. A listing for a document the archive never held removed.
- 26 Sep 2026. “Leaked” removed from the site’s descriptions of its own archive.
- 26 Sep 2026. Article reactions removed; their stored tallies and salted hashes deleted the same day. Until this date some profile pictures, emoji and link previews in the ISS exports still loaded from Discord, contrary to this policy. Pictures and emoji are now served by this site; the link previews are not loaded at all.
- 14 Aug 2026. ISS figures corrected. The launch figures, 117 channels and 57,000+ messages, matched neither the export files nor the search index; the archive held 116 channels and 50,533 indexed messages.
Children's privacy
The site is not directed to children and does not knowingly collect personal information from any visitor, including children. Because the archive documents real events, it may reference minors. Where it does, sensitive personal information and images are redacted as a matter of policy. If you are a parent or guardian concerned about how a minor is referenced, see Published Material; those requests are our highest priority.
Security, transfers & contact
The site is served only over encrypted HTTPS, with a strict Content-Security-Policy and a no-referrer policy. Our providers operate globally, so the limited processing above may occur on servers outside your country. Those providers maintain their own safeguards for international transfers.
Questions, rights requests, and correction or removal requests can be sent through the Titanite Family Discord. We aim to acknowledge good-faith requests promptly.
Changes to this policy
We may update this policy as the site evolves. When we do, we revise the "Last updated" date above. Continued use of the site after an update means you accept the revised policy.