Last updated: 21 October 2026.
Assurance Desk test data
Assurance Desk differs from the local-only Proof Engine. Its controlled devnet preview stores signed-in account identifiers, invitation email addresses and hashed invitation tokens, workspace details, registered public keys, agreements, approvals, uploaded signed evidence, calculated statements, review notes, test invoices, public devnet payment observations and audit records in the hosting database. Workspace evidence is shared with its agency and invited client. Subscription billing and payment exceptions are restricted to the agency; separately authorised PactVerity support operators can inspect recorded payment cases and append review notes. Application request-budget counters contain a hash of the platform account identifier, not an anonymous identifier.
A separate authenticated quote journal stores the original workspace and owner identifiers and test invoice for recovery after a database rollback. It follows the same preview retention limits; database deletion alone does not erase that journal. Recovery requires the existing workspace and original owner and does not automatically grant credit.
Only authorised, synthetic or non-sensitive test records belong in this preview. Do not upload private keys, API credentials, confidential response bodies or real customer records. A role-filtered workspace snapshot and individual statement exports are available. Records remain stored until a reviewed retention and deletion process is established; no automatic expiry or self-service erasure is promised. Shared evidence must not be silently removed from the other party. Contact contact@pactverity.com about access or deletion requests. Any public devnet transaction remains on its network independently of database deletion. These preview boundaries are not a production service agreement or a completed privacy review.
Information currently processed
The website hosting infrastructure may process ordinary technical request data required to deliver and protect pages and API endpoints, such as IP address, device and browser information, request time, response status and security metadata.
The public Proof Engine processes agreement terms, supplied evidence, output text and imported receipts locally in the browser. Raw output text is hashed locally and is not included in the generated receipt. Using the browser engine does not intentionally upload its inputs or receipts to the PactVerity Receipt API. Users can download a receipt to their own device.
The public Receipt API beta is a separate, optional path. JSON submitted to its create or verify endpoints transits PactVerity's hosting infrastructure so the server can return a result. The application does not intentionally store request bodies or receipts in a database or intentionally write those bodies to application logs. Ordinary hosting, abuse-prevention and security metadata may still exist. Do not submit secrets, private keys, recovery phrases, confidential material or unnecessary personal data to either the browser engine or the API.
The deterministic scenario simulator runs in the browser and uses model counts, nominal amounts and a seed. It moves no funds. Its default $25,000,000 result is synthetic nominal volume, not customer activity; service and escrow volume is $0.
If a user chooses an optional wallet signature, the page requests the connected public Solana address and asks the wallet to sign the receipt digest as an off-chain message. The signature, public address and signed message are included in the receipt. This proves key control only, not identity, role or evidence truth. The action does not require SOL or submit a blockchain transaction. The engine disables automatic wallet persistence.
When the owner launch console is used, it requests the connected public wallet address, reads its SOL balance through PublicNode and asks that wallet to sign mainnet transactions. Before broadcast, the signed transaction bytes and public signature are sent to PactVerity's same-origin validator, which accepts only the exact published mint ceremony; the browser then broadcasts an accepted transaction through PublicNode. Neither service receives a seed phrase or private key. Owner authorization remains inside the wallet. The mint address is deterministically derived from the published owner address, original SPL Token Program and a fixed public seed, so no separate mint-account secret is generated or stored.
The Buy PVTY page requests a read-only test quote from Jupiter through PactVerity's market-status endpoint. The route checker sends token mint addresses and a fixed test amount; it does not send a visitor's wallet address, balance or intended purchase amount. This read-only check is separate from the embedded Jupiter swap component. When using the component, entered amounts and token selections are processed by Jupiter; connecting a wallet exposes its public address and may expose balances to the wallet provider and swap infrastructure. A swap requires the user’s wallet approval, and signed transactions are broadcast through the providers’ infrastructure to public Solana. The component and its network requests can expose ordinary technical request information, including IP address, to third parties. Review the displayed fees and minimum received before approving. PactVerity does not receive recovery phrases or private keys. External Jupiter or Raydium links leave this website and are governed by the selected provider; the embedded component also remains subject to Jupiter and wallet-provider policies.
The Integration Challenge application stores the applicant's name, email address, project name, public project URL, selected track, proposal, evidence plan, consent version, review status and submission time. The weekly evidence-update form stores the subscriber's email address, active status, signup source, consent version and subscription time. The design-partner form stores the contact name, work email, organisation, public URL, proposed use case, available evidence signals, pilot goal, review status, consent version and submission time. These records are used only to evaluate integration or pilot proposals, contact applicants and deliver requested PactVerity project updates. Do not include secrets, private customer data, wallet credentials or confidential source material.
When you submit an integration or design-partner enquiry, an email alert containing your contact details, organisation or project name and reference is sent to contact@pactverity.com through the owner-operated enquiry service hosted by IONOS on madniumrah.co.uk. Full proposal details remain in the PactVerity records. A private delivery record tracks whether the mail service accepted the alert; it does not prove inbox receipt. Labelled synthetic tests are excluded from customer lead counts. With optional analytics consent, a successful genuine-form submission records a generate_lead event without contact details; it is not a human qualification or sale.
Optional first-party visitor analytics
From 21 October 2026, optional visitor analytics sends page views and defined tool-use actions only after you select Allow analytics. You can decline without losing access to the tools, and withdraw using Analytics choices in the footer. Do Not Track and Global Privacy Control disable collection. Declared crawlers and ordinary internal quality-assurance sessions are excluded, but bot filtering cannot prove that every recorded visit is human.
With consent, the application stores a random browser identifier for up to 30 days and a random session identifier that expires after 30 minutes of inactivity. The session records the initial optional campaign source, medium and campaign labels and external referring hostname. The server stores these identifiers with an event identifier, event type, public page path without query strings, coarse device class and server timestamp. It does not intentionally store IP addresses, raw user-agent strings, full referrer URLs, wallet addresses, receipt contents or cross-site profiles in these analytics tables. Hosting security logs are separate.
Private date-filtered reports are restricted to the configured site-owner account. They show consenting browsers, sessions, page views, source labels and actions, not verified individuals, customers or token purchases. Declining consent, blocking scripts, using multiple devices or clearing storage affects the counts. Historical cumulative growth counters remain separate and are not retroactively converted to unique visitors.
An explicit measurement diagnostic visit can record consented test events under the source label measurement_qa. These use per-event transient random identifiers and are displayed separately to the owner, never included in visitor totals or legacy counters. The same opt-out and retention rules apply.
New detailed analytics reports cover a maximum of 90 days. Records older than 90 days are removed in batches of up to 1,000 whenever collection or an authorised report runs; on an inactive site they remain stored until that cleanup runs. No continuous or scheduled deletion service is represented. Legacy non-identifying aggregate event records retain their existing handling. Contact contact@pactverity.com for privacy questions; do not send wallet credentials.
Responsible project and contact boundary
The separate general Solana mint checker sends the entered public address to PactVerity's read-only endpoint and its configured Solana RPC provider, currently Helius with allowlisted public-provider fallbacks. It requests finalized account data only, without wallet connections or signatures. Provider authentication is held server-side and is not exposed in browser code. The application keeps at most 100 results per server instance in temporary memory and reuses a result for no more than 30 seconds. Expired entries are discarded on subsequent checks or when the server instance is recycled. It does not intentionally persist the entered addresses in a database or application logs. Hosting and RPC providers may retain technical request logs. This differs from the local-only PVTY identity comparison below. Never enter private keys or recovery phrases.
The PVTY mint checker compares a pasted public address locally in your browser. The checker does not send or store the pasted address. Successful clipboard actions and address-check button actions may generate the same privacy-minimised growth events described above, without the input or comparison result. They measure actions, not unique people, wallet ownership or token purchases.
The founder confirmed on 6 October 2026 that PactVerity has no incorporated operating company and no completed legal review. It is described as a community-driven project with a worldwide audience; that description does not establish decentralised control or legal permission to promote a token in every country. The founder monitors contact@pactverity.com for privacy, data-rights and security reports. Security correspondence is used to assess and respond to the reported issue; do not send confidential evidence until a suitable exchange method is agreed. No response time or bounty is promised. Applicant and subscriber records will be retained while the challenge or subscription remains active and then deleted when no longer required, subject to legitimate security or legal recordkeeping needs.
Fixed PVTY public-data endpoints share short-lived database snapshots of public blockchain and quote results to reduce repeated provider calls. Stored timestamps show when those results were checked. Fixed aggregate counters limit the site's provider calls and general mint-check requests across server instances; these counters do not store visitor IP addresses or submitted mint addresses. Provider failures and expired results are reported as unavailable rather than presented as fresh verification.
Blockchain information
The owner wallet, mint and token-account addresses, balances, transaction signatures and transactions may be sent to Solana RPC services and recorded publicly on Solana. Public blockchain records cannot generally be removed by clearing this website's data.
Cookies and local storage
The PVTY guide compares two factual research invitations only with analytics consent. Its random A/B label is kept in sessionStorage; exposure and click events use the same consenting-browser and session identifiers described above. These are measured actions, not verified people or purchases. The experiment is disabled when Do Not Track or Global Privacy Control is enabled or session storage is unavailable; internal QA is excluded. No advertising audience is created.
The analytics consent choice is stored locally so it is remembered. Browser and session measurement identifiers are created only after consent and removed from local storage when consent is withdrawn; previously received records follow the retention description above. Campaign labels are scoped to the measured session. The optional research-invitation comparison also requires analytics consent. Third-party swap providers have their own data practices.
No advertising cookies are intentionally used. With analytics consent, a visible page load or client-side route change is counted once; reloading a page can count another view. The Proof Engine and scenario simulator store no receipt or scenario in localStorage. The owner console disables automatic wallet persistence and stores a public recovery record in browser localStorage containing the canonical mint address, launch stage, attempt times and available transaction signatures so an interrupted launch can be reconciled. It can also download those public identifiers as JSON. The same canonical address is re-derived if browser data is lost; neither mechanism stores wallet secrets. Clearing site data removes only the local record, not a downloaded file or blockchain records.
Third-party services and links
The Receipt API and owner transaction validator use this site's hosting provider. The owner console interacts with the connected Wallet Standard provider, PactVerity's same-origin validator and PublicNode's Solana mainnet RPC. Links to Solana, PublicNode, x402 or future exchange services are governed by those providers' own policies. Sending an API request or opening an external link may reveal ordinary request information to the relevant provider.
Changes
This notice will be updated when processing materially changes and before introducing materially different processing. Existing embedded swaps and owner-console signing are described above; planned PactVerity service settlement is not represented as deployed.