Your facts.
A defined purpose.
Contact & controller
Write to stratafinancial@pm.me. The controller is EOTM Inc. Its business address is listed in the legal notice. This notice does not certify complete compliance or claim that a particular data-processing agreement or transfer safeguard has been verified.
New setup requests: Tally and Google Sheets
The free request form is provided by Tally. The short request asks for your name, email, current country of residence, activity type and main objective, with an optional package preference and a required acknowledgement of the free human-review request. Approved attribution fields record the source page path, entry CTA, original package ID and campaign tags. STRATA uses the responses in Tally, the connected Google Sheets reception table and a separate manual follow-up table to handle your request. No new subscription or payment starts when you submit.
Tally is configured to send owner alerts to STRATA. A person reviews your details and sends your next step by email. A default Needs review status is an intake label, not an automated eligibility or tax verdict. Your consent covers this request and its follow-up, not marketing subscription.
The embedded form loads content from Tally. Its always-visible link lets you open the same form directly. The form uses Tally’s own service; Tally and Google process the data submitted through their products. Tally publishes its privacy policy and data-processing terms. Google publishes its privacy policy and Workspace service terms. The Google account type, any applicable data-processing agreement, configured data regions and international transfer safeguards depend on the arrangements used. This notice does not assert that STRATA has independently verified those account-specific arrangements or that all data stays in one country.
Older requests and client records: Cloudflare
The earlier /tax-fit, /start, contact, estimate and client workflows remain available for existing links and records. Requests submitted through those workflows are stored in the Cloudflare-hosted database. Operator access is authenticated. Existing client access matches the signed-in email. A separate, hashed edit token protects an estimate when it becomes a full application.
Those requests may contain your name, email, tax residence, physical working location, activity, ownership, client locations, current structure, selected form and package, requested support, optional message, screening details and catalogue snapshot. Earlier estimate and client workflows may contain additional information you provided. Existing case, payment and contract records retain their separate handling and agreed terms.
Older browser drafts and saved summaries
The earlier Tax-Fit Check and four-step start flow save unsent answers in sessionStorage in this browser tab for up to 24 hours. You can clear the draft. Contact drafts are temporary and cleared after successful submission. No identity documents or payment card data are stored there. A saved legacy request records the answers, contact details, selected package, requested additional services, accounting preference, optional service context, screening reasons, score and catalogue version. A hashed request token protects reservation access. These browser drafts are separate from the Tally request form.
Aggregate measurement
Cookie-free aggregate measurement is on by default. You can turn it off with the Aggregate analytics control below. Do Not Track and Global Privacy Control disable browser measurement. Daily counters accept predefined events, variant and step, with optional fixed categories for screen size, section, package and campaign source/medium. Unknown campaign sources and mediums become “other”; free-text campaign names and full URLs are not collected for analytics. Counters are grouped by a server-generated UTC day, not an individual event timestamp. They contain no form answers, contact details, raw attribution payloads, IP addresses, visitor or session identifiers. They cannot reconstruct an individual visitor journey. Clicks on email, cost-breakdown and sample-handover links, FAQ openings and scroll thresholds are action counts, not evidence of delivery, reading or qualification. When the active embedded form reports a load or successful submission, only the corresponding aggregate event is counted. Answers, submission IDs and respondent IDs are ignored for measurement. An external-form link click is counted as a click, not a submission. We do not measure the start of typing, and a Tally submission event does not confirm delivery to Sheets or email. Hosting logs are separate and may contain request information. The preference stays in memory and resets on reload. STRATA remains responsible for the applicable privacy basis for this measurement.
Documents and service handoff
Do not submit passports, bank statements, account numbers, passwords or other credentials through the brief, optional notes, email or chat. Before document collection, the agreed work must name the provider, secure channel and handling terms. No automatic bank submission, filing or provider introduction occurs.
Legacy transactional email requires a configured, verified sender before it works. If enabled, that email provider receives the contact and summary needed for the legacy confirmation or owner alert. New Tally owner alerts and human email replies are a separate workflow. No message is represented as delivered solely because a request was saved.
Retention and rights
Unconverted leads are reviewed manually for deletion after 90 days. This review must cover relevant responses in Tally, the Google Sheets reception table, the manual follow-up table and related email copies. It is not automatic deletion. Earlier unconverted Cloudflare requests remain subject to their manual deletion review. Contract, payment and accounting records have separate retention obligations; the applicable periods and aggregate-counter deletion schedule require owner confirmation.
Ask for access, correction, deletion or restriction at stratafinancial@pm.me, using your request or case reference where available. You may withdraw optional consent and complain to your relevant supervisory authority. Applicable contractual or legal obligations may limit deletion.