Privacy notice

Marketing status and identity

Inquiry status history is stored in the marketing schema, separate from GuardianChain platform records. New submissions receive an initial received state; this is not evidence of human review or a service commitment. The sole owner is bootstrapped only from a matching, provider-verified sign-in email. The server then binds that account's OIDC issuer and subject; future owner checks use that exact pair. Email, client flags, profile fields and form values do not grant owner authority.

Inquiries

We store your name, email, organization or subject, message, submission type and time, and privacy acknowledgement in this application's marketing schema to respond to you and evaluate partner inquiries. This schema is separate from GuardianChain authority, evidence, receipt and operational records. One designated owner may review contact and design-partner inquiries, update their status, assign follow-up and add private internal notes. Those notes are not shown in Partner Access or sent to submitters. No evidence engine, authority service, billing service or marketing-email delivery is activated.

Updates

The separate product-updates form records your email, explicit consent, consent-notice version and submission time. Signing up records interest; it does not start email delivery or a paid subscription. Email delivery may be introduced later only with appropriate consent and unsubscribe controls.

Partner Access

Signing in uses an external identity provider to supply your identifier, email and available profile information. We store profile and session data and use a secure, HTTP-only session cookie for this limited site. Only inquiries submitted while signed in are linked to your account; anonymous inquiries are not claimed by matching email addresses. Signing in never grants operating-platform access.

Storage and protection

The site uses Replit-hosted application and database services. Forms are validated and protected with a honeypot and a submission limit. A time-bucketed hash of a network address is used for rate limiting; request diagnostics may also be processed by the hosting provider. Please do not submit secrets, sensitive evidence or regulated personal information.

Published-site analytics

The published informational site loads a Replit-hosted analytics script from i.replit.com/script.js. Checks of the eight public pages on October 15, 2026 (UTC) observed page-visit requests to i.replit.com/api/send containing the page URL, page title, hostname, referrer, screen dimensions, browser language and a site identifier. These observations cover signed-out public-page visits, not Partner Access sign-in or form submissions. Provider-side processing and retention were not established by this browser inspection.

Cookies and browser storage

Those checks observed a cookie named GAESA on guardianchain.org; Replit documents it as an infrastructure-routing cookie. No additional cookies, advertising requests, or localStorage or sessionStorage entries were observed during those public-page visits. This observation is not a guarantee about every browser configuration or future hosting change. Partner Access uses the separate sign-in and session cookies described above. No new analytics service has been added to this temporary site.

Retention and requests

No fixed retention period is set, and marketing submissions are not deleted automatically. Use the dedicated request form to ask for deletion or to withdraw product-updates consent. A request stays in a pending queue until the configured owner reviews it; the email you enter is not proof of identity, and the owner must explicitly confirm any action. This site does not send email or an email receipt; the form confirms submission on screen. The pending request stores your email, request type and submission time, and its details are removed when the owner closes it.

What happens next

If a deletion request is confirmed, all contact, design-partner and updates submissions matching the request email are deleted from the active marketing data store, along with their marketing-only notes, review and status-history records. The pending request records for that email are removed too. This workflow does not inspect or erase infrastructure backup copies. It does not delete Partner Access profiles or sessions and never touches GuardianChain authority, evidence, receipts or operating records. If product-updates consent is withdrawn, the updates signup is retained with consent turned off; contact and design-partner inquiries remain unless deletion is separately requested. If a request is closed without action, no inquiry or consent data is changed. Completed request details are not retained.