Privacy Policy · repli.ac

1. Introduction

repli.ac ("we," "us," or "our") operates a local-first content repurposing application for creators. You upload UGC clips, generate hook variations from caption word slots, stitch exports, edit on a timeline, and optionally record screen or webcam footage. Pro users may also back up clips to the cloud. Anyone signed in can connect Buffer and add a Buffer Personal Key to schedule posts to channels linked in Buffer. This Privacy Policy explains what information we collect, how we use it, and the choices you have when using repli.ac at repli.ac and in our Windows desktop app.

By using repli.ac, you agree to the collection and use of information described here. If you do not agree, please do not use the service. This page is a transparency notice about our practices. It is not legal advice.

2. Information we collect

We collect the following categories of information:

Account information: When you sign in with Google OAuth through Supabase Auth, we receive your email address, display name, profile picture URL, and a unique user identifier. We do not receive or store your Google password.
Subscription and billing metadata: If you purchase Premium, Stripe processes your payment details. We store your Stripe customer identifier, subscription status, plan type (monthly, annual, or lifetime), and billing period end date in Supabase. We never receive or store your full card number.
Local browser and desktop data: Video clips, rendered outputs, templates, caption word lists, export batches, timeline editor projects, layout preferences, recording drafts, and onboarding state may be stored on your device using IndexedDB, localStorage, and (in the Windows app) files under your local user data directory. This data stays on your device unless you enable cloud features or send a report described below.
Cloud uploads (optional, Pro): If you subscribe to Pro and enable cloud sync, video files and related metadata may be uploaded to Cloudinary and referenced in Supabase. This includes clips synced from the hook maker and recordings you choose to back up. That Pro library is a durable backup subject to a per-account quota (currently 1 GB). It is separate from Schedule staging described below.
Schedule staging media (when you Schedule or Post now): Buffer needs a public HTTPS video URL to publish. When you Schedule or Post now from a local stitch, editor, or recording export, we upload that file to Cloudinary as temporary schedule staging (not into your Pro 1 GB library, and it does not count against Pro quota). We keep that URL available so Buffer can fetch the video at publish time. For timed posts, we keep the staged file until Buffer reports the post as sent, then delete it after a short grace period. For Post now, we keep staging briefly after send, then delete it. We may store staging metadata in Supabase (for example Cloudinary public ids, Buffer post ids, due times, and status) so cleanup can run. If shared staging capacity is exhausted, we may block or refuse new Schedule uploads rather than silently fail. Canceling or deleting a scheduled item may delete unused staging sooner when it is safe to do so.
Buffer scheduling (optional, free with account): If you connect Buffer from Schedule and add a Buffer Personal Key, we store encrypted connection credentials (when used), your Buffer organization identifier, account email as returned by Buffer, and granted connection scopes in Supabase. When you sync channels, compose posts, edit or delete scheduled items, or save ideas, we call Buffer on your behalf. We may process post text, scheduling mode and due times, selected channel identifiers, media URLs (including schedule staging URLs we create), and channel/post metadata Buffer returns (names, service type, status, and similar fields). Social network logins for Instagram, YouTube, TikTok, and other channels happen in Buffer, not in repli.ac. Free accounts always schedule with your Buffer Personal Key. Pro prefers your Personal Key; when personal Buffer capacity is exhausted or credentials are missing, Pro may use repli.ac-operated Buffer application capacity. Disconnecting Buffer deletes the connection row and credentials we store; it does not delete posts already in your Buffer account.
Feedback you submit: When you send feedback through the in-app dialog, we store your message, the page you were on, optional intent and sentiment tags, your browser user agent, and (if signed in) your account identifier and email in Supabase. If you opt in on that submission, we may also store a JPEG screenshot of the visible page (which can include on-screen video previews) and diagnostic metadata such as recent UI actions, console errors, network failure summaries, export log excerpts, app version, and viewport size.
Error and bug reports: When you enable error reporting in Settings or explicitly consent on a feedback submission, we may store error messages, stack traces, route paths, feature areas, session diagnostics, and optional notes in Supabase. Signed-in users must opt in to Settings-based reporting; anonymous diagnostics require per-submit consent. We do not upload raw clip files or IndexedDB blobs with these reports.
Referral program data: If you visit through a referral link, we set HTTP-only cookies with a visitor identifier, referrer slug, and click identifier. We may store hashed IP addresses, user agents, landing paths, and attribution records linking referrers to sign-ups and conversions in Supabase.
Desktop app identifiers: The Windows app may generate and store a device identifier locally for diagnostics and may store window layout and export directory preferences on your machine.
Session management: Signed-in users can view and revoke active sessions. Session metadata is managed through Supabase Auth.
Usage and technical data: Our hosting provider (Vercel) may collect standard server logs and first-party page-view analytics (Vercel Analytics) as described in this policy and our Cookie Policy. We do not run third-party advertising trackers.

3. How we use your information

We use collected information to:

Authenticate you, maintain your session, and manage account settings
Provide Pro cloud clip sync and storage when you opt in
Temporarily stage Schedule / Post now videos on Cloudinary so Buffer can fetch them at publish time, then delete staging after Buffer reports the post sent (plus a short grace window)
Operate Buffer scheduling when you connect Buffer (sync channels, create or edit queue posts, and save ideas through Buffer's API)
Process subscriptions, trials, and referral rewards through Stripe
Operate the hook maker, export studio, timeline editor, recording studio, and results library
Respond to feedback, investigate failures, and improve reliability and security
Route opted-in bug reports to our internal repair workflow (including automated dispatch to our GitHub repository for triage)
Enforce our Terms of Service and prevent referral fraud

We do not sell your personal information. We do not use your uploaded clips to train generative AI models.

4. Lawful bases for processing

Where GDPR or UK GDPR applies, we rely on the following lawful bases (described in plain-language, table-style bullets):

Contract: Processing needed to provide the service you request (account sign-in, Pro billing metadata, optional cloud sync, or Buffer scheduling you enable, core app features you use).
Consent: Processing you opt into, such as error reporting in Settings, optional feedback screenshots or diagnostics, referral cookies when you arrive through a referral link, and other consent-gated features. You can withdraw consent at any time (see Your rights below).
Legitimate interests: Security, fraud prevention (including referral abuse), service reliability, and privacy-oriented first-party analytics on our hosting platform, balanced against your rights and expectations.
Legal obligation: Retaining billing and tax records where required by law.

5. Local-first processing

repli.ac is designed to process video locally whenever possible. Caption rendering, variant generation, timeline export, preview playback, and many stitch workflows run using WebAssembly ffmpeg, canvas APIs, and (on Windows) a bundled native ffmpeg runtime on your device. In these cases, your raw clip data is not transmitted to our servers for processing.

The recording studio captures screen, webcam, and microphone input through your browser or desktop APIs. Recordings are encoded on your device unless you choose to upload them to cloud backup.

Data may leave your device when you: sign in with Google; subscribe to Pro and enable cloud sync; upload clips or recordings to Cloudinary for Pro backup; upload a Schedule or Post now export to Cloudinary schedule staging; connect Buffer and sync channels, schedule posts, or save ideas through Buffer; send feedback or error reports; participate in the referral program; download assets from the results library (hosted on Cloudinary); search royalty-free audio through our server proxy; load fonts from Google; or make standard web requests to our hosting infrastructure.

On Vercel-hosted deployments, server-side hook rendering and desktop-only APIs are unavailable. The Windows desktop app runs a local embedded server for those features.

6. Processors and third-party services

We rely on the following processors and providers to operate the service. Each processes data under its own privacy terms:

Supabase: Authentication, session management, account metadata, subscriptions, Pro cloud clip references, Schedule staging metadata (for example Cloudinary public ids bound to Buffer posts), Buffer connection metadata and encrypted OAuth tokens, feedback, bug reports, referral records, and error-reporting preferences. Media files themselves are not stored in Supabase. Supabase Privacy Policy
Google: OAuth sign-in provider and web font delivery. We do not receive your Google password. Google Privacy Policy
Buffer:When you connect Buffer for scheduling, Buffer authenticates you and processes channel, post, and idea data under Buffer's terms. We send API requests to Buffer using tokens you authorize; Buffer may deliver content to the social networks linked in your Buffer account. Social channel OAuth (for example Instagram, YouTube, or TikTok inside Buffer) is handled by Buffer, not by repli.ac. Buffer Privacy Policy
Cloudinary: Media hosting for (1) optional Pro cloud clip backup and library sync (your 1 GB quota), (2) temporary Schedule / Post now staging uploads so Buffer can fetch your video at publish time, and (3) premade results library video assets. Pro backup and Schedule staging are separate folders and purposes; Schedule staging is deleted after Buffer marks the post sent (plus a short grace window) and does not count toward Pro quota. Cloudinary Privacy Policy
Stripe: Payment processing and subscription billing. Stripe handles your card details directly. Stripe Privacy Policy
Vercel: Application hosting, CDN delivery, serverless API routes, request logs, and privacy-oriented page-view analytics. Vercel Privacy Policy
Freesound:When the in-app audio browser is enabled, search queries are proxied through our servers to Freesound's API. We do not send your clips to Freesound. Freesound Privacy Policy
GitHub: Opted-in bug reports may trigger an automated dispatch event to our private repository containing a report identifier for internal triage. Full diagnostic payloads remain in Supabase. GitHub Privacy Statement

7. Cookies and similar technologies

We use cookies and similar technologies for authentication, referral attribution, desktop mode, and first-party page-view analytics. Details are in our Cookie Policy. Local storage and IndexedDB hold editor state, clips, and preferences on your device. A service worker may cache ffmpeg and font assets locally to speed up exports. You can clear cookies and site data through your browser settings. Clearing local data removes unsynced clips and preferences stored only on your device.

8. Feedback, error reporting, and diagnostics

Feedback and error reporting are voluntary and consent-gated. Nothing is sent in the background without your action on a Send button, except standard web logs and analytics described above.

When you enable error reporting in Settings, you may receive a one-time 7-day Premium trial per account as described in our Terms of Service. You can disable reporting at any time in Settings.

Diagnostic reports may include error messages, stack traces, routes, viewport size, session duration, app version, subscription tier, recent network failures (URL, method, and status only, with auth tokens redacted), export log excerpts, and console error summaries. They do not include raw video files, project blobs, or local filesystem paths. Optional screenshots capture what is visible on screen at submit time and may include video previews or text you entered in the UI.

9. Referral program

If you participate in our referral program as a referrer or referee, we process account identifiers, referral slugs, click and conversion events, reward status, and fraud-check signals to attribute sign-ups and apply discounts or rewards. Referral cookies are described in the Cookie Policy.

10. Data retention

We retain personal data for the periods below, then delete or anonymize it:

Account data: While your account is active, and for a short period after closure to complete deletion requests.
Billing and subscription records: Up to 7 years where needed for tax, accounting, and dispute records.
Pro cloud-stored clips: Until you delete them, disable sync and remove backups, or we complete an account deletion request. This is your durable 1 GB Pro library, not Schedule staging.
Schedule staging media: Kept on Cloudinary until Buffer reports the related post as sent, then deleted after a short grace period so Buffer can finish fetching the file. Post now staging is kept briefly after send, then deleted. Orphaned or unused staging (for example a failed create with no Buffer post id) is cleaned up on a shorter retention window. Staging metadata in Supabase is removed when the related asset is deleted or when we complete an account deletion request.
Buffer connection data:Encrypted OAuth tokens and connection metadata until you disconnect Buffer in Schedule (or elsewhere in the app), or until we complete an account deletion request. Disconnecting removes our stored Buffer tokens; content already in Buffer remains under Buffer's retention and your Buffer account settings.
Feedback and bug reports: About 24 months, unless a longer period is needed to finish an investigation you opened.
Server logs:About 90 days, subject to our hosting provider's rotation policies.
Referral attribution cookies: 30 days from the click that set them.
Local browser and desktop data: Until you clear site data, wipe local storage in Settings, or uninstall the Windows app.

You may delete local data from Settings at any time. To request deletion of cloud account data, contact us using the details below.

11. International transfers

Our service may be accessed from many countries. Personal data may be processed in the United States and other regions where our processors operate data centers, including Supabase, Stripe, Cloudinary (Pro backup and temporary Schedule staging), Vercel, Google, and Buffer (when you connect scheduling). Where we transfer personal data from the European Economic Area, United Kingdom, or Switzerland to countries that are not covered by an adequacy decision, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses (SCCs) and equivalent UK transfer tools offered by our processors, together with any supplementary measures they describe in their documentation.

12. Your rights in the EU and UK (GDPR / UK GDPR)

If you are in the European Economic Area or United Kingdom, you may have rights to:

Access the personal data we hold about you
Correct inaccurate personal data
Delete personal data in certain circumstances
Export (portability) personal data you provided to us in a commonly used format
Object to processing based on legitimate interests, and to restrict processing in certain cases
Withdraw consent where processing is based on consent, without affecting prior lawful processing
Lodge a complaint with your local supervisory authority

Email support@ineedleads.ca with "privacy requests" in the subject line to exercise these rights.

13. Your rights in California (CCPA / CPRA)

If you are a California resident, you may have rights to know/access, correct, delete, and obtain a copy of personal information, and to opt out of the sale or sharing of personal information for cross-context behavioral advertising. We do not sell personal information and we do not share it for cross-context behavioral advertising. See Privacy choices for California-focused notice and how to request access, export, or deletion. We do not use or disclose sensitive personal information for purposes that require a right to limit under CPRA beyond what is needed to provide the service. We will not discriminate against you for exercising privacy rights.

14. Your rights in Canada (PIPEDA)

If PIPEDA or similar Canadian privacy law applies, you may request access to personal information we hold about you, challenge its accuracy, and request correction. You may also ask us to delete or stop using information where appropriate. Contact us at the address below. You may complain to the Office of the Privacy Commissioner of Canada if you are not satisfied with our response.

15. Your rights in Australia (Australian Privacy Principles)

If the Australian Privacy Principles apply, you may request access to and correction of personal information we hold about you, and complain about how we handle your information. Contact us first using the details below. If you are not satisfied, you may contact the Office of the Australian Information Commissioner.

16. Do Not Sell or Share

We do not sell your personal information. We do not share personal information for cross-context behavioral advertising. For a short California-focused notice and how to contact us about privacy choices, visit /privacy-choices.

17. Security

We implement reasonable technical and organizational measures to protect your information, including HTTPS encryption in transit, encrypted storage of Buffer and YouTube OAuth tokens at rest, and access controls on cloud storage. No method of transmission or storage is completely secure; we cannot guarantee absolute security.

18. Children's privacy

repli.ac is for users 13 years of age or older (or the higher minimum age required in your jurisdiction). We do not knowingly collect personal information from children under 13. If you believe a child has provided us data, contact us and we will delete it promptly.

19. Changes to this policy

We may update this Privacy Policy from time to time. We will revise the "Last updated" date at the top of this page. Material changes may be communicated through the app or by email where appropriate. Continued use after changes constitutes acceptance of the updated policy.

20. Contact us

Questions about this Privacy Policy or privacy requests (access, correction, deletion, export, opt-out, or consent withdrawal) may be sent to support@ineedleads.ca. Please put "privacy requests" in the subject line so we can route your message correctly. We will respond within a reasonable timeframe required by applicable law.