AccessProof Service Terms
Effective October 22, 2026
1. Operator and business use
AccessProof is operated by Scott Corlett, an individual in California, United States. These terms apply to your business subscription. The initial service is available to United States business customers. You must be authorized to accept these terms for your business and instruct AccessProof for the connected GitHub organization. Supply an accurate business name, complete US business address and business-use declaration. These supplied details are not independent identity, address, residency or geolocation verification. Privileged actions require fresh proof that you are an active owner of the connected organization.
2. Your monthly service
$499 USD per month, before any applicable tax shown before purchase, covers one fixed selected, organization-owned, active private non-fork GitHub repository. The service supports outside-collaborator expiry policies, scheduled access checks, returned-access findings, supported authorized enforcement, separately checked outcomes and available evidence/activity records. The plan supports up to 100 active expiry policies, 500 observed collaborators and 3 automatic enforcement cycles per workspace per UTC day. No annual plan or free trial is included in this offer. Findings and available evidence are provided in the app. Automated customer-email alerts are not included at launch.
3. Your instructions and GitHub permissions
You choose the repository, collaborator, expiry and policy. Automatic expiry enforcement and enforcement after returned access require their respective explicit instructions. Reader requests Metadata read and organization Members read. Executor additionally requests repository Administration write, which is broader than removal-only; AccessProof constrains its use in software. Neither App requests Contents permission. Removal can have GitHub-defined effects beyond the immediate permission change, including effects on forks and other GitHub resources. Review those effects before authorizing removal. Removal and its provider side effects are not universally reversible.
4. What a verified result means
A separate read-only App makes fresh provider-reported observations to assess the supported result. A successful write response alone is not verified success. Verification concerns the stated repository and identity at the observation time. It is not an outside audit, login test, compliance certification, breach-prevention guarantee or permanent prevention of future access. Organization, team and enterprise access changes, pending invitations, downloaded copies, other identities and unselected repositories are outside the supported scope.
5. Schedule and availability
Nominal check choices are 5 minutes, 15 minutes, hourly or daily. Checks are polling while the service and required provider, authorization and payment evidence are available. Provider rate limits or outages, authorization expiry, changed scope and unresolved operations can delay results or require customer action. An expiry does not guarantee removal at the exact deadline. Unavailable or unresolved results are not represented as successful protection.
6. Payment and renewal
Your subscription renews monthly unless you cancel renewal before the next renewal. The total, including any tax collected, is shown before purchase. Verified paid billing status is required for paid entitlement; a checkout return page alone is not payment proof. Stripe processes payment and billing interactions. Payment failures or an unverified billing state can prevent paid operations. A future applicable tax or price change will be disclosed before it affects your subscription.
7. Cancel renewal
Cancel renewal in Subscription / Billing without a sales call. Wait for Stripe-confirmed cancellation and the displayed paid-through date. Ordinary cancellation takes effect at period end and does not automatically request a refund. Stopping monitoring or disconnecting does not cancel renewal. Billing management requires fresh GitHub owner proof. After disconnecting, billing-only Reader authorization lasts up to 10 minutes and can manage an existing subscription; it does not reconnect monitoring, authorize Executor or create a new checkout. Keep Reader installed until cancellation or refund is finished. If you removed Reader, the current self-service route requires reinstalling Reader for the same organization and fresh owner proof. Executor and monitoring do not need to restart. If this route is unavailable, contact support@accessproof.net.
8. First-payment refund
You may request one full refund of the first qualifying payment within 7 × 24 hours of that payment. The request requires explicit agreement to immediate subscription cancellation and the immediate end of service entitlement. The supported refund is the verified original invoice/payment total, including any supported collected tax. Renewal payments are outside this voluntary first-payment policy. An already-refunded, disputed, unsupported or ambiguous payment may require resolution before a refund can proceed. A pending refund remains pending until Stripe confirms it. Bank or card credit timing is not guaranteed. This policy does not limit rights that applicable law does not allow us to exclude.
9. Stopping, disconnecting and leaving
Stopping checks or enforcement prevents queued recurring operations from starting a write; an operation already sent may still complete. Disconnecting removes workspace token fields and stops local monitoring and watches. It does not cancel billing, uninstall GitHub Apps or delete account records. Save available evidence you need and finish billing actions before uninstalling Apps in GitHub to revoke their installation grants. Cancellation does not regrant removed access or undo GitHub side effects.
10. Data, support and security
Our Privacy Notice describes data uses, provider handling and retention. Only eligible recurring access-check history has automated 30-day cleanup, with maintenance and backlog delay. Other records and backups are outside that cleanup. Complete automated account deletion is not available; privacy requests use the disclosed support process. Product, billing and privacy questions: support@accessproof.net. Security reports: security@accessproof.net. Do not send passwords, App keys, tokens, card details or repository source code. No staffed-response service-level commitment is included in this plan.
11. Service risk and liability
The service is provided as available. We do not promise uninterrupted or error-free operation. To the extent applicable law allows, we disclaim implied warranties and exclude indirect or consequential losses. Our aggregate contractual liability arising from the service is limited to the fees you paid for the service during the three months before the event giving rise to the claim. These limitations do not exclude fraud, willful misconduct or liability that cannot lawfully be limited. California law governs these terms, subject to mandatory applicable law.
12. Changes and contact
We will disclose material service, price or terms changes before they affect an existing subscription, with an opportunity to stop renewal. Changing the catalog does not silently reprice an already accepted offer. Questions about these terms may be sent to support@accessproof.net.