Local source workflow
Source videos and rendered clips are processed through the desktop workflow. Pacinos does not require users to publish their private source library on this public website.
Security & data handling
Local-first processing with explicit third-party permissions.
Pacinos is designed to keep source media, application configuration and account access under the user's control while using external services only where a selected feature requires them.
Protected tokens
Connected-account tokens are treated as secrets and stored using operating-system protected local storage where supported.
Client-secret protection
Platform client secrets are not exposed in the public website and are not intended to be embedded in public source code.
Minimum permissions
Pacinos requests only the platform permissions needed for the integration features the user is using.
No password collection
Third-party authentication takes place with the third-party provider. Pacinos does not ask users to type their TikTok password into Pacinos.
Disconnect support
Users can remove connected account access and can contact Pacinos about deletion of Pacinos-controlled personal information.
Cloud AI
Cloud processing is feature-specific, not a requirement for every operation.
Pacinos can use local AI models for parts of its content-analysis workflow. Where a configured cloud-AI feature is used, the relevant text, transcript excerpts or metadata needed for that request may be sent to the selected provider. Pacinos is designed to avoid sending secrets such as API keys inside AI prompts.
Data-minimisation approach
- Use local processing where practical
- Send only task-relevant content to configured providers
- Keep API credentials out of model prompts
- Separate test/benchmark data from production analytics
- Treat stale or missing metrics as unreliable rather than silently learning from them
Report a security concern
If you believe you have found a security or privacy issue affecting Pacinos, contact:
Do not send passwords, API keys, access tokens or other secrets in the initial email.
Responsible access
No account takeover, credential harvesting or platform evasion.
Pacinos is intended to work with creator-owned or properly authorised accounts. The product does not need automated account creation, stolen session data, browser-cookie extraction or anti-enforcement techniques to perform its intended workflow.