JAWP House Media

Privacy Policy

Effective date: September 20, 2026
Applies to: JAWP House Media and JAWP Clipping Jarvis

This Privacy Policy explains how JAWP House Media (“we,” “us,” or “our”) may collect, use, and share information in connection with the JAWP Clipping Jarvis application and related websites and services (collectively, the “Service”).

This Privacy Policy describes how JAWP House Media handles information in connection with the Service. It is not a substitute for legal advice.

1. Information We Collect

Depending on how you use the Service and which accounts you explicitly connect, we may process the following categories of information:

  • Account identifiers (for example, usernames, account IDs, or emails associated with a connected account)
  • Profile information made available by a connected platform
  • OAuth authorization information (such as authorization codes, granted scopes, and related callback parameters)
  • Access and refresh tokens used to perform authorized integrations
  • Authorized social-account information needed to operate connected workflows
  • Content supplied or authorized by users (including media files, titles, captions, and related instructions)
  • Video and media metadata (for example, duration, format, timestamps, and processing status)
  • Posting information and publishing status for authorized distribution workflows
  • Analytics and performance information retrieved through permitted platform APIs or user-authorized reports
  • Workflow and audit records (for example, approval decisions, operator actions, and exception logs)
  • Technical logs necessary to operate and secure the Service (such as request metadata, error logs, and diagnostic events)

We do not ask you to provide information beyond what is needed to operate authorized workflows. We process and store information only as needed to operate the Service and related security, audit, and support functions.

2. How Information Is Used

We use information for purposes such as:

  • Authenticating connected accounts
  • Performing user-authorized actions on third-party platforms
  • Preparing, reviewing, and distributing content that users authorize
  • Retrieving permitted analytics and performance information
  • Maintaining security, troubleshooting, and service reliability
  • Supporting auditability and human approval workflows
  • Improving internal workflow performance and operator tooling

Credentials and authorization tokens are used to perform authorized integrations and must not be exposed publicly. Tokens and secrets should be stored server-side or in secure credential storage, not in client-side browser storage.

3. Connected Third-Party Services

The Service may integrate with third-party platforms that you choose to connect (for example, social platforms used for authorized publishing or analytics). Those platforms process information under their own privacy policies and terms. Using a platform API does not create a partnership with that platform.

Third-party platforms you connect, and service providers that help us operate the Service, may process information as needed to provide those services under their own terms and policies.

4. OAuth and Authorization

When you connect an account through OAuth or a similar authorization flow, we receive authorization artifacts necessary to complete the connection (such as a temporary authorization code and state parameter) and to obtain tokens for authorized API access.

  • Authorization codes and tokens should be handled server-side.
  • State values should be validated server-side when the full OAuth integration is enabled.
  • We do not intentionally display secrets, tokens, or authorization codes in the public website UI.

You may disconnect authorized accounts through the relevant third-party platform’s account/app settings. Additional Service-side disconnect controls may be available depending on your access.

5. Content and Media

Content you supply or authorize may be processed to generate clip candidates, support quality and compliance review, prepare distribution packages, and maintain workflow records. You are responsible for ensuring you have appropriate rights and permissions to the content and accounts you authorize.

6. Data Sharing

We may share information in limited circumstances, including:

  • With third-party platforms when you authorize an action on that platform
  • With service providers who help us host, operate, secure, or support the Service
  • When required by law, valid legal process, or to protect rights, safety, and security
  • In connection with a merger, acquisition, financing, reorganization, or sale of assets, if applicable

We do not sell personal information as a retail product. If a specific privacy law uses a broader definition of “sale” or “share,” we will handle requests as required by applicable law.

7. Data Retention

We retain information only as long as needed for the purposes described in this Policy, including security, audit, dispute resolution, and legal compliance needs.

8. Security

We take reasonable administrative, technical, and organizational measures designed to protect information processed by the Service. No method of transmission or storage is completely secure. Specific certifications, encryption standards, or compliance attestations are not claimed in this Policy unless separately documented.

9. User Choices and Account Disconnection

Depending on the feature set available to you, you may be able to:

  • Disconnect a connected third-party account
  • Request updates to account contact details
  • Limit or stop use of certain integrations

Platform-side revocation (for example, removing app access in a social platform’s settings) is also an important control.

10. Data Deletion Requests

You may request deletion of personal information associated with your use of the Service by contacting us through the Contact page. We will review deletion requests and may need to verify the requester’s identity before acting. We may retain limited information when required for security, audit, legal, or operational reasons.

11. Children's Privacy

The Service is not directed to children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided personal information, contact us and we will take appropriate steps.

12. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will revise the effective date above and post the updated Policy on this page. Material changes will be posted on this page. We may also provide additional notice when appropriate.

13. Contact

For privacy questions or deletion requests, contact: