NO MORE BITS

Content Engine privacy policy

Last updated: September 18, 2026.

This policy describes the current data handling of Content Engine by No More Bits, a desktop recording and editing library used by our team.

Data the application handles

The application handles selected recordings and their audio, previews, thumbnails, timestamps, human markers, bookmarks, tags, transcripts, summaries, questions and answers, editing notes, and export history. It also uses account identifiers, project membership, and authorization credentials to connect authorized users to shared services.

Google user data

Content Engine requests Google Drive access to upload recording assets to a configured shared folder and retrieve those assets for playback and editing. It reads file and folder metadata, including identifiers, names, sizes, checksums, and access capabilities, to locate media and verify transfers.

The current Google permission permits viewing, editing, creating, and deleting files accessible to the connected Google account. The application uses the configured project folder for its shared media workflow. Authorizing the application does not automatically share the user's Drive with other team members.

Use and sharing

Data is used to provide recording review, collaboration, transcription, AI-assisted bookmarking, search, and export. Google Drive stores shared media. Supabase stores shared library metadata and manages application accounts and membership. Authorized team members can access data according to the library and Drive permissions configured for them.

When AI processing is enabled or requested, the application sends relevant audio, transcript text, questions, metadata, and optionally selected video frames to OpenAI for transcription or analysis. This can include content retrieved from the project's Google Drive folder. Automatic visual analysis is disabled by default. AI spending is subject to configured recording and project limits.

The application does not sell Google user data or use it for advertising. Content Engine's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Storage and protection

The desktop application keeps a local metadata database and local media or cached previews. Google authorization tokens, Supabase session tokens, and API credentials are stored in the operating system's credential store. Shared metadata access is restricted by project membership. Media access also depends on the sharing permissions set on Google Drive.

Retention and deletion

Recordings and metadata remain until removed by the responsible user or administrator. Revoking authorization stops future authorized access but does not delete existing local files or shared copies. Automatic deletion of shared originals is not performed by this application. Local cleanup and cloud deletion are separate operations; other team members may retain copies or exported clips.

To request removal of data from the shared library and its managed copies, contact No More Bits at ali.alabbasi03@gmail.com and identify the relevant recording or account. The administrator can coordinate deletion of local and cloud copies.

Your controls

You can disconnect the Google authorization from your Google Account connections, change Drive sharing permissions, and ask the library administrator to remove application access. Administrators can pause AI processing or change its spending limits.

Contact and changes

Questions about this policy can be sent to ali.alabbasi03@gmail.com. Changes to the application's data practices will be reflected here with an updated date.