Privacy Policy
Last updated: 2026-11-07
1. Scope and contact
This Privacy Policy explains how personal information is handled across all Cachely services and all present or future plans, including separately contracted plans, when you visit our websites, sign in to the dashboard, use the managed build-cache Service, manage a subscription, or contact us. In this Policy, "Cachely," "we," "us," and "our" refer to the operator providing the Service under the Cachely brand. Cachely is an independently operated, founder-led service and is not an incorporated company. For privacy questions and requests, email hello@cachely.dev.
Cachely can handle different types of information in different roles. For account administration, website analytics, communication, billing reconciliation, security, and some operational analytics, Cachely generally determines the purposes and means of processing. When an organization directs Cachely to store or process personal information in the build artifacts that it uploads, Cachely may act as a processor/service provider on the organization's behalf, where applicable law uses those concepts. Roles depend on the actual data and activity. This Policy does not itself constitute a data-processing agreement. If your intended processing requires additional binding processor terms under applicable data-protection law, those terms must be agreed before the relevant processing begins. Contact hello@cachely.dev before submitting the relevant personal information.
2. What information we handle
Account, access, and membership information. When you sign in with Google or GitHub, we receive information such as your email address, display name, and the provider's user identifier. We do not obtain your Google or GitHub account password, and signing in does not give us permission to clone or browse your source-code repositories. We maintain account settings, memberships, invitations, role grants, workspaces, API-token records and access-related history needed to provide the Service. For interactive sign-ins after the applicable Terms are published, we record the Terms version, authenticated user ID, and server timestamps as acceptance evidence. This is separate from optional analytics consent. We do not need to retain the full secret value of an API token after issuing it. Welcome and invitation emails may include a restricted internal administrative copy to support account operations.
Customer-provided cache data. Your configured build tools and CI systems send cache keys, hashes, artifacts, task outputs, file paths, and related metadata. Depending on what you configure, uploaded outputs may contain source-derived files, personal information, confidential materials, or credentials. Cachely does not independently clone or scan your repository; it receives the content your chosen build workflow uploads.
Operations and Insights. We record cache operations (including reads, writes, hits and misses), timestamps, artifact sizes and identifiers, workspace and token references, task labels, quota usage, diagnostics, and derived classifications. We use these to deliver customer-facing Insights, understand usage, calculate plan limits, troubleshoot the Service, and detect misuse. Some historical Insights remain associated with your account even after you delete a workspace.
Subscriptions and payment administration. For purchases through Dodo Payments, we receive limited information required to connect the payment to the correct account and manage access, such as the selected plan and billing period, billing customer or subscription reference, payment or subscription status, and related technical confirmations. Dodo Payments, our Merchant of Record, manages buyer checkout, payment-card collection, invoices, transaction taxes, refunds and payment disputes under its own terms. Cachely does not receive or store your full payment-card number. Dodo independently determines how it processes certain buyer/payment information as a separate provider.
Contact, feedback, and research. We receive the name, email address, company details, message, and other fields you voluntarily submit in a contact form, email, feedback request, or product research form. Certain compatibility or integration forms also ask for build-tool versions, current solutions, technical blockers, approximate team size, level of interest, and limited page or referral context. Submissions may be delivered to an internal mailbox for response and product evaluation. Submitting a form does not automatically subscribe you to marketing messages.
Technical, security, and website information. Our infrastructure providers may process IP addresses, user agents, request URLs, timestamps, response statuses, error reports, and other technical data required to deliver pages and API requests, prevent abuse, and diagnose faults. We also collect the website analytics information described below.
Is providing information required? Creating and using a Cachely account requires certain information, including a sign-in identity and an email address associated with a supported sign-in provider. Without that information, we cannot provide authenticated account access. An undeliverable address may prevent you from receiving important account, service, or legal communications. Build-cache uploads, optional forms, research responses, and marketing analytics consent are otherwise voluntary; if you choose not to upload artifacts, the corresponding remote-cache functionality cannot operate. You can decline optional analytics without losing access to the Service. We do not require you to provide additional personal information merely to browse the public website.
3. Purposes and legal grounds
We use the information above to:
- Provide Cachely: authenticate people and services, authorize workspaces, receive and return artifacts, enforce Plan limits, and display account Insights.
- Operate and protect the Service: detect abuse, investigate incidents, maintain reliability, troubleshoot technical errors, and respond to legitimate support requests.
- Manage paid access: reconcile subscription events and help customers find billing, refund, or cancellation processes managed by our payment provider.
- Communicate with users: provide account-related notices, answer questions, handle feedback, and assess voluntary feature requests.
- Understand product performance: use operational measurements and appropriately aggregated, non-identifying information to maintain and improve Cachely.
- Meet legal duties: respond to lawful requests and retain records that applicable law requires.
- Measure optional marketing activity: use Google Analytics 4 only after the visitor makes an affirmative analytics-consent choice where required.
Where GDPR or similar legal frameworks apply and Cachely acts as a controller, the legal ground depends on the particular activity: performance of our agreement, legitimate interests in providing and securing the Service, compliance with legal obligations, or consent for optional analytics. Where Cachely acts as a processor for content supplied on a customer's behalf, the customer's lawful basis and documented instructions govern that processing, subject to applicable law and any required processor terms agreed before the relevant processing begins.
4. Automated artifact inspection and human access
Cachely's systems may automatically inspect limited artifact structure, file paths, cache metadata, and prefixes of task output to identify build tools, projects, tasks, file counts, durations, size classifications, and other Insights shown to authorized account users.
We protect managed artifacts using HTTPS/TLS in transit, provider-managed encryption at rest, and scoped access controls, including workspace-scoped, revocable API tokens. Authorized operational access to relevant information may be possible when reasonably needed for support, incident response, security, abuse prevention, or correcting incorrect classification. We aim to limit any such access to the minimum needed.
We do not sell personal data, provide customer-specific artifacts or Insights to advertisers or data brokers, use them to train AI models, publish them for competitive research, or intentionally expose one customer's data to another. We do not independently browse your source repository.
Where legally permitted and consistent with applicable customer instructions, Cachely may in the future develop and make available technical benchmarks, performance comparisons, and optimization recommendations based on aggregated and appropriately anonymized technical information. Such outputs must not disclose identifiable customer configurations, confidential content, or personal information. This reserves a possible future use; it does not describe a feature currently offered.
5. Providers and disclosures
We use the following providers for the corresponding functions:
- Cloudflare: hosting and delivery of the Service, Workers, managed R2 object storage, D1 data storage, network security, supporting email delivery, and Cloudflare Web Analytics.
- Google: Google sign-in, if selected, and optional Google Analytics 4 measurement when enabled by consent.
- GitHub: GitHub sign-in, if selected, without general repository permissions for Cachely sign-in.
- Dodo Payments: checkout, payment processing as Merchant of Record, subscription management, invoices, indirect transaction taxes, refund handling, fraud controls, and payment disputes.
Providers do not all have the same privacy role. Cloudflare may process data on Cachely's behalf, while a sign-in provider or Dodo may act independently for some of its activities. We share information as reasonably necessary for the chosen function, subject to applicable law and provider terms. We may also disclose information if reasonably necessary to investigate misuse, enforce rights, comply with lawful requests, or protect the Service and its users.
Our providers may process information in multiple countries, including outside the country where you live. Depending on the service and the applicable law, international data transfers may require contractual or other safeguards. Contact us at hello@cachely.dev for more information about processing locations and applicable safeguards.
6. Website and dashboard analytics
We use Cloudflare Web Analytics to understand aggregate traffic, referral sources, and page performance. It is intended to operate without analytics cookies or visitor fingerprinting.
Google Analytics 4 (GA4) is optional. It is loaded only after the applicable analytics consent is granted. When enabled, it may receive sanitized page URLs and titles, referrers, broad device/browser information, selected calls-to-action and form events, and limited signup or first-cache-hit attribution events from the dashboard. We exclude dashboard paths and OAuth parameters from these events. We do not intentionally send account IDs, workspace IDs, email addresses, free-text contact responses, or cache artifact contents to GA4. Optional compatibility-form analytics may include technical version and categorical answers, but not contact details.
First-party signup attribution. Separately from GA4, when you follow a marketing signup link we may carry a call-to-action label, landing-page path and referring hostname into the signup flow. If you create an account, we store those values and a first-seen timestamp with your account to understand which pages lead to signups. This collection does not depend on your optional GA4 choice. We store the referring hostname rather than the full referring URL or query string, and do not add your network IP address or user agent to this record. It is not sent to GA4 as an account identifier. It remains with the account until removed through the account-erasure process.
You can allow, reject, or later change your consent through the Privacy Policy or the website's available analytics controls. Consent is not required for basic use of the Service.
7. How long information remains
We use different retention periods for different types of information:
- Managed cache files: Currently subject to a storage-lifecycle policy of approximately 20 days after upload. Later uploads of the same or equivalent output may start another period. Cached data is not guaranteed to remain retrievable for that full period.
- Workspace deletion: An authorized owner can delete a workspace. Its tokens are revoked and its managed cache files enter a deletion process that may run in multiple batches and need to be resumed after interruption. Deleting the workspace does not remove historical account-level Insights or automatically close the account.
- Operational events, task metadata, and Insights: May remain while the corresponding Cachely account exists, including for workspaces that have been deleted. This preserves customer-visible history and supports operational analysis. See the deletion rights below.
- Account and membership records: Normally kept while the account is open, with limited exceptions where law or security needs require retention afterward.
- Integration-request database records: A scheduled cleanup removes records at least 24 months old. This cleanup does not remove emailed copies. Other contact correspondence and compatibility-research submissions do not currently have the same automated deletion schedule. You can request their deletion using the contact details below, subject to applicable retention obligations.
- Infrastructure and security logs: Retention depends on the log type and provider settings. We do not specify a single verified retention period for all such logs; contact us for information about a particular processing activity.
- Billing records: Dodo and Cachely may retain the distinct records they are legally required to keep, even after an account closes.
- Backups and replicas: Deletion may not immediately remove every transient or protected copy; remaining copies are subject to their relevant lifecycle and lawful retention requirements. We cannot promise that all such copies are removed at the same time as active records.
We will not describe deletion of a workspace as full erasure of all account-related data.
8. Account deletion and privacy requests
You may ask us to delete your account and associated personal information, including applicable Insights, by emailing hello@cachely.dev from the address associated with the account. We may request reasonable verification to protect account owners and other users. At present, account-wide erasure is handled as a support-assisted request, not as a one-click action in the dashboard. We respond to verified requests within the deadlines required by applicable law and explain any lawful retention exceptions or permitted extension. Removing active records and expiry of remaining provider copies may occur at different times, subject to those legal requirements.
If you want to keep your account but request removal of particular personal information or retained historical Insights, contact us with enough detail to identify the information. We will assess the request under applicable law and technical capabilities. The request is not automatically fulfilled by deleting the workspace.
Depending on your location and the circumstances, you may have rights to access, correct, obtain a copy of, restrict processing of, object to certain processing of, or request deletion of personal information, to withdraw consent where applicable, and to complain to a relevant supervisory authority. We may direct a request concerning personal information contained in an organization's uploaded materials to that organization where it is the controller.
9. Security and responsible use
We use HTTPS/TLS, provider-managed encryption at rest, workspace-scoped and revocable API tokens, and access controls to protect the Service. These measures reduce risk but do not provide an absolute security guarantee. Please keep secrets out of build outputs where practicable, configure CI credentials by trust level, and report suspected security issues to hello@cachely.dev. We do not claim a certification such as SOC 2 unless and until it has been obtained.
10. Children
Cachely accounts are for people 18 years of age or older. We do not knowingly permit anyone under 18 to register for or use an account. Customer-uploaded build outputs may nevertheless contain personal information about other individuals, including minors, depending on the customer's configuration; that information is handled as described in this Policy. If you believe a minor has registered for an account, contact us.
11. Changes to this Policy
We may revise this Policy to reflect changes to our products, providers, or processing practices. We will update its effective date and, where required, give additional notice or request consent before a material change takes effect.
Privacy contact: hello@cachely.dev.