PikaPark Commerce Sync — Privacy Policy

Effective date: October 1, 2026

1. Who we are and what this policy covers

Shopvidi Inc. (“we,” “us” or “our”) owns and operates PikaPark Commerce Sync and its associated PIKA Park Control Center functionality (the “Application”). The Application is used exclusively by Shopvidi Inc.’s authorized employees and contractors for internal PIKA Park operations. This Policy describes information processed through that internal use.

This is separate from the PIKA Park storefront’s existing privacy policy and other store policies. Shopping on the storefront or visiting a Shopify-hosted page may involve separate Shopify and storefront processing. This Policy does not replace those notices.

2. Information processed

Clover. The current integration reads merchant information to verify the intended merchant and reads inventory items. Saved observations can include item identifiers, names, SKUs, item codes or barcodes, prices, quantities, hidden or deleted indicators, and modification times. It does not automatically save every field in the merchant response. The current Clover integration does not collect Clover customer records, orders or payment-card details. Available account permissions may be broader than the functions implemented.

Shopify. Depending on permissions and the operation, the Application reads store identity, domains, timezone, currency and access scopes; product descriptions, titles, handles, status, timestamps and media information; variants, SKUs, prices, locations and inventory; and catalog fields such as SEO information, vendor, product type, tags, options, collections and publication information.

Selected order information includes identifiers, timestamps, test and cancellation indicators, financial status, amounts received or refunded, currency, and line-item identifiers, product/variant references, SKUs and quantities. Order tags are used to identify process tests and removed from the ordinary stored order payload. Supported aggregate store-session information may be retrieved where available.

The fixed Shopify queries do not request customer names, email addresses, billing or shipping addresses, or payment-card numbers. Order identifiers and linked transaction data may nevertheless be personal information. Merchant-entered text and other fields may also contain personal information.

Public storefront information. The Application can retrieve public product pages and public product data to check identity, title, price, availability and observable page elements. It saves observations, URLs, response results, timestamps and content fingerprints. These checks do not submit forms or add products to a cart.

Operator-supplied information. Authorized users can provide names or labels, task inputs, approvals, notes, files, content, evidence references, manual external results and campaign measurements. Records may include order references, carrier/tracking information, fulfillment and delivery evidence, and references to approved follow-up messages and consent. Free-text information and files are not automatically anonymized.

Authentication and technical information. The Application processes credentials, access and refresh tokens, merchant/store identifiers and session information. It also records connection results, error codes, task output, request references and timestamps.

3. Purposes

Information is used to authenticate connections, verify the intended store, observe catalog and inventory changes, match products and variants, prepare supported metrics and content, recommend operational steps, obtain human decisions, record results and diagnose problems.

Workflow recommendations use deterministic rules. Model-assisted tasks are separate functions. Unavailable metrics are not automatically treated as zero, and approvals or generated artifacts are not proof of external business activity.

4. Storage and protection

Operational information is stored in databases and files on the computer or server used to operate the Application. Stored materials can include observations, tasks, approvals, evidence, history, metrics, content, images and execution logs. Information may exist in more than one record, file or backup.

Credentials are kept separately in private configuration or credential storage. Protection includes restricted credential-file permissions, authenticated operator controls, checks on request origin and merchant identity, and verified HTTPS connections to providers.

The Application does not itself encrypt its operational databases or Clover credential file at rest. A read-only check confirmed that FileVault disk encryption was enabled on the current operating Mac. This finding does not establish encryption of every exported file, backup or future host. Storage and backup protection depend on the environment used. Secret-pattern filtering is not comprehensive personal-information filtering, and no security measure guarantees protection against every risk.

5. Third-party processing

Clover and Shopify receive the authentication information required by their protocols and the parameters and identifiers needed for authorized requests. They return the requested store information. A separately enabled Shopify draft-product function can also send proposed product text, classification, collections, variants, SKUs, prices and settings. That function creates drafts; it does not publish them or set stock quantities.

Merakku image gateway receives authentication and request metadata for model-list checks. Such checks do not send prompts or images. If paid image editing is separately enabled and invoked, prompts, reference images, model identifiers and generation settings are transmitted. Reference materials can include product imagery, a logo and a style reference.

Codex and its configured model provider receive selected structured input when an authorized model-assisted task runs. This can include product facts, revision notes, product-page observations, measurements, policy information or campaign data. A task described as local can still use remote model processing. It is not a guarantee that information remains on the local computer.

ngrok carries OAuth traffic when the authorization tunnel is used. Callback requests can contain an authorization code and security state. Disabling request-content capture does not remove ngrok from the data path or establish that no provider metadata is retained.

Manual external recipients. Operators may separately send authorized task information to Tycoon or another approved recipient and record the result. There is no direct Tycoon API integration in the Application.

Providers may receive connection information such as IP addresses and request timing. Their processing is governed by the applicable service and account arrangements. This Policy does not promise that all providers retain no data, exclude all inputs from model training, or process information only in a particular country.

6. Cookies and tracking

The internal UI uses a session cookie for protected operator functions. Sessions have an eight-hour validity period and are invalidated when the service restarts. This is not a retention period for business records.

The current internal Application has no advertising pixels, cross-site advertising analytics or feature for selling personal information. It does not implement automated handling of Do Not Track or Global Privacy Control signals. This statement does not describe the separate tracking practices of the storefront or provider websites.

7. Retention and deletion

The Application does not currently enforce a general automatic retention or deletion schedule. Operational records, files and backups can remain until an authorized administrator reviews and handles them. A reporting window limits a particular data retrieval; it does not automatically remove earlier imports.

Some current observations are replaced, while other information is retained as history. Certain audit and evidence records cannot be removed through ordinary application operations. These technical restrictions do not, by themselves, exempt information from applicable privacy obligations.

Stopping use, disconnecting a provider, expiration of credentials or uninstalling the Application does not automatically delete previously stored information or provider copies. The Application has no self-service erasure workflow or automatic process covering all credentials, records and backups.

A deletion request requires administrative assessment of the affected information, any applicable retention obligation and copies held in files, backups or provider systems. Administrative procedures have been drafted for this work; category-specific retention periods and exceptions remain subject to approval and applicable obligations.

Isolated tests using synthetic data demonstrated limited minimization of a test record and associated file, preservation of audit protections, and reapplication of a test decision when reconstructing an old test backup. These tests did not delete real information and do not establish that production deletion, complete backup cleanup or prevention of reimport is implemented.

The current production restore and import processes do not automatically reapply deletion decisions or prevent previously handled information from being imported again. Backup handling requires separate review; deleting a current copy is not proof that every copy has been removed. No fixed automatic deletion period or secure-erasure guarantee is stated here.

8. Questions and privacy requests

Contact andyw@pikapark.us to request review, access, correction or deletion of personal information processed through the Application. Describe the records or activity involved and your relationship to them. Do not include passwords, tokens, card details or unnecessary identity documents in your initial email.

Proportionate verification of identity and authority may be necessary. Available rights, response requirements and permitted exceptions depend on applicable law and the Company’s role. Requests currently require administrative handling; the Application does not automate their fulfillment. Records independently held by providers may also require action through those providers.

9. Intended users and changes

The Application is restricted to authorized internal business personnel and is not designed to solicit information from children. Please contact us if unnecessary sensitive or child-related information has been included in Application records.

This Policy may be revised to reflect actual processing changes. Revised wording does not itself enable a feature, authorize an external action or establish that a proposed retention or deletion control has been implemented.