Privacy Policy

• Early Access and audit request details, including name, work email, company, optional website, portfolio size, current tools, biggest pain, feedback-call preference, and optional notes.
• Account and authentication information, including email address, OTP challenge records, session records, and basic security metadata needed to protect sign-in.
• Organization and site records created inside Portaviq, including organization names, WordPress site names, site URLs, optional wp-admin URLs, status, and setup timestamps.

• Verification and heartbeat data, including site public ID, site URL, plugin version, WordPress version, PHP version, active theme if available, timestamp, and signature.
• Lightweight pageview activity, including page URL/path, page title, referrer, occurrence time, and basic technical request metadata such as user agent.
• Portaviq strips query strings and URL fragments from stored pageview URLs and referrers.

• For Early Access requests, account access, support, security, and product operations, Portaviq generally acts as an independent controller.
• For organization records, site records, heartbeat, and pageview activity submitted by customers for connected WordPress sites, Portaviq generally acts as a processor or service provider on customer instructions.
• Portaviq may rely on contract, legitimate interests, consent where required, and legal obligations as practical lawful bases depending on the data and region.
• Customers are responsible for confirming their own lawful basis and privacy notice before enabling tracking on client or visitor-facing sites.

• You may contact Portaviq to request access, correction, deletion, or export of personal information connected to your account or Early Access request.
• Where applicable, you may object to or restrict certain processing.
• Where processing depends on consent, you may withdraw that consent for future processing.
• EU and UK individuals may also have the right to complain to their local data protection authority.

Do not share OTP codes, session cookies, verification tokens, tracking secrets, or private credentials with Portaviq support. A Portaviq support request should never require your one-time sign-in code or WordPress password.

Early Access requests

Kept while reviewing fit and during a reasonable Early Access follow-up period, unless deletion is requested earlier.

Account and session data

Kept while the account is active, with OTP and expired session records cleaned up on a shorter operational schedule where practical.

Organization and site data

Kept while the customer account or workspace is active, or until the user deletes the organization/site or requests deletion.

Heartbeat and pageview data

Kept for Early Access visibility and product debugging. A stricter production retention schedule should be finalized before broad launch.

Provider details are listed on the subprocessors page. If data is processed outside your country or region, Portaviq should rely on appropriate contractual and provider safeguards for the active deployment.

Include the email address connected to your request or account. Do not include OTP codes, verification tokens, tracking secrets, passwords, or private credentials.