Privacy overview

Work-email accounts and account data

ZoKorp accounts are intended for business use. Registration, sign-in, and customer support flows are built around work-email accounts rather than personal inbox domains.

The platform stores the minimum account data needed to operate the service, including your business email, verification state, password-auth credentials, billing linkage, service requests, and core audit or usage events.

Security-related account events such as verification requests, password resets, sign-in attempts, and billing changes may be logged so ZoKorp can operate the platform safely.

Tool submissions, results, and account history

ZoKorp tries to keep detailed diagnostic payload retention narrow by default. Tool inputs are processed to generate the result, then detailed submission content is minimized or scrubbed from the normal workflow when the job is complete.

What does remain by default is the operational history needed to support the customer account: tool name, run timestamp, delivery state, broad score or estimate bands, purchases, credits, entitlements, and supportable audit trails.

Architecture review results, Validator runs, forecasting runs, and service requests may appear in account history even when the full uploaded source material is not retained long term.

Optional archival, booked calls, and follow-up storage

Some workflows offer explicit follow-up options such as saving a submission for later review, allowing CRM follow-up, or booking a consultation. Those paths store more operational context than the default no-follow-up path because ZoKorp needs enough information to continue the conversation responsibly.

Architecture review archival is opt-in. If you do not choose follow-up archival, ZoKorp is designed not to keep the detailed diagram narrative, OCR text, or report JSON as a long-term customer record after delivery processing finishes.

Short-lived duplicate protection may store a submission fingerprint hash for a brief period to prevent accidental duplicate sends. This is used for operational safety, not for profiling or marketing.

Email preferences, CRM, and service providers

ZoKorp uses hosted providers for application hosting, database access, authentication, billing, email delivery, scheduling, and optional follow-up workflows. Stripe handles billing workflows, and ZoKorp does not operate a custom credit-card storage system inside the app.

Operational result delivery and future marketing or CRM follow-up are treated separately. Signed-in users can manage email preference controls, and optional CRM follow-up remains an explicit submission-level choice instead of a silent default.

When you choose a workflow that needs a provider, such as Stripe billing, booked-call scheduling, or optional archival or CRM follow-up, the minimum data needed for that workflow may be shared with the relevant provider to complete the requested operation.

Forecasting beta and current platform scope

ZoKorp Forecasting Beta is a narrow forecasting workflow, not a broad MLOps data platform. Uploaded forecasting files are processed to produce the result and supporting audit metadata, but the current launch is not designed as a long-term persistent training-data warehouse.

Live data connectors, broad persistent dataset storage, and general-purpose MLOps claims are intentionally out of scope for the current launch.

Retention enforcement and contact

ZoKorp runs scheduled cleanup to delete expired archives, remove duplicate-protection fingerprints, and scrub sensitive records that should not remain in storage beyond their intended operational window.

Questions about privacy, retention, or data handling can be sent to consulting@zokorp.com.