The paperwork is already public

Three documents set the relationship. All three are readable without an account, and a reviewer can quote them by section.

Retention follows the kind of record. The figures below restate what the privacy policy already fixes in writing.

Closing an account runs from account settings, and it takes effect on the spot. Where a law requires a record to remain, the screen names that record and the period it is kept for. The three routes out — doing it yourself, asking by email, and handling a connected Facebook or Instagram account — are set out step by step on how to delete your data.

The access we ask for differs by channel. One page sets out each permission, the API methods it lets us call, what we decline to ask for, and how you take it back. Permissions we ask for, channel by channel

Company changes are kept in one place with the date attached: when the service opened, when the name and address changed, when the product changed. You can check for yourself how long the sentence you are reading has stood. The record so far

Figures ship with the conditions that produced them, fixed at the moment of measurement. We call that fixing a seal: the query set, the surfaces read, the repetition count and the judging rules are hashed when the run happens, so a later edit to the numbers shows up. Five stops take a reviewer from the method to our own scorecard.

1. Stop 1

   Open the method

   How queries are built, which surfaces are read in what order, and how a citation is separated from a mention. Open the methodology

2. Stop 2

   Check the denominators

   How many questions go out, to which named places, how many times each, and the read rates a round has to clear before it ships. Open the measurement spec

3. Stop 3

   Pin the terms of art

   Citation, mention, answer presence, confidence interval: each fixed to a single definition you can quote. Open the definitions

4. Stop 4

   Trace the figure

   Numbers used in public writing are registered with source type and reference date. Open the claims registry

5. Stop 5

   Read our own numbers

   We run the same reading on ourselves and republish it every round: the readings we failed to take, the times our instruments were wrong, and how often AI answers cite us. Open our own numbers

What a diagnosis collects is used to build and verify the report for that engagement. It stays inside the scope and the retention window the contract sets, and a client's own asset data is used for that client's work.

Aggregates published on this site are shaped so that no single client can be identified. Every figure that appears in public copy is registered with its source type and reference date in the public claims registry.

The reporting route is published in machine-readable form as well. The file sits at the location RFC 9116 defines, and carries the contact address, an expiry date and the languages we can respond in.

• /.well-known/security.txt: the standard location
• /security.txt: same content, for scanners that read the root
• Email works too: support@citeangle.com

We acknowledge receipt, then report what we found and when it was addressed in the same thread.

The same content people read is emitted for machines. What each file carries, and how to open it, is written out on the docs page.

• /rsl.xml: licensing notice for published research (free use with attribution)
• /robots.txt: crawler access guidance
• /sitemap.xml: public pages and their last change dates
• Docs: the human guide to those files and the data rails

Operational signals live one page over: the signals the service emits about itself, and the thresholds that move it into a warning state, are on the status page. The same reading is available as JSON, so you can check it at any moment without asking us.