Subprocessors
Service providers used to operate Saff.
Purpose of this list
Lenouar uses trusted service providers to run Saff, process documents, manage payments, send transactional emails, run background tasks, and store encrypted data.
This list explains what each provider is used for. It may be updated as Saff changes, subject to applicable customer agreements and notice requirements.
| Provider | Category | Purpose | Data handled | Notes |
|---|---|---|---|---|
| DigitalOcean | Application hosting | Hosts the Saff website, application, and background worker. | Application requests, sign-in related information, service logs, and public/protected pages. | Uploaded document bytes are stored in Cloudflare R2 during processing, not in application hosting storage. |
| PostgreSQL 17 on DigitalOcean | Database | Stores account, workspace, billing, and extraction records. | Account, workspace, billing, activity, table, batch, row, and encrypted extraction records. | The database runs on Lenouar-controlled DigitalOcean infrastructure. Sensitive extracted values are encrypted by Saff before being saved. |
| Cloudflare R2 | Temporary file storage | Stores encrypted temporary uploads while Saff processes documents. | Encrypted temporary document files and basic file details. | Objects are deleted after processing, failure handling, cancellation, or expiry cleanup. |
| Stripe | Payment processing | Processes embedded wallet top-up payments and payment status updates. | Payment references, customer/payment identifiers, transaction details, and receipt-related payment status. | Saff does not store raw card numbers. |
| Microsoft 365 | Transactional email | Sends account, verification, reset, and receipt email messages. | Recipient email address, localized email content, and delivery information. | Saff sends transactional mail through a Lenouar-managed Microsoft 365 mailbox. |
| Redis provider | Rate limiting and background jobs | Stores request rate-limit counters and background queue state for document processing and cleanup jobs. | Rate-limit keys, job IDs, workspace/table/batch/file IDs, retry status, and redacted job details. | Background job data is not intended to include plaintext document content or extracted values. |
| AI extraction processing provider | AI processing | Reads document content during processing and returns extracted values for the fields selected by the user. | Document content, file type, table field details, extraction instructions, and extraction results. | Saff does not show the underlying AI provider name in normal product screens. |
| Customer-selected S3-compatible storage | Customer-controlled storage | Stores retained original files only when a workspace chooses to keep originals. | Encrypted retained original files and basic storage details. | The customer controls the bucket, region, access policy, lifecycle policy, and provider relationship. |
Connected storage is customer-controlled
When a workspace connects S3-compatible storage, Lenouar does not choose the customer's storage provider or region. The workspace owner is responsible for that bucket and for deciding whether it meets the customer's requirements.
Saff encrypts retained originals before writing them to the connected bucket. Users preview or download retained originals through Saff instead of receiving direct bucket links.
Contact
For questions about Saff subprocessors, contact Lenouar Artificial Intelligence Developing Services LLC at services@lenouar.ae or +971555537749.