Known providers and service boundaries
This is the known provider inventory, not a claim that every service is a processor in every context. A customer-specific subprocessor list must be completed and agreed before processing customer personal data.
| Provider | Purpose and information | Status |
|---|---|---|
| Microsoft Azure | Website notification relay on Azure App Service in East US. Enquiry content is processed to send email; persistent relay records contain request IDs and delivery status. Application telemetry uses Azure monitoring. Other customer records depend on the agreed deployment. | Primary region: East US, United States. Exact services, backups, contracting entity and processing terms require confirmation. |
| OpenAI Sites / Cloudflare infrastructure | Deliver this public website, handle network requests, and store buyer requests, enquiries, payment requests, coupon rules, and referral attribution in Cloudflare D1. | Visible preview hosting. Exact contracting chain, log retention and geographic processing require confirmation. |
| Hostinger Email | Receive website buyer requests and enquiries in our business mailbox, including the contact and company details submitted. | Connected through encrypted SMTP. Mailbox storage region, backup retention and contractual transfer safeguards require confirmation. |
| Cal.com | Optional embedded scheduler and direct booking destination. Technical connection information and booking details entered there. | Enabled after a visitor’s choice. Privacy notice ↗ · Provider trust information ↗. |
| AI, outbound email, CRM, call recording and other customer integrations | Depends on the contracted campaign and customer configuration. | Names, purposes, locations and contractual terms have not been confirmed for this register. No claim of an approved complete vendor list. |
Review before processing
The customer’s processing agreement must address authorization of subprocessors, advance notice of changes, an opportunity to object, equivalent data-protection obligations, and responsibility for their processing. This page does not itself authorize a new subprocessor.
Request the current customer-specific register. Include your company and the service you are evaluating; do not attach a customer dataset.
Payments, coupons, and referrals
Payment requests, customer name, email, phone, agreed prices, status, coupon rules, and referral attribution are stored in this website's Cloudflare D1 database, separate from the Azure customer environment. The exact D1 location, backup retention, and processing terms require confirmation. Self-service purchases also store your selected plan and confirmation of its purchase details. A salted IP digest and hourly request count help limit misuse; purchase counters are removed during later purchases after their roughly 24-hour window. Separate short-lived API counters expire within ten minutes and are cleared during later API calls. Only salted digests are stored for these counters, not raw IP addresses. When checkout is prepared, necessary customer and payment details are sent to Cashfree Payments.
Card details are entered on Cashfree's hosted checkout and are not collected by this website. We process payment records to administer your requested transaction and contract, prevent misuse, and meet applicable accounting duties. Referral codes can identify a referrer by email; they do not subscribe either person to marketing or send commissions.
Live requests collect real payments through Cashfree. Sandbox requests, when enabled, are clearly labeled and collect no real money. The ordinary two-year retention policy is subject to applicable accounting duties. Automated payment-record deletion and backup expiry are not yet verified; deletion requests are reviewed manually. Cashfree's own processing locations, retention, and contractual safeguards are governed by its own terms and privacy notice. Cashfree privacy notice ↗.