1. Purpose and scope
Paperclip uses connected platform data to authenticate users, link creator accounts, verify ownership, verify campaign submissions, check campaign-relevant metrics, protect against fraud, support users, and satisfy platform review requirements. Data access is limited to what is needed for those purposes.
2. Platform data map
The expected platform data categories are:
| Provider | Data used | Purpose |
|---|---|---|
| TikTok | Basic user profile, account identifier, authorized media or video metadata, and campaign-relevant metrics when approved. | Creator account linking, content ownership checks, and campaign delivery verification. |
| Meta / Instagram | Authorized profile, account, media, insight, and webhook data after product path and review approval. | Creator account linking, media validation, campaign metric review, and fraud checks. |
| Google / YouTube | OAuth identity, channel identity, video lists, metadata, and campaign-relevant statistics through approved read-only access. | YouTube account linking, video ownership verification, and campaign performance checks. |
| Apple | App review, distribution, TestFlight, and Apple account metadata needed for iOS release operations. | iOS app review, testing, crash diagnostics, and release management. |
| Telegram Gateway | OTP delivery metadata and authentication status. | Phone-number sign-in and account security for Cambodia validation. |
| ABA / KHQR rails | Deposit and payout references, approved amounts, status, and audit evidence. | Brand deposits, creator payouts, reconciliation, and financial audit. |
3. Minimization and allowed use
- Paperclip requests the minimum practical access needed for account linking and campaign verification.
- Paperclip does not sell platform user data.
- Paperclip does not use platform user data for unrelated advertising or model training.
- Paperclip does not transfer platform user data except to provide the service, comply with provider policy, protect security, or satisfy legal requirements.
- Production APIs are not treated as approved until each provider grants the required production access.
4. Storage and security
Paperclip separates staging and production environments. Secret values are stored in a secrets manager and are never committed to source code, prompts, logs, examples, or public documentation. Sensitive application data is protected through access control, encryption where appropriate, audit logging, operational monitoring, and staff access controls.
5. Staff access
Staff and operators receive the minimum access required for setup, support, fraud review, platform review, or payout approval. Production back-office access is protected by Cloudflare Access and an approved identity provider. Payout release remains manual and single-approver during validation.
6. Retention, disconnection, and deletion
Platform tokens and connected-account data are retained only as needed for the user account, campaign verification, support, audit, legal, and fraud-prevention needs. Users may disconnect accounts or request deletion. Paperclip may retain limited ledger, payout, fraud, dispute, or legal records when required.
7. Service providers
Paperclip uses infrastructure, database, cache, email, authentication, OTP, observability, analytics, DNS, hosting, and payment-rail providers. Providers are used only for the operational purposes described in this notice and the Privacy Policy.
8. Contact
Platform review, data-handling, or deletion questions can be sent to antony@aivosoftware.com.