Your documents.
A defined purpose.

Draft notice for the pre-launch application. Provider settings, retention details and final privacy disclosures require verification before customer processing is enabled.

This service is operated by JP Associates FZC, United Arab Emirates.

What the service processes

The service uses your verified account, project brief, selected supporting evidence, generated documents and billing status to create and manage your packs. Workspaces are designed for owner-only access. Files are not offered through public document links.

AI and no training

The application uses a direct business API account and is designed not to opt customer content into training, model improvement, feedback, evaluation datasets or cross-customer knowledge bases. Provider terms and account settings must be verified before AI processing is enabled. A configuration switch alone is not proof of compliance.

Original files are parsed by the application worker. Only the bounded brief and selected evidence reviewed by you are sent for generation. The AI provider receives that content and produces a draft. Responses use storage disabled and foreground execution. This does not establish zero retention: standard API abuse monitoring and model-specific caching may retain data under the provider’s applicable terms. See OpenAI data controls.

Providers and access

The planned processors are Vercel for hosting, Supabase for accounts and storage, OpenAI for generation, Trigger.dev or a reviewed self-hosted worker for processing, Stripe for billing and Resend for notifications. Each may process data needed for its role. Regions, agreements and retention settings must be recorded before launch. Private access does not mean end-to-end encryption or that service providers never process content.

Retention and deletion

Initial defaults are 30 days for originals and extracted evidence and 90 days for generated versions and exports. You can explicitly change retention for active content. Expired or deleted content becomes inaccessible immediately; physical deletion runs through a retryable queue.

Deleting a source does not by itself remove facts already in reports. The deletion control offers removal of dependent versions. Project deletion covers its files, evidence, versions and exports. Workspace deletion also requests account removal. Minimal billing records may remain. Backups and processor retention can outlast application deletion; their actual expiry periods must be verified and disclosed before launch.

Appropriate content

Launch scope is business documents. Patient-identifiable clinical records need a separately approved deployment. Do not upload them here. Review unnecessary personal information before generation.

Requests and contact

Use Data and retention in your authenticated workspace to delete content. For privacy enquiries, contact JP Associates FZC at enquiries@jpassociates.services. Do not attach supporting documents or sensitive project details to email.

Digital purchases and refunds

Digital purchases are non-refundable, except where a refund is required by applicable law. Please review the product description and samples before purchasing.

If your digital product is not delivered, is defective or does not match its description, contact us so we can review the issue and provide the remedy required by applicable law. Your statutory rights are not affected.

Read the purchase terms for the full scope.