Archived policy. This version has been superseded. Read the current privacy policy.

Clippy Creator Studio Privacy Policy

Effective date: September 19, 2026

Clippy Creator Studio (“Clippy,” “we,” “us,” or “our”) is a Mac application developed by Domenico Ditanna for editing recordings, preparing captions and publishing details, and scheduling videos on YouTube. This policy covers the Clippy Mac app, this Clippy privacy website, and feedback you send to us. A planned sales website, paid checkout, and license accounts are not yet operating under this release. We will update these disclosures before those features collect information.

Website visits, cookies, and tracking

This privacy page does not include a signup form, checkout, advertising pixels, embedded social media, or an analytics script added by Clippy. Its hosting and network providers process technical connection information such as IP addresses and request details to deliver and protect the page. This page is hosted through OpenAI Sites; provider processing is described in the OpenAI Privacy Policy.

Our page code does not set cookies, use browser storage, or track your activity across other websites. We do not sell website visitor information or share it for cross-context behavioral advertising. Browser Do Not Track and Global Privacy Control signals do not change this page's behavior because those activities are not enabled for any visitor. Links to Google, Apple, and other websites open services with their own privacy practices; those services are not embedded trackers on this page.

Information Clippy handles

Recordings and edits. When you select a footage source, Clippy accesses recordings and file information, including names, locations, duration, and available recording dates. It creates transcripts, captions, proxies, audio analysis, editing settings, and rendered videos. Recordings and transcripts may contain personal information about you or other people.

Projects and publishing. Clippy stores project names, preferences, titles, descriptions, tags, approval choices, posting schedules, and upload or verification status.

Connected accounts. Connecting YouTube gives Clippy authorization tokens and channel information through Google. Clippy accesses video identifiers, links, processing status, visibility, and scheduling information to upload videos and verify their status. You sign in through Google; Clippy does not ask for your Google password. Imported Google desktop OAuth client credentials and account tokens are stored in macOS Keychain.

Feedback and diagnostics. If you contact us, we receive your contact details, message, and any attachments you provide. Local diagnostic records may contain file paths and technical details. Apple may provide us with TestFlight feedback, crash reports, and testing information through its beta distribution service.

How information is used

Clippy uses this information to find footage in selected sources; transcribe, caption, edit, and export videos; remember preferences; generate publishing drafts; connect the intended YouTube channel; upload and schedule authorized videos; verify their publishing status; and diagnose problems. We use feedback to answer support requests and improve the app.

We do not sell personal information, use it for targeted advertising, or include a separate advertising or behavioral analytics service in the current app.

Local processing and AI

The current app processes video, audio, transcription, and editing on your Mac. Available Apple on-device language-model features can use transcript text to suggest titles, descriptions, and tags. When the on-device model is unavailable, Clippy can use local text-processing methods instead.

Clippy does not send footage or transcripts to a Clippy-operated cloud AI service. We do not use your recordings, transcripts, or Google account data to train general-purpose AI models. Review generated drafts before approving publication because they may contain errors.

Storage

Project settings, transcripts, editing records, and publishing records are stored in your local library. Proxies, analysis files, and exports may be stored on your selected SSD or another location chosen in the app. Clippy may create local library backups during updates. These backups do not include original media or Keychain credentials.

We do not automatically receive a copy of your local library or recordings. Files in folders synchronized or backed up by another service are subject to that service's settings and policies. People and software with appropriate access to your Mac or drive may be able to access local files.

Google and YouTube

Clippy uses YouTube API Services. When you authorize an upload or automatic publishing, Clippy sends the selected video and publishing information to YouTube. This can include titles, descriptions, tags, language, category, recording date, audience settings, visibility, and scheduled publication times. Clippy reads relevant channel and video information to display your connected account and check upload, processing, and scheduling status.

Your chosen visibility and schedule determine when others can access an uploaded video. Google handles information under the Google Privacy Policy. YouTube use is subject to the YouTube Terms of Service.

Disconnecting a channel in Clippy removes that project's saved authorization tokens and disables its automatic publishing connection. It does not erase local project history or delete videos already uploaded. You can also revoke authorization through Google account permissions. Manage or delete uploaded videos through YouTube Studio.

Other recipients

Apple handles TestFlight distribution, updates, and related beta services under its Privacy Policy and applicable TestFlight terms. Feedback email is processed by the email service used to deliver and store that correspondence.

We may disclose information we actually hold when required by law or reasonably necessary to protect security, investigate abuse, or protect legal rights. This does not give us remote access to recordings stored only on your Mac.

Retention, deletion, and choices

Local projects and editing records remain until you remove them. Updates are designed to preserve your library, and local backups are not automatically erased. Removing a recording from the grid does not necessarily delete its media, exports, or backups. Uninstalling the app may leave local data and Keychain items behind.

You can stop watching a footage source, disconnect YouTube, revoke Google access, and delete files you control. Contact us for help removing local Clippy data, connected-account records, or credentials. Delete backup copies separately if you want those removed too. Deleting Clippy data does not delete information held by YouTube or Apple.

We retain feedback and support information only as long as needed to handle requests, investigate related issues, or meet applicable legal obligations. Contact us to request access, correction, or deletion of personal information we hold. Additional privacy rights may apply depending on where you live. We may need to verify your request before acting on it.

Your California privacy rights

California residents may contact us to review, correct, or request deletion of personal information we hold. Where the California Consumer Privacy Act, as amended by the California Privacy Rights Act, applies, rights include knowing the categories and specific information collected, receiving a portable copy, correction, deletion subject to exceptions, opting out of sale or sharing, limiting certain uses of sensitive information, and receiving equal treatment for exercising those rights.

The information categories used by the current app and support service are identifiers and contact details; recordings and audio/visual content; transcripts and other content you provide; account authorization information; project and publishing activity; and technical or diagnostic information. Their sources, purposes, storage, and recipients are described above. Most app information stays on your devices, rather than being collected by us. We do not sell personal information or share it for cross-context behavioral advertising, including information about minors. We do not use sensitive information to infer characteristics about you.

Send a request using the privacy request email. Identify the service and request type; do not attach identity documents, passwords, tokens, or private footage unless a secure, necessary verification method has been arranged. We may confirm control of the relevant email or request limited information to match records. An authorized agent can contact us with evidence of authority; we may also need to verify the person represented. We respond within applicable legal deadlines and explain any lawful exception. We cannot remotely delete files held only on your Mac, but can help you locate them.

Security

Clippy uses macOS Keychain for saved OAuth credentials and HTTPS for Google API communications. Protect your Mac, external drives, backups, and account access. No storage or transmission method guarantees complete security.

Children's privacy (COPPA)

Clippy is a general-audience creator tool, not a service directed to children under 13. Children under 13 should not submit personal information to us. We do not knowingly collect personal information online from children under 13. If we learn that we have received such information, we will stop using it and take steps to delete it, unless a narrow legal exception permits retention. Parents or guardians can contact us about a child's information; we will use appropriate verification before disclosing information or acting on a request.

This statement is not a parental-consent process. If Clippy introduces a child-directed service or knowingly permits under-13 accounts, the required notices, verifiable parental consent, parental controls, security, and retention safeguards must be in place first. A video's YouTube audience setting is a separate decision: creators must accurately identify content made for children. Choosing “not made for kids” does not establish COPPA compliance for a website or app.

Changes

We will revise this policy and its effective date when our practices change. Material changes will be communicated through the app or another appropriate channel. If a new use of information requires consent, we will obtain it before that use begins.

Contact

Developer: Domenico Ditanna
Privacy and feedback email: Domditanna@gmail.com

Use the subject “Clippy Privacy Request” for privacy questions or requests. Do not send passwords or authorization tokens.