We collect only the information we need to operate the Service.
§ 2.1Account information
When you create a Reelcycler account we collect your email address and a salted hash of your password. We use these to authenticate you, to send transactional email (password resets, billing notices, service announcements), and to contact you about your account. We do not store your password in plain text.
§ 2.2Content you upload
When you create a Post, we collect the video file you upload, the default caption you write, the Platform accounts you select as publish targets, and any per-target caption overrides. We store the video on Amazon S3 in the us-west-2 region for the lifetime of the Post so that we can publish it and retry on failure, and we delete the video from S3 when you delete the Post or close your account. We do not analyze your video content, train any model on it, or use it for any purpose other than publishing it on your instruction.
§ 2.3OAuth tokens and connected Platform metadata
When you connect a Platform account through the relevant OAuth flow, the Platform issues us an access token (and, where applicable, a refresh token) scoped to your account. We store these tokens encrypted at rest in our database (using Rails Active Record encryption) and use them only to publish content you have explicitly asked us to publish, to refresh expired tokens, and to read the minimum metadata required to display your connected accounts and to validate publish eligibility.
We request only the scopes we actually need:
- Meta / Instagram (Graph API). Scopes such as
instagram_basic, instagram_content_publish, pages_show_list, and business_management (final scope set subject to Meta App Review). We use them solely to (a) identify the Instagram Business or Creator account linked to your Facebook Page so we can display it in Reelcycler, and (b) create and publish a Reels media container on that account when you initiate a publish. We do not read your followers, your DMs, your Insights, or other people’s content. We do not store Insights or analytics data.
- Google / YouTube (Data API v3). Scope
https://www.googleapis.com/auth/youtube.upload, used solely to upload a video to your YouTube channel and to set the title, description, and Shorts-eligible metadata you have provided. We may also use a userinfo.email / userinfo.profile scope at the OAuth step solely to display which Google account you have connected. We do not request youtube.readonly, youtube.force-ssl, or any other YouTube scope in the MVP.
- TikTok (Content Posting API). Scopes
video.upload and video.publish (and user.info.basic to display the connected account handle). We use these solely to upload and publish a video on the connected TikTok account when you initiate a publish.
Reelcycler’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular, Reelcycler:
- only requests the YouTube
youtube.upload scope, which is the minimum scope needed to publish on your behalf;
- uses data obtained from Google APIs only to provide the user-facing feature you initiated (uploading a Short to your YouTube channel);
- does not transfer that data to others except as necessary to provide that feature, to comply with applicable law, or as part of a merger, acquisition, or asset sale in which the recipient is bound by terms at least as protective as this policy;
- does not use that data for serving advertisements, including retargeting, personalized, or interest-based advertising;
- does not allow humans to read that data, except (i) with your affirmative consent for specific files, (ii) for security purposes (e.g., investigating abuse), (iii) to comply with applicable law, or (iv) where the data has been aggregated and anonymized and is used for internal operations; and
- does not use that data to develop, improve, or train generalized AI or machine-learning models.
§ 2.4Billing information
Subscriptions are processed by Stripe. We do not see or store your card number, CVC, or full bank-account details. We store the Stripe customer ID, subscription ID, plan, status, and current period end returned by Stripe so that we can show your billing state in Reelcycler and gate the Service on subscription status. We receive billing event notifications from Stripe by webhook and verify their signatures before acting on them. For Stripe’s own processing of your payment data, see Stripe’s Privacy Policy at https://stripe.com/privacy.
§ 2.5Usage telemetry
We collect basic operational logs from the Service — for example, which API endpoints you call, HTTP status codes, error stack traces, publish attempts and their outcomes, and aggregate counts of Posts per user — so we can keep the Service running, diagnose failures, prevent abuse, and improve reliability. These logs include your account ID and IP address. They do not include the contents of your video or your captions.
§ 2.6Cookies on the marketing site
reelcycler.com uses strictly necessary cookies for sign-in, session management, and CSRF protection. We may also use a small number of first-party analytics cookies to measure aggregate marketing-site traffic; where required by law, we will request your consent through a cookie banner before setting non-essential cookies. The Reelcycler mobile application does not use third-party advertising SDKs, does not include any tracking identifier used across other companies’ apps and websites, and does not enable Apple’s App Tracking Transparency tracking.
§ 2.7Information we do not collect
We do not collect your real name, date of birth, address, phone number, government ID, precise geolocation, contacts, photos beyond the videos you upload, microphone audio, biometrics, health data, or financial-account numbers. We do not buy data about you from data brokers.