Privacy Policy

JEEKSSHIRE 24 | Legal. Version dated 23 October 2026. This policy covers the macOS application and https://legal.jeeksshire24.com, including cloud workspaces, AI, contact verification and payments. Reading this policy is not consent to optional processing.

Who is responsible

The service operator is JEEKSSHIRE 24 FZE LLC, registration number 2624416735888, Ajman NuVentures Centre Free Zone, UAE. Address: Office CWS-1V-227119, 26th Floor, Amber Gem Tower, Sheikh Khalifa Street, Ajman, United Arab Emirates. Privacy and support contact: jeeksshire024@gmail.com. If you upload information about clients or employees, you are also responsible for lawfully providing it. The application does not replace any data processing agreement your organisation needs.

Information we process

• Account information: name, email, internal user ID, password hash, contact verification, sessions and linked sign-in methods. We store a phone number if you choose phone verification.
• Workspace content: documents and working versions, uploaded files, AI conversations and replies, a drawn signature, selected country and region, and interface preferences.
• Party profiles: names, representatives and authority, addresses, email, phone numbers, tax and registration identifiers, bank account details and any additional fields you enter.
• Payments: plan, order and subscription IDs, amount, currency, period, status, payment events and AI quota usage. The app does not receive card numbers or CVCs; you enter these on the payment provider's page.
• Technical information: IP address at sign-in and code requests, operation time and outcome, request identifiers and errors needed for security and service operation. This is not an advertising profile.

Do not upload information you are not entitled to share, passwords, card credentials, state secrets or unnecessary health or other sensitive information. A signature drawing is not used for biometric recognition or identity verification.

Purposes and grounds

We use account and workspace data to provide the requested service: authentication, synchronisation, editing, storage and handling your requests. Payment and mandatory recordkeeping require order information. Proportionate technical information protects access and prevents abuse. Where applicable, the grounds are performing a contract, legal obligations and legitimate interests in security, subject to your rights. Optional disclosure to an external AI requires separate permission. Where local law requires additional consent, it must be obtained separately. This policy does not provide consent to marketing.

External AI

For an authorised AI request, our server sends Anthropic, through the Claude API, your prompt, relevant conversation history, selected document, jurisdiction settings and selected party details. This can include personal and confidential information in the content. You can decline AI disclosure and use local reading, editing and export; saving to a cloud workspace is a separate operation.

Legal research uses external web tools. Public search queries should exclude party names and private contract terms; this does not prevent the full authorised context from reaching the AI provider. Review and minimise information before sending it. Declining a subsequent request does not reverse a completed disclosure.

Anthropic sets its own contractual API processing periods, including security and legal exceptions. We do not promise zero retention. Current information is available at https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data. We do not use your documents to train our own models; the provider's processing terms must be checked separately and are not replaced by this statement.

Recipients and locations

Cloud workspaces are hosted on DigitalOcean infrastructure in Frankfurt, Germany. Authorised service administrators can access this infrastructure. Anthropic processes authorised AI requests. Google or Yandex supplies basic profile information when you choose its sign-in service. SMTP.bz receives the email address and service email content; a backup SMTP provider is used for the corresponding delivery. Telegram Gateway receives your phone number and verification code if you request phone verification. Stripe or T-Bank receives information required for the payment you select, including receipt email. SMS.ru is not an active delivery channel in this version.

Providers may process information in other countries. Selecting Russia or another jurisdiction for a document does not relocate servers. We do not claim Russian database localisation, zero AI retention or end-to-end encryption. Before organisational use, assess localisation, international transfer and professional secrecy obligations. Consent cannot override mandatory legal restrictions.

Security and retention

Each account has its own ID and workspace database. TLS, access controls, password hashing and AES-256-GCM protect workspace content, history and stored credentials. Keys are held in a separate server directory outside the document volume. This is neither end-to-end encryption nor an external KMS: authorised servers need access to content. Pending edits on Mac use Keychain/safeStorage encryption; the web version uses encrypted IndexedDB storage, which does not protect against a compromised site origin. You control exported files. Local Mac OCR does not send scans to an external AI provider; you review recognised text before applying it.

Your account supports data export, import of your own backup, section history and document trash. Up to 20 section versions are kept for 30 days within a separate storage budget; large documents may reduce the count. Regular users can initiate deletion in Account → My Data → Delete Account, with password confirmation and an explicit confirmation. Stripe renewal is cancelled before deletion. The account, linked sign-ins, active sessions, documents, chats, party profiles and credentials are removed from working systems. Financial and necessary security records are assessed separately for mandatory retention. The service owner must first transfer administration through support.

Hourly backups are encrypted with a public recovery key; the private recovery key is held off-server. An additional encrypted copy is stored on the operator's trusted Mac. Scheduled backup retention is 30 days; a powered-off or suspended device performs cleanup when it next runs. A minimal deletion receipt, consisting of a hash of a random user ID and deletion date, is retained for 90 days outside the workspace database to prevent restored accounts from returning. Current receipts must be preserved and deletions reapplied before restored systems become accessible. Immediate erasure of all backup and external copies is not promised. Verification codes last 10 minutes and sign-in sessions up to 12 hours; these are not deletion periods for all related records. Contact jeeksshire024@gmail.com for data requests and retention exceptions.

Your rights

Depending on applicable law, you may request access, correction, a copy, deletion, restriction or portability; object to processing; withdraw consent for future optional operations; and complain to the competent data protection authority. Write from your account's verified address. We verify ownership proportionately and respond within the applicable legal deadline. Under GDPR, the usual response period is one month, subject to permitted extensions. Shorter mandatory periods elsewhere remain applicable. Do not send passwords, sign-in codes or card details.

Age and changes

The service is intended for adults and organisations, not children. Contact support if children's information has been supplied without a proper basis. Material changes to processing must be communicated before new processing; new consent is requested where required. The version and date are published in the service's document centre.