Updated 2026-07-02
Security
CueKit is a browser-first teleprompter, so security depends on clear product boundaries: what stays in the browser, what is sent for AI, how accounts work, and how checkout is handled.
Browser recording
CueKit uses browser recording capabilities where available. Camera and microphone permissions are controlled by your browser, and CueKit cannot bypass those prompts.
The current recording flow is designed for local preview and local .webm download.
Local downloads
Recorded takes are downloaded as local .webm files in the current flow. Manage those files like any other local recording on your device.
AI script requests
When you choose an AI action, CueKit may send your submitted script text, prompt, and instructions to an AI provider so the feature can return a generated or rewritten script.
Use the free online teleprompter without AI actions when you want to avoid sending script text for AI processing.
Supabase Auth
CueKit uses Supabase Auth for account sign-in and session handling. Authentication cookies or tokens are used to keep you signed in.
Creem checkout
CueKit uses Creem for checkout and subscription payment flows. Payment details are handled through the checkout provider rather than stored directly in the CueKit app.
Camera and microphone permissions
Camera and microphone permissions are controlled by your browser. You can review or revoke permissions in browser settings.
If permissions are denied, CueKit can still function as a script and teleprompter surface, but camera recording may not work.
Responsible reporting
If you believe you found a security issue, contact support@cuekit.online with enough detail for us to reproduce the problem.