Privacy Policy

What we collect

We collect information you provide directly: your name, email address, workspace data, and content you import or create inside Sigmora. We also collect usage data (pages visited, features used, error logs) to improve the product.

How we use it

We use your data to operate the service, send transactional emails (billing receipts, invitations), and improve the product. We do not sell your data to third parties. We do not use your content to train AI models.

Managed-services meetings

When you book a managed-services meeting, we use Zcal to collect the booking details you enter, check availability, create the calendar invitation, and send meeting reminders. Zcal processes this information under its own privacy terms; only the details needed to arrange and deliver the meeting are shared with it.

Browser extension

After you invoke the Sigmora browser extension, it sends the active page URL, visible title, your instruction, and a bounded selection or main visible-text snapshot to plan the requested action. On an ordinary page it may also send a value-free semantic snapshot of visible control kinds, labels, required/disabled state, character limits, and existing dropdown options; it does not read those fields’ current values. A returned plan may contain the exact ordinary values to fill, options to select, non-consent toggles to set, targets to scroll to, or one reversible non-submit control to click. The extension revalidates the URL, semantic target, label, control kind, and state before acting. On supported YouTube, TikTok, Instagram, Reddit, X, and LinkedIn pages, it may also send the URL to look for an existing saved analysis, and it sends a title and URL when you choose to save, analyze, or remix a video. On supported editing and reply surfaces, it sends current editor text and only the bounded visible context needed for the action at its applicable execution boundary. Workspace owners choose Review, Autopilot, or YOLO for creator-instructed plans: Review requires a second approval; Autopilot can immediately run zero-credit same-page semantic operations; and YOLO can also navigate or use displayed credit-spending generation tools after the creator’s initial instruction. Non-review authorizations expire after 30 days. The model cannot grant itself those modes. If the task belongs on another site, Sigmora may propose a public HTTPS destination and displays its hostname in Review mode before opening it. Passwords, MFA or OTP values, passcodes, recovery codes, cookies, payment or identity-number fields, consent controls, destructive controls, and other form values are never requested by the extension, sent to the model, or stored; you authenticate directly on the platform page with your browser password manager and complete MFA yourself. A dashboard-configured active-tab monitor may inspect visible YouTube comment controls locally while the tab is open. In review mode, comment text is sent only when you request an action. If a workspace owner expressly enables the 30-day YouTube autopilot policy, bounded visible comment context may instead be sent when a matching visible tab encounters an owner-authorized clear question or praise target; the configured identity, signed-in YouTube handle, categories, credit cost, hourly limit, and daily limit constrain that processing. The extension reads YouTube’s visible active-account header locally and stops if its handle does not match the owner’s authorization. Sigmora combines requests with the workspace, creator identity, and Voice profile you selected, then applies the result to the page under the selected execution mode. A supported YouTube, X, LinkedIn, or Instagram Post or Reply control is invoked only under a separate approval for that exact draft and target; other final controls remain in the platform UI, and a low-risk YouTube reply may instead use the owner’s unexpired bounded YouTube autopilot authorization. Generic final Post, Publish, Send, Save, Pay, and Submit controls are never invoked by Review, Autopilot, or YOLO. Sigmora stores hashed target and draft identifiers, consent source, and submission outcome as a duplicate-prevention, limit-enforcement, and audit receipt; it does not copy the submitted text into that receipt. Sensitive or ambiguous replies remain review-only. If you explicitly choose a ready workspace video for an upload, or generate an image download under the applicable mode, the extension requests the authorized media and opens the browser’s save flow so you can hand the file into the platform’s native picker. It stores an opaque, revocable Sigmora extension session and selected-context metadata in your browser; it does not store your Firebase credential. Saved references and their analysis remain in your workspace until you delete them.

Data storage

Account and workspace records are stored in Google Firestore (Firebase, United States) and on Cloudflare. Files you upload, record or import from a link (video, audio, images), and the renders Sigmora makes from them, are stored in your workspace in object storage (Cloudflare R2 and Backblaze B2) and processed on our application servers, hosted by netcup in Germany. When you import a video from a link, we fetch it and keep a copy in your workspace so you can edit it. You can delete files from your workspace at any time. Card and subscription payments are processed by Stripe or Whop; Paystack is limited to supported USSD and M-Pesa payments. We do not store card numbers. The full list of providers that process data for us is on our sub-processor list.

If you join the affiliate program, we store the payout destination you submit so we can pay your commissions. Account numbers, payout emails, and mobile-money numbers are encrypted at rest and are available only to authorized payout operations. They are never included in staff notification emails. Do not submit card details, online-banking passwords, PINs, or tax identification numbers in the payout form.

Your rights

You can export all of a workspace’s data at any time from Settings (a re-importable JSON file — no lock-in). You can request deletion of your account and all associated data through our privacy request form; we process deletion requests within 30 days. If you are in the EEA, UK, or California, you also have rights of access, correction, portability, and objection — contact us to exercise them.

Google and YouTube data

When you connect a Google account, Sigmora asks only for the access the features you use need: uploading and managing videos on your YouTube channel and reading its analytics and comments (YouTube), reading files you choose to import (Google Drive), and, if you enable it, reading sign-in codes for browser publishing (Gmail). Sigmora’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data to train AI models, sell it, or use it for advertising.

Sigmora uses YouTube API Services. By connecting YouTube you also agree to the YouTube Terms of Service, and Google’s handling of your data is described in the Google Privacy Policy.

You can stop Sigmora’s access at any time by disconnecting the account in Settings > Connections, or by revoking it on your Google Account’s third-party access page. To have data we obtained from Google or YouTube deleted, use the privacy request form.

Enterprise & data processing

If you process personal data through Sigmora, our Data Processing Agreement governs that processing, and the full sub-processor list is published for review. A countersigned DPA is available on request.

Cookies

We use Firebase Auth session cookies to keep you signed in. We do not use advertising or tracking cookies.

Contact

Questions about this policy: use our privacy request form.