OlyWork

Data we process

OlyWork may process account profile data, OAuth identifiers, Discover listing metadata, creator package metadata, install/access token records, usage logs, IP address, user agent, and security audit events.

OlyWork may also process creator verification signals such as GitHub installation metadata, repository owner names, selected file paths, package version metadata, and moderation report details.

GitHub sources

When creators connect GitHub, OlyWork uses authorized installation access to ingest selected repository paths server-side. Private repository URLs and source metadata are not shown to buyers through public pages, collection exports, library pages, or sync responses.

Package delivery logs

OlyWork logs sync attempts, token status, route, timestamp, IP address, and user agent so creators and operators can detect token abuse, failed installs, and suspicious access.

Sync responses are designed to return package payloads and public manifest data only after entitlement validation. They should not include private repository URLs, internal storage keys, or creator infrastructure details.

Payments

Payments are currently dormant. When enabled, payment processing will be handled by Stripe, and OlyWork will store only the billing identifiers needed for checkout, fulfillment, refunds, disputes, subscriptions, and creator payouts.

Retention and removal

OlyWork keeps operational records while accounts, listings, entitlements, and audit trails are active. You can request account or listing review through support channels, subject to security, fraud, audit, and legal retention requirements.

Security

OlyWork uses access controls, token status checks, encrypted package delivery, audit logs, and restricted source exposure to reduce unauthorized redistribution. No internet service can guarantee perfect security, so creators should avoid uploading unnecessary secrets or private customer data.