SERVICE POLICIES

Privacy Policy

Published September 20, 2026

What Access Desk processes, who can see it, and how to request help or deletion.

Who to contact

Access Desk is a US-based software service operating under the Access Desk brand. The contact for this policy and privacy requests is ikr99111115@gmail.com. Please include your account or purchase reference when useful, but never send an access code, password, bot token, bank information or identity document by email or in public Discord channels.

Access, purchases and support

We process website order and Stripe checkout/payment references, agreed price and currency, consent revision, your chosen platform, fulfillment and revocation status, access-account identifiers, device-key fingerprints, request signatures, usage limits and timestamps. When you use Discord, we also process user, server, channel, application and any native purchase-entitlement identifiers. These support authentication, one-device access, payment verification, delivery, account security and support. Stripe processes website payment details and the contact information you enter during checkout. Discord and its providers process any native Discord payments. Access Desk’s delivery service does not receive card numbers.

The storefront uses an essential, Secure, HttpOnly browser cookie for private order access, lasting up to 32 days from a visit. Only a hash of its random value is stored with an order. Your browser also stores a list of recent order references and an in-progress checkout reference; these do not contain payment details or activation credentials. Clearing cookies can remove your automatic access to an order page. Administrator recovery links contain a temporary secret in their URL fragment; the server stores only its hash and whether a browser has claimed it.

Discord stores messages you send there and the codes or links delivered there. Private support channels are visible to the customer, the configured owner and the bot; Discord administrators can override channel permissions. They are private from ordinary members, not end-to-end encrypted. The bot does not request Discord’s privileged Message Content intent. Information sent to our support email is used to handle your request.

Questions and AI processing

Text, images, screenshots and source audio you submit for AI features are sent over HTTPS to our Cloudflare-hosted service and Google Gemini. This includes content captured from the selected practice window when you enable the Mac’s capture features. The device signs requests; signing does not hide content from our service or the AI provider. Google’s handling is governed by the Gemini API terms. Do not submit content you are not authorized to share.

Private administrator history

Updated Mac clients retain submitted questions, screenshots, source audio/transcripts, generated answers and request outcomes for administrator review. Built-in practice and mock records also include original exercises, selected choices, written responses, blanks, sentence order, drafts saved on leaving/restarting/quitting, skipped items and completion status. Speaking records prompt/timer status, not a microphone recording or proof of speaking. This is not a keystroke log, and it does not verify submissions made in other exam apps.

These server records remain until an authorized administrator explicitly deletes them. There is no automatic expiry. Content is encrypted before private storage and is available through authenticated administrator tools. Turning off or clearing local history, signing out, or allowing access to expire does not delete this separate archive. Queued records can finish uploading under their original account after access expires. Contact ikr99111115@gmail.com to request review or deletion.

Windows 1.0.4 preview and older clients that do not opt into the administrator-history feature retain their existing behavior. The Windows preview requests no answer replay storage from our service; that does not control Google’s separate processing or access/billing metadata.

Data on your device

Settings and preferences are stored locally. Optional local history is encrypted and starts off. Mac credentials and encryption keys use Keychain and a Secure Enclave device key; Windows credentials and history use Windows user protection and a TPM-backed device key. Private device keys remain on the device. Mac pending study records are encrypted locally until uploaded. The app’s Copy Answer feature attempts to expire its owned clipboard copy; other apps or recipients may retain copies you share.

Infrastructure, retention and transfers

Cloudflare provides hosting, network protection and private storage; Google processes AI requests; Stripe processes website payments; Discord provides messaging, support and any native entitlements or checkout; email support uses Gmail. These providers may process data in countries other than yours under their own terms and privacy policies. Technical request metadata, including IP addresses processed by the hosting service, may be used for security, reliability and rate limiting.

Access, fulfillment and security records have no general automatic deletion schedule. We retain them for service operation, support, fraud prevention, duplicate-delivery prevention and applicable obligations, and review deletion requests individually. Content-free receipts can remain after a content deletion to prevent old retries from recreating the content. Infrastructure backups may retain prior data for their applicable retention periods. We do not sell customer data or use third-party advertising trackers in these policy pages.

Your controls and requests

You can pause capture, manage the app’s privacy settings, clear local history, sign out, and contact us about server records. Depending on applicable law, you may have rights to access, correct, delete or otherwise control personal data. We may need to verify account ownership before acting, and explain when legal or security obligations prevent deletion. Keep private credentials out of the request.

Policy updates

We publish changes here with the revision date. Material changes to how submitted content is retained should be disclosed before the updated behavior is used. This policy accompanies our Terms of Service.