1. Controller and contact
The site is operated by Karolina Dopierała, ul. Kubusia Puchatka 14/10, 05-800 PRUSZKOW, POLAND. Privacy questions may be sent to hello@profitperorder.com.
2. Calculator inputs
Calculator inputs are sent to the application server to produce a result. They are not associated with a user account. The application records an aggregate calculation event without storing the submitted financial values in the event table.
3. Paid reports
When a paid report is requested, the application stores a random private token, calculator identifier, submitted inputs, deterministic results, payment status and generated report. Stripe processes checkout and payment data under its own privacy terms. This application does not receive full card numbers. The customer email returned by Stripe is stored to deliver and, when necessary, resend the private report link and to handle purchase support.
4. OpenAI
When OpenAI reporting is enabled, calculator inputs and deterministic results are sent server-side to generate structured narrative. The integration requests that the response not be stored by the API. Do not submit personal data or customer records in calculator fields.
5. Logs, local operational metrics and internal traffic
The server may process IP address and user-agent data transiently for security and operational logs. The built-in business-event table records aggregate product actions such as completed calculations, checkout starts and outbound partner clicks. It also records a privacy-light server-side landing event for public HTML page entries so paid acquisition can be reconciled even when browser analytics is blocked. That landing event stores the landing path, external referrer host, standard UTM values, a coarse traffic channel and only boolean flags indicating whether a Google or Microsoft Ads click marker was present; it does not persist the raw IP address, raw user-agent, user-agent hash or raw advertising click identifier. Obvious automated crawlers and prefetches are filtered before this landing event is written. It does not store city or country. An authenticated administrator browser can receive a signed first-party cookie so its future test activity is marked as internal and excluded from the default business dashboard. Historical records are retained in an archive view rather than deleted when a new clean metrics period begins.
6. Analytics, Google Ads tag and campaign attribution
The Google tag initializes on page load using Advanced Consent Mode. Analytics storage is granted by default outside the European Economic Area, the United Kingdom and Switzerland unless a visitor has previously opted out. In the EEA, UK and Switzerland, analytics storage is denied by default until a visitor explicitly allows it; while storage is denied, Google tags may send cookieless measurement and consent pings. Advertising storage, advertising user data and ad personalization remain denied everywhere, and Google Signals remains disabled. Google Analytics 4 is used to understand page usage, calculator completion, affiliate clicks, checkout starts and completed purchases. Purchase events use a Stripe Checkout Session identifier and do not include card data or the customer's email address. After Stripe verifies a paid Profit Action Report, the site also sends the configured Google Ads purchase conversion using the verified transaction value, currency and Checkout Session identifier. Private report tokens, payment-preview tokens and calculator input query parameters are removed from Analytics page URLs. A visitor can change the Analytics storage preference through “Privacy settings”; choosing Essential only denies Analytics storage and removes first-party Analytics cookies. When Analytics storage is explicitly allowed, the site may also keep a short first-party attribution record containing standard UTM source, medium, campaign and content values plus the landing path, so local aggregate metrics can connect a campaign to calculator and checkout events. Declining or revoking Analytics storage does not restrict the site.
7. Optional affiliate measurement and preference storage
After the same explicit choice, the site may load the Impact.com Publisher Tag. It may transform eligible direct partner links and measure impressions or attributed journeys. The site does not use the identifyUser function and does not send a visitor name, email address or account identifier to Impact.com. The preference is stored locally in the browser and can be changed through “Privacy settings” in the footer.
8. Transactional email and confirmed subscriptions
When enabled, Resend processes the recipient address and message content as a service provider. Transactional messages deliver purchased report links and operational purchase notices. Separately, a visitor may explicitly request the free Profit Per Order email sprint. That subscription uses double opt-in: no lifecycle or marketing message is queued until the confirmation link is used. The application stores the email address, optional first name, consent wording and version, source, timestamps, a one-way IP hash, attribution fields where optional measurement was allowed, delivery status and suppression reason. Every marketing message contains an unsubscribe route. Unsubscribe actions cancel pending marketing jobs locally. Resend automatically suppresses recipients after hard bounces or complaints; when a signed Resend webhook is available, the application also mirrors those events into its local subscriber state. Publicly listed or scraped addresses are not imported into this system.
9. Automated operations and OpenAI
Scheduled jobs may aggregate local, privacy-light funnel metrics, choose a deterministic bottleneck category and prepare an owner summary. When OpenAI is enabled for this purpose, the integration receives aggregate counts and published content metadata, not subscriber email addresses or raw calculator inputs. A deterministic fallback is used if the API is unavailable.
10. Cookies, payments and advertising
The calculators do not require an account cookie. The site can use essential security storage, an administrator-only internal-traffic cookie, optional consent and attribution storage, and Stripe storage needed for hosted checkout. A Google Ads base tag is present for measurement readiness, but advertising storage, advertising user data and ad personalization are denied in the current implementation. Personalized advertising and display advertising are not enabled in the current launch plan.
11. Retention and rights
Data is retained only for the period needed to deliver the service, resend purchased reports, handle payments, secure the site, measure performance, meet legal obligations and resolve disputes, according to the operator's documented retention schedule. Depending on applicable law, a person may have rights of access, correction, deletion, restriction, objection, portability and complaint to a supervisory authority. Requests may be sent to the contact address above.