Prepared October 12, 2026. Proposed prototype terms require affirmative adoption; no customer agreement is formed by reading this page.
AssureDocket Prototype Terms and Policies
Supersharp Shop LLC | Policy revision 0.5 | Prepared October 12 2026
This package sets out proposed terms for evaluating AssureDocket, a product initiative of Supersharp Shop LLC. The authorized pilot evaluates one defined AI workflow and produces evidence for human review. It does not authorize access to other systems or certify that a customer is compliant, secure, or ready for production. The policy revision is separate from the prototype runtime, which remains version 0.4.
Adoption and document order
These prototype terms take effect for an organization only when its authorized representative expressly accepts this version through a signed pilot order or a recorded acceptance process. Preparing or displaying this document does not amend an existing contract. The website currently has no prototype enrollment or contract acceptance mechanism.
The signed pilot order defines the parties, scope, dates, fees, support, applicable law and venue, and permitted data. A signed data processing agreement governs its subject matter; a signed confidentiality agreement governs confidentiality where it expressly differs. The pilot order may override these terms only by identifying the affected provision and the agreed change. Marketing, a roadmap, a proposal, a badge, or an AI-generated answer cannot expand the authorized scope.
Prototype evaluation terms
1 Parties and authority
The service provider is Supersharp Shop LLC, using the AssureDocket product name. The customer is the legal organization named in the signed order. AssureDocket is not represented as a separately formed legal entity, registered DBA, or cleared trademark by these terms. Each signer must have authority to bind the party represented. Organization users must be adults authorized to act for the customer.
2 Evaluation license and access
For the agreed evaluation period, Supersharp grants approved users a limited, nonexclusive, nontransferable right to use the designated prototype for the agreed internal evaluation. The order must identify the build or commit, environment, account owners, and permitted users. Existing open-source or separately granted license rights remain governed by their own terms. Access must stop when authorization expires or is revoked. No evaluation right grants access to a third party's infrastructure.
3 Written scope before testing
Before testing, the parties must identify the exact hostname or workload, organization, environment, owner, approved connectors or supplied artifacts, test window and timezone, permitted actions, prohibited actions, rate limits, stop conditions, and emergency contacts. The system owner must approve these details in writing. A scope expansion, new connector, live-data class, privileged operation, or production recovery exercise requires a written scope change before it occurs.
4 Default mode and prohibited activity
The default evaluation uses synthetic or properly sanitized data in a private local or isolated staging environment. Shadow mode records observations without changing the customer's operational decisions. These terms do not authorize exploitation, password guessing, credential harvesting, phishing, malware, persistence, unrelated discovery, denial of service, interception of others' communications, active dark-web infiltration, or actions against suspected attackers. Any separately contracted security testing requires its own rules of engagement. Do not expose the present local scaffold as a public or multi-tenant customer service.
5 Approved evidence and data rights
The customer must have rights to supply and permit the agreed processing of evidence. Collect the minimum evidence needed for the defined checks. Prefer metadata, approved identifiers, digests and references over raw content. Do not upload secrets, private keys, passwords, personal client correspondence, protected health information, student education records, children's data, payment-card data, or other restricted records under the default evaluation. A later use involving personal or regulated data requires a documented lawful basis, necessary notices and permissions, an appropriate data agreement, and deployment-specific security approval before intake.
6 Customer content and intellectual property
The customer retains its rights in its supplied content. Supersharp receives only the permission needed to carry out the agreed evaluation, secure the environment, and deliver the agreed evidence package. Customer content may not be sold, published, used in unrelated demonstrations, or used to train a general model under these terms. Third-party AI processing is disabled for customer evidence unless the order identifies and approves the provider, purposes, retention and training settings. Supersharp retains its platform and pre-existing methods; the customer receives the right to use its delivered reports for internal review and agreed disclosures. Any custom-code ownership must be stated in the order.
7 Feedback and publicity
Voluntary nonconfidential feedback may be used to improve the product without transferring ownership of the customer's content, confidential workflows, or inventions. A customer's name, logo, quote, benchmark, results, or participation may be used publicly only with separate written permission specifying the disclosure. A mentor reference, an application, or a conversation is not an endorsement, partnership, or customer commitment.
8 Confidentiality and personnel access
Each party must use the other's confidential information only for the agreed work, limit access to people with a legitimate need and confidentiality obligations, and apply reasonable safeguards appropriate to the information. Public information, independently developed information, and information lawfully received without a duty of confidentiality are excluded. Legally compelled disclosures must be limited to what is required; provide notice when legally permitted. Customer evidence must be treated as confidential even if it does not qualify as a trade secret.
9 Independence and human responsibility
The evaluated workload must not be the sole authority for its verification result. The order must identify evidence sources, their operators, the verifier, reviewer, key custodians, and any common ownership or access that limits independence. A separate software process or shared-key signature alone does not establish operational independence. The customer retains decisions about deployment, underwriting, procurement, communications, incident declarations, and return to service. AssureDocket supplies scoped evidence and decision support.
10 Meaning of results
VERIFIED means only that the named checks accepted the supplied evidence for the recorded target, version and test conditions. It does not establish that all source statements are true, every action was observed, the AI is safe in general, or a regulator accepts the result. REVIEW_REQUIRED means material evidence or confidence is insufficient or conflicting. FAILED or REJECTED identifies a failed defined check; it does not by itself attribute malicious conduct. NOT_TESTED and UNVERIFIED must remain visible when a control has not been assessed. Operational colors such as GREEN are workflow states, not legal or technical certifications. Expired evidence must not be treated as current proof.
11 Actual scaffold limitations
The inspected version 0.4 package stores records, nonces, snapshots and events in memory. Restart may remove them. Its signatures use a shared HMAC key, including development fallbacks; they are not public-key signatures that an outside reviewer can independently verify without sharing the secret. Core evidence routes lack complete authentication and organization isolation. Submitted time observations are not authenticated independent clocks. The verification route checks nonce reuse and expected artifact/policy values but does not comprehensively bind evidence to the requested organization and deployment. Continuity transitions do not enforce a validated recovery attestation before GREEN. These limits prevent treating the scaffold as a durable archive, production security boundary, or independently validated recovery system.
12 Evidence integrity and retention
Hash chains can expose certain modifications when a trustworthy reference and verification procedure are retained. They do not prove completeness or defeat all rewriting by an administrator controlling storage and keys. For an evaluation, the customer retains original records and approved exports. The order must establish raw-content handling, export responsibility, retention periods, deletion procedures, backup expiry, legal holds and evidence custody. No permanent-retention promise applies to the memory-only scaffold. Corrections should preserve an audit trail while lawful erasure requirements are handled through the approved retention architecture. Digests and pseudonymous identifiers may still require privacy protection.
13 Recovery and containment exercises
Restoration is a controlled test only when separately included in the signed scope. Define the known-good artifact, policy, configuration, tool permissions and identity, plus the permitted recovery actions and reviewer. No destructive action, isolation, account change, credential revocation, or restart may occur without the specified authority. A simulation or comparison of a submitted snapshot is not proof of restored production behavior. Return to service requires the customer's approved decision and independently collected post-recovery evidence. The current runtime does not automate that complete gate.
14 Providers and integrations
Use customer-approved exports and documented APIs within the customer's actual provider permissions. Provider account ownership, API-key access, and contracts do not automatically authorize all data collection or onward disclosure. The order must document the permitted evidence path. AssureDocket is independent of Apple and other providers; these terms imply no affiliation, certification or private-infrastructure access. Provider confidentiality, intellectual-property restrictions, revocation rights, and data restrictions remain applicable. Apple Business analytics or documentation must not be redistributed merely because AssureDocket can ingest them.
15 Fees and milestone acceptance
The working full-pilot price is up to $7,550 for one authorized workflow, subject to a signed order. Suggested milestones are $2,550 for scope and kickoff, $3,000 for a test-ready baseline, and $2,000 for evidence delivery, findings review and one scoped retest. These are proposed fees, not booked revenue or a subscription. No payment is required to use the public planner or make an inquiry. Before charging, the order must state deliverables, review period, acceptance criteria, taxes, expenses, due dates and cancellation terms. Payment buys the agreed work, not a favorable verification result or certification. Ongoing monitoring and additional retests require a separate scope.
16 Evaluation availability and changes
The prototype may contain errors, change, or become unavailable. There is no uptime commitment, support SLA, recovery time or recovery point promise unless expressly signed. Material scope changes must be documented. Supersharp must not apply a new data use retroactively merely by updating a page. Material contractual changes require notice and the agreed acceptance process. Security suspension may occur when needed to stop an immediate risk, with prompt notice where practicable.
17 Incidents and cooperation
Each party must promptly notify the designated pilot contact after discovering unauthorized access to pilot evidence or a material scope violation, preserve relevant records, and cooperate on bounded investigation. The signed data agreement must set any required notice deadline and content for personal-data incidents; applicable legal deadlines still govern. No notification capability, around-the-clock response, or human attacker identification is implied by the prototype. Pause intake if evidence exposure or authorization uncertainty arises.
18 Suspension and termination
Either party may stop the evaluation for expired authority, material breach, unresolved data/security risk, or a lawful instruction. The order must define notice, any cure period, earned milestones and refund treatment. A proposed fair commercial rule is to pay for accepted work and approved noncancelable costs, refund unearned prepaid amounts, and provide available approved exports before deletion, subject to legal restrictions. This proposed rule becomes binding only when adopted in the order. Stop access, revoke issued credentials, and document custody and deletion at closeout.
19 Warranties and responsibility
To the extent law permits, the evaluation prototype is provided as is and as available. There is no guarantee of completeness, fitness for a production purpose, breach prevention, regulatory approval, insurance acceptance, financial return, or future functionality. These qualifications do not excuse misleading statements, breach of signed obligations, or duties that law does not allow a party to disclaim. The customer must retain its existing safeguards, records, qualified reviewers and recovery procedures.
20 Liability allocation and disputes
The parties must approve a liability clause before a paid or customer-data pilot. A proposed B2B starting point limits ordinary aggregate liability to the greater of $1,000 or the fees paid or payable under the pilot order during the preceding twelve months, and excludes indirect or consequential losses to the extent lawful. Counsel must assess suitable treatment of confidentiality, security, privacy, intellectual property, fraud, gross negligence, willful misconduct and nonwaivable rights; those matters are not silently capped by this drafting proposal. Governing law, venue and any dispute mechanism belong in the signed order. No mandatory arbitration, class waiver, personal guarantee or blanket customer indemnity is created by this package.
21 Contact and mandatory rights
For scope, privacy, security or terms questions, use supersharp.assuredocket@vidalsky.com. Formal notice details must be completed in the order. If an adopted provision is unenforceable, the remaining provisions apply to the extent lawful. Applicable mandatory legal rights remain intact. Neither a domain location nor an illustrative scenario establishes the provider's jurisdiction or a governing law clause.
Public website terms and privacy notice
The public site presents product information, a concept film, local examples, a planner and a curated guide. Reviewing the site does not sign a pilot contract, authorize security testing, enroll the visitor in recurring billing, or create an investment offer. Example screens and local historical test counts must retain their fixture/build/date labels. Sources and market scenarios are informational; no business outcome is promised.
The inspected site has no visitor accounts, server-side intake, payment checkout or advertising-tracker code. Planner and guide interactions run in the browser. Email links open the visitor's mail application; information reaches Supersharp only when the visitor sends a message. Hosting and security services can process delivery records such as IP address, time and request details. The stylesheet currently requests Google Fonts, which can transmit network information to that provider. External source links lead to other organizations' policies. Do not interpret local planner processing as a claim that no network requests occur.
An inquiry may contain a name, role, organization, contact details and the information the sender chooses to include. Use it to respond, assess pilot fit, maintain necessary business records and address security or legal issues. Do not solicit confidential evidence through ordinary email. Access should be restricted to people and service providers supporting those purposes. Any use for newsletters, public testimonials, unrelated profiling, advertising or model training requires its own appropriate permission and notice.
Before publishing an operational privacy policy, confirm the provider inventory, mailbox access, log retention, international transfers, tracking choices and deletion process. A proposed inquiry-retention target is 90 days after an inquiry closes unless an active engagement, lawful hold or documented recordkeeping need requires longer. This is an implementation choice awaiting configuration, not a verified current deletion schedule. Visitors can send privacy requests to the contact above; authenticate requests proportionately and respond under applicable law. Do not promise a universal response deadline or statutory regime without establishing applicability.
Pilot order and authorization schedule
The following must be completed and signed before an external evaluation. It supplements the existing bounded verification request; it does not authorize systems through a blank or incomplete form.
| Required field | What the order must record |
|---|---|
| Parties and signers | Customer legal entity and provider, addresses, signer names, roles and authority |
| Build and systems | Runtime/build digest, exact assets, hostnames, owners and environment |
| Test authority | Permission evidence, dates, timezone, allowed methods and rate limits |
| Data and providers | Allowed data classes, evidence source rights, connectors and approved processors |
| People and escalation | Observer, verifier, reviewer, key custodian and emergency contacts |
| Commercial agreement | Deliverables, fee, milestones, review period, acceptance and cancellations |
| Records and privacy | Export, retention, deletion, legal holds, incident notices and data agreement |
| Recovery boundaries | Simulated or actual exercise, permitted actions, baseline and return-to-service authority |
| Legal provisions | Applicable law, venue, approved liability allocation and existing contract priority |
| Acceptance evidence | Terms version, document digest, signatures or affirmative acceptance, timestamps and copy delivered |
Activation requirements
Use the documentation for local synthetic evaluation now. Before a real customer-data pilot, correct authentication and organization/evidence binding, eliminate default credentials, implement approved durable evidence storage and key custody, validate observer and clock sources, enforce recovery attestation, and obtain independent security review appropriate to the scope. Establish the operational privacy and contract records listed above. A signature on these terms cannot make an unimplemented control effective.
Drafting references
The customer-data and provider provisions respond to the supplied Apple Business Terms of Service in abus.pdf, English main agreement sections 2 through 7, pages 2 through 6. That reference constrains Apple Business use; it does not prove compatibility with Apple products generally. Separate Managed Services provisions and any actual API terms must be assessed for a specific integration.
The FTC explains that privacy commitments about AI data use must be honored and that undisclosed changes in purposes can create legal exposure. This supports matching the proposed notice to actual processing before activation. FTC privacy and confidentiality guidance.
Technical limitations are grounded in the inspected assuredocket_trust_resilience_v0_4.zip, including app/store.py, app/security.py, app/main.py and its README. Existing project inputs include the October 1 Authorized Verification Request, paid-pilot scope, architecture notes and security acceptance criteria. These are drafting references, not certifications or counsel approval.