Spache

Information we collect

When you create an account, Firebase Authentication provides us with account identifiers and details such as your email address and display name. We also store the site settings you provide, including site names, origin URLs, connected domains, preview settings, render options, and cache or capture configuration.

When you use Spache, we process service and diagnostic information such as request paths, methods, status codes, timestamps, response sizes, cache outcomes, render and validation durations, and route activity. Infrastructure providers may also process IP addresses, user-agent details, and other request metadata in their logs.

If you contact support, we receive the information you include in your message.

Website content Spache processes

To render and serve a connected site, Spache fetches pages and related responses from the origin you configure. We store rendered HTML and may store screenshots, response metadata, and API response bodies used by configured capture or replay features. A site’s cache settings control when content is considered stale and refreshed; they do not guarantee physical deletion of older stored copies. Clearing a cache or removing a site stops Spache from serving the associated current cache, but older files may remain in storage. Spache does not currently promise a fixed deletion deadline for every old render-cache object. Other copies may also persist briefly in logs, backups, or distributed systems while cleanup completes.

Spache renders pages without a visitor’s signed-in session. However, a public origin or API can still return personal or confidential information, and a configured capture can store a response. Do not connect private or authenticated content unless you have reviewed the configuration and have a lawful basis to do so. Requests containing non-empty authorization or cookie headers are not fulfilled from captured-response replay; they are sent to the origin instead.

Some route screenshots can be made public by the site owner. Anyone with the public screenshot URL can view that image while it is available.

Pricing estimate requests

When someone requests a public pricing estimate, we render the submitted root domain. We retain an internal record of each valid check, including the domain, check time, result, and render measurements, indefinitely. The generated estimate and screenshot are cached for 24 hours and may then be rendered again on a later check.

How we use information

We use information to provide rendering, caching, proxying, account and site management, usage measurement, billing where enabled, customer support, security, abuse prevention, troubleshooting, and service improvement. We may also use operational records to investigate incidents or comply with legal obligations.

Service providers and sharing

Spache uses Google Cloud and Firebase for hosting, databases, storage, authentication, and operations. If billing is enabled, Paddle processes checkout and payment information under its own privacy terms; Spache does not receive or store full payment-card numbers. We also send requests to the website origins you configure. These providers process information as needed to provide their services and may process it in locations where they operate.

We do not sell personal information. We may disclose information if required by law, to protect users or the service, or as part of a business transfer.

Retention and deletion

Account and site configuration is retained while needed to operate your account. Active rendered content follows its cache settings. Route screenshot files are scheduled for deletion after 30 days, though deletion may not happen immediately. Old rendered HTML objects do not currently have a guaranteed deletion deadline. Usage records, security logs, and billing records may be kept longer for service operation, accounting, security, or legal purposes; pricing-estimate check history is currently retained indefinitely.

You can remove a site in the app or clear its cache. To request account or personal-information deletion, email info@spache.online from the address associated with your account. We will handle requests subject to applicable law and records we need to retain. Deletion from backups and distributed systems may take additional time.

Your choices and security

Keep your account details accurate, choose public origins carefully, and avoid putting secrets or personal data in URLs or content that Spache may render, log, cache, or serve. Use the site’s cache and capture settings to control what Spache stores or replays. We use access controls and service safeguards, but no online service can guarantee absolute security.

Depending on where you live, privacy laws may give you rights to access, correct, or request deletion of personal information. Contact us and we will respond as required by applicable law.

Changes to this policy

We may update this policy as Spache changes. We will update the date above and, where appropriate, notify account holders of material changes.