1. Information we process
We process the identity and organization information needed to authenticate you and control access, including your name, email address, organization membership, role, and session activity. We also process the provider connections your organization authorizes, including the connected team or account, sync status, period coverage, and redacted spend and usage metadata.
2. Vercel data
When your organization connects Vercel, Spendclose uses the OAuth permission shown during authorization to read billing and usage information for the selected team. We use team and project identifiers to attribute the data. Spendclose does not access deployment source code and does not deploy, edit, or delete Vercel projects.
3. How we use information
We use information to authenticate users, enforce organization-level access controls, sync provider data, calculate supported spend views, show evidence and freshness, operate the close workflow, prevent abuse, troubleshoot failures, and maintain an audit trail. We do not use customer spend data for advertising or sell it to data brokers.
4. What we store and what we do not
Spendclose stores redacted financial and usage metadata, invoices, derived facts, connection metadata, and audit events needed to operate the service. Provider credentials are held in managed secret storage and are not rendered in the UI, returned in API responses, or written to ordinary application logs. We do not store prompts, model completions, ordinary developer API keys, or raw application payloads as part of the spendclose data model.
5. Service providers
We use infrastructure and service providers to host the application, protect secrets, store evidence, authenticate users, and retrieve data from the providers you authorize. They may process information only to provide those services, under the applicable agreements and security controls. Your organization remains responsible for choosing which provider accounts to connect.
6. Security
Spendclose uses organization-scoped authorization, tenant isolation, secure session cookies, least-privilege provider access, managed secret storage, and audit logging. No system can promise absolute security, so please report suspected unauthorized access through the support contact provided by your organization administrator.
7. Retention and deletion
Provider credentials are deleted immediately when a connection is disconnected. Customer financial and analytical data is purged within the published deletion window, normally 30 days, after an organization-wide or connection-specific deletion request or termination. Audit records may be retained for the applicable contractual window, normally at least one year. A legal hold or other legal retention duty may delay deletion for the affected scope; backups expire on their normal schedule.
8. Your choices
Organization Owners can manage connections, request deletion, and control who has access through the organization identity provider. You can stop a provider sync by disconnecting its connection. If you need to correct account information or exercise a privacy right, contact the Spendclose support contact provided by your organization administrator or commercial agreement.
9. Changes to this policy
We may update this policy when the service or its data practices change. The effective date at the top of this page identifies the current version. Material changes should be reviewed by an authorized organization administrator.