The agreement, in plain terms.
These terms govern use of Déjà. Enterprise customers additionally sign an order form and, where applicable, a Master Services Agreement — where those differ from this page, they control.
- Effective
- 8 August 2026
- Entity
- Déjà, Inc. · Delaware
- Contract questions
- legal@deja.dev
- Sections with counsel
- 3
The registered address is not yet published on this page. Déjà, Inc. is incorporated in Delaware; the registered address will be stated here and in Section 16. Until then, ask legal@deja.dev and we will give it to you in writing.
Orientation only — the numbered sections are the operative terms
- One
You own your data
We process it to run the service and for nothing else. No sale, no sharing with advertisers, no model training.
- Two
Your receipts outlive us
Signed receipts stay verifiable offline against a published key, whether or not you are still a customer and whether or not we still exist.
- Three
We never stop signing over money
A billing dispute does not put a gap in your ledger. Access can be suspended for non-payment; sealing and signing continue.
- Four
Trial and production receipts are issued identically
We do not currently distinguish them by key or by any marking, and this agreement does not ask you to tell them apart.
- Five
The standard is open, the service is not
DSR/1.0 is Apache-2.0 and anyone may implement it. The hosted service that produces receipts is ours.
- Six
We don't promise admissibility
Déjà supplies a record. Whether it is admissible anywhere, and whether it satisfies any regulation, is not something we warrant.
Acceptance
These terms govern your use of Déjà, operated by Déjà, Inc. By creating a vault, including a trial vault, or by accepting these terms at signup, you agree to be bound by them.
If you accept on behalf of an organisation, you confirm you are authorised to bind it, and "you" means that organisation and its authorised users. If you do not agree, do not create a vault.
Where you have signed an order form or Master Services Agreement with us, that document controls to the extent it differs from these terms.
The service
Déjà keeps a record of what your connected systems reported and what changed. Signals from the sources Déjà scores are sealed into an append-only chain when they are scored; where a signal carries the information needed to do so, changes in a lookback window are scored against it, and the outcome is recorded whether or not anything is attributed. Signals from other connected sources are received but not sealed; our How it works page lists which sources are scored.
Attribution is narrow by design. It covers a defined set of schema-change patterns described in our documentation. Most signals do not produce an attribution, and receive a receipt recording the outcome instead. Nothing in these terms should be read as a commitment to attribute any particular incident.
We may change or discontinue features. Where a change materially affects a paying customer, we will give reasonable advance notice.
Vaults and accounts
A vault is the organisation-level scope that owns a chain of receipts. Creating one requires a work email address on your organisation's domain — consumer email domains are declined, because a vault is identified by an organisation rather than a person.
Where your domain already has a vault, you will be offered a request to join it or the option to create a separate vault. Separate vaults keep their data isolated and their own receipt chains. Vaults on Déjà's managed signing key share that key; Enterprise and Sovereign vaults can use their own.
You are responsible for your credentials and for activity under your account. Tell us promptly if you believe access has been compromised.
Trials
- Trials are free, fully featured, and require no payment card.
- The fourteen days start when you sign up. Time spent configuring your vault during onboarding counts toward the trial.
- Paid tiers carry a monthly attribution allowance — Standard 200 a month, Charter 42 a month, with Enterprise and Sovereign unmetered. Exceeding it never blocks sealing or signing and is never charged; it opens a conversation about scope.
- Trial and production receipts are currently issued identically — the same vault key, no trial marking, no watermark. We do not represent them as distinguishable, and nothing in these terms asks you to tell them apart.
Fees
Paid tiers are charged as set out on our pricing page or your order form. Pricing is by scope — vaults, seats, retention, key custody and support. There is no per-receipt charge and no overage: the attribution allowance in section 4 is never charged.
We may change prices with at least sixty days' written notice before your renewal date. A price change does not affect a prepaid term until renewal.
With counsel · not yet in force
Invoice timing, payment terms, late payment, tax, currency, proration and auto-renewal mechanics are being finalised. Until this section is published, billing terms are those set out in your order form.
Acceptable use
You agree not to:
- Use the service unlawfully, or to process data you have no right to process
- Attempt to access another customer's vault, receipts or data
- Deliberately submit false or misleading data to induce a particular attribution outcome
- Circumvent technical restrictions or rate limits
- Reverse-engineer the hosted service, except where the law says you may
We may suspend access for a material breach, with notice where practical.
What this does not restrict
Nothing here limits your rights under the DSR/1.0 licence. The specification is published under Apache-2.0 and you may implement it, build your own verifier, write integrations against it, or publish a competing implementation of the standard. The restrictions above concern the hosted service, not the open format — and an evidence standard nobody else can implement would not be a standard.
Your data
You own your data. You grant us a limited licence to process it solely to provide the service — sealing signals, examining changes, and issuing and delivering receipts, including the governance receipts that record changes to your configuration and access.
We do not sell it, do not use it to train models, and do not share it beyond the subprocessors listed in our privacy policy or where the law requires. Where we process on your behalf, you are the controller and we are the processor; enterprise customers sign a Data Processing Agreement, which controls where it differs from these terms.
Retention follows your tier as set out on the pricing page. You can export your receipts at any time, including after termination until your data is destroyed; what the export contains is described on our Security page. Erasure is carried out on your instruction; we do not currently issue a signed receipt attesting to the destruction itself, and we do not claim one.
Receipts and keys
Receipts are sealed into an append-only chain. Specific classes additionally carry a digital signature: Ed25519 on Déjà's managed key, or RSA-PSS or ECDSA where you use your own key.
We do not retroactively invalidate receipts. A receipt issued during your subscription stays valid. Database triggers reject deleting a receipt, and reject updating one except to record a review decision or fill an empty link or hash once; and a change to a signed field breaks its signature, which holds against us as much as against anyone else.
Verification does not depend on us. Signed receipts are checked offline against a published public key, using open tooling, with no account and no call to our systems. We will keep the public keys required to verify any receipt we have issued publicly available, and this obligation survives termination of your subscription.
A signature establishes the content of a receipt and the authority of the key that signed it. It does not establish the time at which anything occurred — issuance timestamps are asserted by us and are not currently anchored to an external time source.
On evidence
Déjà supplies a record. We make no warranty that a receipt is admissible in any proceeding, or that it satisfies any regulatory requirement. Determination, classification, filing and certification under DORA, 23 NYCRR Part 500 or any other regime remain with your named accountable individuals.
Intellectual property
The hosted service — software, interface, documentation and branding — is ours, and these terms grant you a limited, non-exclusive, non-transferable right to use it.
DSR/1.0 is published under the Apache License 2.0. You may verify receipts, implement verifiers and build integrations against the specification with no Déjà subscription and no permission from us. The receipt format is open; the service that produces receipts is not.
If you send us feedback or suggestions, we may use them without obligation to you, unless a separate agreement says otherwise.
Warranties and disclaimers
We warrant that during a paid subscription the service will perform materially in accordance with the Documentation — meaning the DSR/1.0 specification and the system documentation published at the time, not marketing pages. This warranty does not apply to trials.
Otherwise the service is provided "as is" and "as available", and we disclaim all other warranties, express or implied, including merchantability, fitness for a particular purpose and non-infringement.
We do not warrant that the service will be uninterrupted or error-free, that any particular incident will be attributed, or that the service alone will satisfy your regulatory or audit obligations.
Limitation of liability
With counsel · not yet in force
This section is being drafted by external counsel and is deliberately not published in placeholder form. Until it is, liability between us is governed by your order form or Master Services Agreement, or in the absence of one, by applicable law. We would rather leave this blank than publish something we cannot stand behind.
Indemnification
With counsel · not yet in force
Being drafted. Enterprise and Charter customers negotiate indemnification in their agreement; ask us for the current position at legal@deja.dev.
Termination
By you. Cancel at any time from your vault settings or by contacting us. A trial vault can be deleted immediately. Paid terms follow your order form.
By us. We may suspend or terminate for material breach, or for non-payment after a reasonable opportunity to cure.
After termination, your access ends and your data is retained for the period set out in the privacy policy to allow export, then erased on your instruction. Receipts issued during your subscription remain verifiable, and the key-availability commitment in Section 8 survives.
The commitment that survives a billing dispute
Suspension does not stop your ledger. Where access is suspended for non-payment, sealing and signing continue, so the record of the period remains complete and you can export it once the account is settled. There is no circumstance in which a commercial dispute with us puts a gap in your evidence.
An evidence product with a kill switch is not an evidence product, and we would rather pursue an unpaid invoice than hold a record hostage.
Governing law and disputes
With counsel · not yet in force
Choice of law, venue and dispute resolution are being settled with counsel and are deliberately not published in placeholder form. Enterprise agreements set these out expressly; ask at legal@deja.dev for the current position.
Changes to these terms
We may update these terms. For material changes we will email you and post a notice in your vault at least thirty days before they take effect. Continued use after that date means you accept the revised terms. Previous versions are available on request.
Where you hold a signed agreement with us, these online terms are subordinate to it.
Contact
Contract and procurement questions: legal@deja.dev. Privacy: privacy@deja.dev. Security and vulnerability reports: security@deja.dev.
These terms govern use of the Déjà service. Where a customer has signed an order form or Master Services Agreement, that agreement controls to the extent of any difference. Déjà supplies a record of what connected systems reported and what changed; it does not determine root cause, file regulatory reports, or discharge any obligation under any regulatory regime.