This page lists third‑party processors ("Subprocessors") we use to deliver the Foreclose AI Platform. Each Subprocessor processes limited Personal Data under our instructions to provide specific functionality.
1. We keep data collection to the minimum necessary.
2. We do not use Customer Data to train AI models.
3. We primarily host in AWS ap‑south‑1 (Mumbai); some providers operate global infrastructure.
| Provider | Role / Purpose | Categories of Personal Data | Location(s) | Notes |
|---|---|---|---|---|
| Amazon Web Services, Inc. (AWS) | Cloud infrastructure: compute, storage, networking, managed services (e.g., logging/backups) | Account metadata, operational telemetry/logs, configuration data, limited support data | Primarily ap‑south‑1 (Mumbai) | Encryption in transit and at rest (AWS KMS). |
| Supabase | Authentication & identity management | Account identifiers (name, email), OAuth profile attributes (if provided by IdP), auth logs | Provider‑managed regions | We do not store raw passwords; Supabase handles auth. |
| Resend, Inc. | Transactional email delivery | Business email addresses; message routing metadata; limited template variables | Provider‑managed regions | Used for service emails (e.g., verification, alerts). |
| Cashfree Payments | Payment processing | Billing contact details and payment tokens/IDs; we do not store card numbers | Provider‑managed (primarily India) | Subject to Cashfree terms; used only for payments. |
| Google LLC (Google Analytics 4) | Optional analytics (only with consent) | Pseudonymous identifiers, device/browser info, page/events, approximate geolocation | Provider‑managed global infra | Disabled by default where consent not provided; GPC honored. |
None at this time.
• Contractual data protection terms, including confidentiality and security obligations.
• Technical and organizational measures appropriate to the data and risk.
• Data minimization, access controls, and retention aligned with our policies.
We will update this page to add or replace a Subprocessor and, for material changes, provide at least 15 days' advance notice via this page and/or in‑product/email notice. In urgent cases (e.g., security, continuity), we may add or replace a Subprocessor immediately and notify promptly thereafter.
Subscribe to updates: Email founder@laikatest.com with subject "Subscribe: Subprocessor Updates" and we'll notify you of changes.
If you reasonably object to a new Subprocessor, email founder@laikatest.com within 15 days of notice. We'll work with you in good faith to provide a commercially reasonable alternative. If we cannot, you may terminate the affected Service features (or the Agreement, if materially affected) without early‑termination charges, and we will refund any prepaid, unused fees for the terminated portion.
We aim to keep processing in ap‑south‑1 (Mumbai) for core hosting. Some Subprocessors may process data in other jurisdictions depending on their infrastructure and your configuration. Where required, we use appropriate safeguards (e.g., Standard Contractual Clauses) as described in our Privacy Policy.
Questions about this list or a provider? Contact us for more information.