Privacy Policy

This policy explains how SlicePost handles information when you visit slicepost.com, use our tools, or connect an account or integration. SlicePost is operated by Noia Media LLC, based in Iowa, United States. Privacy questions: privacy@slicepost.com.

1. Information we handle

• Account information: email, profile details supplied by your sign-in provider, account identifiers, and workspace membership.
• Beta requests and email updates: the email address you submit, your consent and confirmation status, and delivery or unsubscribe records.
• Your projects: videos, audio, source links, transcripts, thumbnails, edit settings, captions, and exports. Recordings can contain information about other people.
• Connected accounts: social account identifiers, handles, connection permissions, authorization references, scheduled posts, and posting results. Our posting provider handles the social authorization tokens needed to perform the actions you request.
• Integrations: API key identifiers, permissions, expiry and revocation status, authorized applications, and API or MCP activity.
• Technical records: request and job identifiers, usage, timestamps, browser and device details, viewport, and application errors. Hosting and security providers also receive IP addresses and request metadata.
• Support and billing: messages, bug reports, and attachments you supply; and, if you purchase, billing contacts, transaction references, and subscription status. The payment processor handles payment card details.

2. Why we use it

We use information to sign you in, process and store projects, generate clips and captions, publish posts you authorize, track allowances, answer support requests, and deliver account notices. Technical records help us diagnose failures, improve reliability, maintain security, and prevent abuse.

If you request beta access, we use your email to send a confirmation link, beta invitation notices and public-launch news. We add you to the mailing list after you confirm your email. Joining the list does not create an account or guarantee access. You can unsubscribe through the link in our updates or contact hello@slicepost.com.

Where a legal basis is required, we rely on performing our agreement with you, legitimate interests in operating and securing the service, legal duties, or consent where required. Withdrawing consent does not affect earlier lawful processing.

3. Media processing

Hosted media is stored in cloud storage. Transcription providers receive audio; language-model providers receive transcripts and instructions for clip selection or writing; video workers receive media and edit settings. Posting sends selected media, captions, and settings to the posting provider and destination platform.

YouTube posting uses YouTube API Services through Post for Me. We handle the selected channel's connection identifiers, reviewed post details, schedules, and publishing results to provide that workflow. Connecting a channel does not authorize a post by itself; you select the destination and review each submission.

Framing can analyze faces and speech activity to follow speakers within a video. These are editing aids, not a feature for identifying people by name, matching identity across customer projects, or inferring sensitive traits. You must have permission to process the recordings you submit.

We do not use uploaded media to train our own models. External provider data handling depends on the service and applicable agreement; we do not promise identical retention or training rules across every provider.

4. Providers and disclosures

These providers support hosted workflows. Which receive your information depends on the feature you use. Their notices provide additional context; processing on our behalf is also governed by applicable service agreements.

• Clerk: authentication, sessions, and delegated application authorization.
• Supabase: database records, including projects, permissions, usage, and job status.
• Cloudflare: R2 media storage, network delivery, and security.
• Railway: application hosting and operational logs.
• RunPod and Modal: cloud media workers, where used.
• Deepgram and Groq: speech transcription, depending on the workflow.
• OpenAI: transcript-based clip selection and text generation.
• Post for Me: social account connections, scheduling, and publishing on slicepost.com.
• Stripe: payment processing when checkout is available and you purchase.
• Brevo: beta-request forms, consent and confirmation records, and email updates you request.
• Zoho Mail: support, privacy, legal and other correspondence sent to our SlicePost email addresses.

The separate internal localhost workflow can use locally configured providers, including UploadPost. It does not change the hosted Post for Me posting workflow.

We may disclose information to comply with lawful requests, protect rights or safety, investigate abuse, or resolve disputes. Information may transfer with the business in a merger or sale, subject to applicable law. We do not sell personal information or share it for cross-context behavioral advertising.

5. Cookies, browser storage, and diagnostics

Cookies and browser storage support sign-in, security, theme preferences, workflow state, and recovery of queued diagnostic events. Blocking them can prevent sign-in or interrupt editing.

Errors and failed requests may be reported automatically. Reports can include the page, request status, job reference, browser, viewport, timezone, and connection state. Diagnostic context is limited and common credentials and private locators are redacted. Reports you submit can also contain your description or attachment; avoid sending passwords or API keys. Diagnostic events are not a recording of everything you type or a video replay of your session.

Some pages load fonts from Google, which receives network information needed to serve them. See Google's privacy policy.

6. Retention and deletion

Project expiry, Save status, and storage usage are shown in the application. Unsaved projects can expire on the displayed date. Saving keeps the editable project within your allowance, without creating extra capacity. Removing Save restores the applicable expiry. Keep independent copies of important exports.

Deletion or expiry can require background cleanup; active processing or reconciliation may delay removal. Hiding a project does not prove every copy has been erased. Project expiry removes eligible stored media; it does not erase the complete account data graph. Project metadata, transcripts, edit settings, posting records, and cleanup receipts can remain after media expiry. Account, billing, security, and support records may be kept longer for operations, legal duties, fraud prevention, or disputes. Backups and provider records follow their applicable retention processes.

Request account or personal-data deletion at privacy@slicepost.com using your account email. We may verify your identity. Deleting SlicePost data does not delete downloaded files or posts already published to social platforms.

7. Choices and rights

You can manage available account settings, disconnect social accounts, and revoke API keys or application access. Disconnection stops new use of that connection, but does not remove published posts. Review pending scheduled posts separately. You can also revoke access in the platform's security settings. For Google, use Google's security permissions page. Google/YouTube data is also subject to Google's privacy policy.

Depending on your location, you may have rights to access, correct, delete, or receive a copy of information; restrict or object to processing; withdraw consent; or appeal a request decision. Send requests and appeals to privacy@slicepost.com. We handle them under applicable law without penalizing you for exercising your rights. You may complain to your local data-protection authority.

External API or MCP clients can receive data and take actions within their permissions. Choose clients carefully, review their privacy policies, and revoke access when it is no longer needed.

8. Security and international processing

We use access controls, tenant authorization, private storage, and limited-duration media links. No internet service is completely secure. Keep credentials private and report suspected unauthorized access to support@slicepost.com.

Providers may process information outside your country. Transfers must use safeguards required by applicable law where required. Contact us about arrangements relevant to your use; we do not promise all data stays in one country.

9. Age requirement

Accounts are intended for adults aged 18 or older. If you believe a child has supplied personal information, contact privacy@slicepost.com so we can investigate.

10. Updates and contact

We update this policy when practices change. The date above identifies this version. We provide additional notice of material changes when required by law. Privacy: privacy@slicepost.com. Product help: support@slicepost.com.