Privacy

You can browse madebysidequest.com without an account. The site uses first-party aggregate counters to understand visits to all public pages, including support, legal, and purchase-return pages. It also counts selections of download and checkout buttons and the start of a successful response from a stable SideQuest app download URL.

These counters are totals for each UTC day. They do not use cookies, advertising identifiers, fingerprints, or cross-session identity. The current browser tab can keep only fixed source and campaign labels in session storage so later pages in that tab use the same attribution. That storage closes with the browser tab.

The daily counters record a fixed source category, a fixed campaign category when present, the Cloudflare country code, and the first browser language reduced to a fixed language category. SideQuest does not put IP addresses, full referrers, raw query strings, full language headers, email addresses, order details, licence details, or visitor identifiers in the analytics database.

The site also reduces bounded browser request headers to a fixed browser-family, operating-system, and device-type category. Each category is stored as a separate daily total. SideQuest does not store raw user-agent or client-hint headers in the analytics database. The action records described below combine reduced categories for each action.

The site also reduces a referring website or fixed campaign source to a provider-level traffic-origin category, such as a known search engine, social network, launch site, or partner. SideQuest does not store the referrer URL, path, query string, or a free-form source value. Traffic-origin totals stay separate from country, language, and device totals. Fixed source and promotion labels are also counted with the product action they accompany.

A successful stable download response is also counted by its product, a fixed route-source category, and whether it was a full response or the initial byte range. Route-source categories distinguish a site download button, an automatic or retried purchase-page download, a direct request, and an operational verification. The database does not store the download URL, query string, byte range, or request headers.

Registered promotion labels identify a product, channel, video slot, and link placement. The site counts product-page opens, button selections, successful stable download responses, failed download responses, and purchase-return pages with these fixed labels. A label can be kept in the current tab for up to 24 hours of inactivity and added to download and Stripe checkout links. It is shared by everyone using that promotion, not a visitor identifier. New externally tagged visits replace the previous label. Unknown labels are reduced to a fixed category. Update-feed checks and starts of versioned full or delta updates are counted separately by product and whether the client identifies itself as Sparkle. The site also counts accepted, rejected, and verification analytics requests. On a Mac, a supported browser may provide its architecture as ARM or x86; unavailable or declined values stay unknown. This is a separate aggregate counter, not combined with product, campaign, country, language, or other environment categories. Raw hints are not stored.

To understand which product actions come from which sources and devices, SideQuest also keeps individual page, download-button, checkout-button, purchase-return, and stable-download response records for the current UTC day and the previous 89 days. Each record contains its server receipt time, a fixed page and product label, action, source or registered promotion, button placement, country, approximate region and city supplied by Cloudflare, language category, operating system, device type, browser family and major version, and a known-bot or verification classification when available. Download records also contain a fixed route-source label, response type, and HTTP status. Network location can be wrong or unavailable. A random identifier identifies one action for duplicate suppression; it does not identify a visitor or link separate actions. These records contain no IP addresses, raw headers, full URLs, contact details, or persistent visitor identifiers. They are available only through the private studio dashboard and are removed automatically after this retention window. Requests with Global Privacy Control or Do Not Track set to 1 do not produce these individual records; the aggregate counters above can still operate. The site does not record sessions, screen contents, keystrokes, or activity inside an installed app.

A counter is a request or action signal. It is not a count of unique people, completed downloads, purchases, or app activations. A visit to a purchase-return page does not prove that payment or licence delivery succeeded. Daily totals are kept for the current UTC month and the previous 12 calendar months. Older daily totals can be combined into monthly totals. Totals older than the previous 24 completed UTC months are deleted. Analytics write failures are discarded and do not block pages, checkout links, or downloads.

The infrastructure that serves the site may process standard request information, such as an IP address, browser details, requested pages, and timestamps, to deliver and protect the site.

When you use the support form, SideQuest receives the topic you choose, an optional app name, your email address, and your message. Cloudflare runs the form endpoint and Resend delivers the request to our support inbox.

We use this information to answer and manage your request, resolve purchase or delivery problems, and maintain necessary support records. Support correspondence is kept only as long as it is needed for those purposes or to meet legal obligations. Do not send full card details or licence keys through the form.

SideQuest does not collect card details on this website. When you buy an app, its official product site sends you to a Stripe-hosted checkout. Stripe processes the payment and billing information needed to complete the transaction under its own privacy terms.

Stripe makes purchase information available to SideQuest so we can fulfil and support the order. That information may include your email address, transaction identifiers, the product purchased, payment status, amount, currency, and applicable tax details. SideQuest does not receive your full card number. A fixed promotion label may accompany the checkout. Each product can keep that label with its purchase record to count paid checkouts and licence delivery without duplicating webhook notifications. Only daily aggregate totals, not customer or transaction identifiers, are sent to the private studio dashboard.

For apps that use licence keys, SideQuest may store the purchase record, email address, signed licence key, and entitlement dates. We use that information to deliver the licence, prevent duplicate fulfilment, recover a key when requested, provide support, and keep required accounting records.

We use service providers to host purchase records and send transactional email. These providers, including Stripe, may process information outside your country, where it may be subject to local law. Each app's own privacy page describes any app-specific data handling.

We do not sell personal information or use a purchase email for marketing without separate consent. We share information only with providers needed to operate checkout, fulfil purchases, deliver email, support customers, prevent fraud, and meet legal obligations.

We keep information only as long as it is needed for those purposes. Some purchase, tax, fraud-prevention, and accounting records may need to be retained after a deletion request.

To ask what personal information SideQuest holds about you, request a correction or deletion, or raise a privacy concern, use our support page. Include the relevant app and purchase email when needed, without sending unnecessary details.

If this policy changes, the updated version will be posted here with a new effective date.