Privacy policy

What we handle

Close Fetch processes firm account data (names, emails), client contact details, and the documents your clients upload — typically bank and card statements. Documents are stored privately and access is scoped to your organization.

How we use it

Client documents are read by AI providers solely to extract the fields needed to match them to your close requirements (institution, account last-4, statement period). Provider processing and retention terms must be confirmed in the final agreement before live client use.

Where it lives

The application supports Supabase for database and authentication, and private Supabase Storage or Cloudflare R2 for files. The actual hosting region, encryption configuration, backup policy, and provider retention terms must be verified before real client use. Database access rules isolate each firm’s records.

Retention and deletion

The provisional application behavior retains documents until the firm owner requests deletion. Owners can export their firm’s records, offboard a client while retaining records, or schedule client deletion with a 24-hour cancellation window. Minimal deletion audit records remain. Backup expiry and provider-held copies require a finalized provider policy. This is an implementation assumption, not a legal retention recommendation.

Supported service providers

This is the application’s integration list. The final subprocessor list, contracts, and model-training commitments remain subject to review.

• Supabase (database, auth, file storage)
• Cloudflare R2 (optional file storage)
• Resend (transactional email)
• Stripe (billing)
• OpenAI and Anthropic (document extraction)
• Vercel (hosting)
• Inngest (background jobs)
• PostHog (product analytics)
• Sentry (error monitoring)