Quibbly

Privacy Policy

Last updated: April 14, 2026

1. About This Policy

This Privacy Policy describes how Quibbly, a product of Scriptify Inc. (DBA Quibbly), handles information when you use the Quibbly Chrome extension and its connected account, recording, storage, and reporting features. Our registered address is 838 Walker Road, Suite 21-2, Dover, DE 19904.

2. Our Privacy-First Approach

Quibbly is designed so that customer recordings and reporting remain private to the customer organization. Quibbly employees cannot view, play, download, or otherwise access customer videos or organization reporting. Access is restricted through account, organization, and workspace permissions, and only authorized members of the customer organization can access this information.

Our systems may automatically process recordings and reporting data only as necessary to provide the features requested by the user. This automated processing does not make the content available to Quibbly employees, and we do not manually review customer recordings or reporting data.

We do not sell personal information or recording content. We do not use recordings or reporting data for advertising, profiling, employee review, or AI model training.

3. Information We Handle

Quibbly handles only the information needed to provide and secure the service. Depending on the features you use, this may include:

  • Account information, such as your email address, name, organization, workspace membership, and account settings.
  • Recordings and related media that you choose to create, upload, store, or send through Quibbly.
  • Reporting information about activity performed through Quibbly, such as the organization member who sent an item, the date and time, media type, send source, item name, and recipient details associated with the send.
  • Limited technical error information when the extension encounters a problem, such as an error message, feature context, and session identifier. Error reports are used only to diagnose and improve reliability.

Quibbly does not collect your general LinkedIn browsing history, private LinkedIn messages, contacts, or LinkedIn password. The extension does not collect, store, or transmit the value of your LinkedIn cookies to Quibbly.

4. Recordings and Video Storage

When you record, upload, store, or send a video using Quibbly, the recording may be transmitted to and stored by Quibbly so that we can provide conversion, delivery, playback, library, and organization features requested by you.

Recordings are encrypted in transit and at rest and are stored in the U.S. East region. Quibbly does not use recording content for advertising, profiling, sale, employee review, or AI model training. Any automated processing of a recording is limited to providing the requested product functionality, such as converting the file into a compatible format, generating playback assets, storing it in the organization library, or delivering it at the user's direction.

Recording access is governed by the account, organization, workspace, and sharing permissions selected by the organization. Within the Quibbly product, only authorized members of the organization or workspace can access private recordings. Quibbly employees cannot view, play, download, or access customer recordings.

If an organization or user intentionally creates or enables a public or shared link, anyone with the required link or access credentials may be able to view that recording according to the selected sharing settings.

5. Organization Reporting

Quibbly provides reporting so organizations can understand how their members use Quibbly. Reporting may include send activity such as the sender, date and time, media type, send source, item name, and recipient name or profile information associated with the send.

Reporting does not include the contents of a video, audio recording, or private message. Organization administrators control whether team reporting and recipient details are visible to other organization members. Reporting information is available only to the user and authorized members of the same organization according to those settings. Quibbly employees cannot access or view an organization's reporting information.

6. How We Use Information

We use information only to:

  • Provide, maintain, and secure Quibbly.
  • Process, store, convert, play, and deliver recordings at the user's direction.
  • Authenticate users and manage accounts, organizations, workspaces, subscriptions, and permissions.
  • Provide organization reporting and related product functionality.
  • Diagnose errors, prevent abuse, and improve service reliability.
  • Respond to support requests and comply with applicable legal obligations.

We do not sell personal information, recording content, or reporting data. We do not use recording content or reporting data for advertising, profiling, employee review, or AI model training.

7. Cookies and Tracking

The Quibbly Chrome extension does not use advertising cookies, third-party tracking cookies, tracking pixels, or behavioral advertising technologies.

Quibbly may use a strictly necessary authentication token or cookie to keep a user signed in and connect the extension to the user's Quibbly account. The extension operates within the user's existing LinkedIn session to perform actions requested by the user, but Quibbly does not collect, store, or transmit LinkedIn cookie values.

8. Service Providers and Third Parties

Quibbly does not sell, rent, or disclose personal information or recording content to third parties for advertising, profiling, or their own independent use.

Quibbly may use infrastructure, storage, payment, and other service providers that process limited information on our behalf only as needed to operate the service. These providers are not permitted by Quibbly to use recording content for their own advertising or profiling purposes. Payment card information is handled by our payment processor and is not stored by Quibbly.

When a user directs Quibbly to send media through LinkedIn, the media and related information are provided to LinkedIn as necessary to complete that user-requested action. LinkedIn's handling of information is governed by LinkedIn's own terms and privacy policy.

9. Data Retention and Deletion

Stored recordings and related account information are retained while needed to provide the service or until they are deleted by an authorized user or organization, subject to limited backup, security, fraud-prevention, and legal retention requirements.

Users and organizations can delete recordings through available Quibbly controls or request deletion of account information by contacting [email protected]. Deleting a recording or account from Quibbly does not delete copies that a user has already sent to LinkedIn or another destination.

10. Data Security

Quibbly uses strict administrative, technical, and organizational safeguards designed to protect information. These safeguards include encryption in transit and at rest, storage in the U.S. East region, authentication, and account-, organization-, and workspace-based access controls. Customer videos and organization reporting are not accessible to Quibbly employees.

No method of transmission or storage is completely secure. Users are responsible for protecting their account credentials and configuring organization, workspace, and sharing permissions appropriately.

11. Your Choices and Rights

Depending on where you live, you may have rights to access, correct, export, or delete personal information, or to object to or restrict certain processing. You may also manage recording access and sharing through your organization's Quibbly settings.

To make a privacy request, contact [email protected]. We may need to verify your identity and authority to act for an organization before completing a request.

12. Contact Us

If you have questions about this Privacy Policy or how Quibbly handles information, contact us at [email protected].

13. Changes to This Policy

We may update this Privacy Policy from time to time. Any changes will be posted on this page. The date displayed at the top of the policy identifies the applicable version.