Privacy Policy

1. Data processed locally

Reflow runs in your browser. The SRT text you paste or upload for reflow is processed on your device and is not sent to our servers for reflow. Reflow is rule-based, uses no AI, and makes no external API calls.

2. Data uploaded for Snap to Cuts

If you use Snap to Cuts, your selected video file and one SRT are uploaded to secure temporary storage and processed on our servers (including FFmpeg-based visual-cut detection) to align caption timing. If you turn off “Reflow captions before Snap to Cuts”, the source SRT you provided is uploaded as-is; if reflow is on, the generated reflowed SRT is uploaded. Your video is uploaded only when you start a Snap to Cuts job. No AI or third-party language model processes your captions or video.

3. Temporary storage and retention

Uploaded videos, uploaded SRTs, generated SRTs, job result files, and any troubleshooting files you choose to share through feedback are temporary. They are set to expire about 24 hours after processing or submission, so you can run the job and download the result. Automatic cleanup may be delayed, which is why we describe these files as set to expire rather than instantly deleted. We do not use your uploaded video or captions to train any model.

4. Account data (Firebase Auth)

If you sign in, authentication is handled by Google Firebase Authentication, which processes your account identifier and email address to manage sign-in. We reference your account by its Firebase user ID. Email and password accounts can request a password reset email when needed.

5. Billing data

Snap to Cuts is free during the current beta, and no payment is collected at this time. If paid plans launch later, payments will be processed by Stripe, which handles payment details; we would not store full card information and would keep only opaque, non-sensitive references needed to know whether a subscription is active.

6. Usage metrics

We record content-free usage counters (for example, how many times reflow was run or a Snap to Cuts job was created), fair-use counters with the metadata needed to show when a quota resets, records of any request for additional jobs, and beta access and admin control settings, to understand overall usage and operate the service. These records never include your SRT or caption text, cue text, filenames, video content, URLs, signed download links, tokens, or error details. Anonymous usage is aggregated and not tied to an identity; signed-in usage is associated with your Firebase user ID only. An internal admin dashboard shows these counters to the operator.

7. Feedback you submit

If you send feedback through the in-app form, we store your message, an optional category, and any reply email you choose to provide, so we can review and respond. Feedback is kept in a separate store from usage metrics. Please do not include private caption or video content in your message. We do not capture screenshots of the page.

Troubleshooting sharing is optional and off by default. When you send feedback you may explicitly opt in to share the relevant files so an issue can be looked into. For Snap to Cuts, if a job exists, you can let an operator access the files already uploaded for that job while they remain within their normal retention window. For Reflow, you can upload the current browser-side source SRT and reflowed SRTs together with your feedback, whether or not you are signed in.

You may also optionally attach a small number of your own support files to feedback — for example a screenshot or a small text, SRT, or CSV file — whether or not you are signed in. Attachments are only ever the files you select yourself; we do not capture screenshots automatically. Attached files are stored temporarily so an operator can review the issue, and an operator downloads them through short-lived links.

Only files you explicitly choose to share or attach are shared. Operator access uses short-lived download links and works only while the files remain available. Shared troubleshooting files and feedback attachments are set to expire on a short schedule, about 24 hours after submission, and we do not promise instant deletion.

8. No AI transcript processing

We do not send your captions, transcripts, or video to any AI or third-party language model for processing. Reflow is rule-based and local; Snap to Cuts performs video analysis only.

9. No sale of personal data

We do not sell your personal data.

10. Cookies and local storage

We limit browser storage to what the app needs to function: the cookies and tokens required for authentication and session flows handled by Firebase. Your SRT, caption, and video content is never written to browser storage. We do not use advertising or cross-site tracking cookies.

11. Data deletion, your rights, and contact

To request deletion of your account data or feedback, or to ask a privacy question, contact us at ryan@ryansauve.com. We will delete account-linked data we hold on request; uploaded job files are short-lived and expire automatically as described above. We operate from Alberta, Canada. Depending on where you live, applicable privacy laws (such as Canada’s PIPEDA and Alberta’s PIPA) may give you rights to access or request deletion of your personal data; contact us to exercise them.

12. Changes to this policy

We may update this policy from time to time. Material changes will be reflected by updating the effective date above.