We use Umami to understand visits to public pages and actions such as starting sign-in, connecting a channel, opening checkout and observing an active subscription or successful publication. An observed subscription is not treated as a newly completed purchase. When analytics is enabled, checkout also carries the broad acquisition category and approved landing path so our server can attribute a confirmed payment after Stripe verifies it. These attribution fields contain no raw referral URL or campaign parameters. We also measure public-page loading, layout stability and interaction responsiveness (LCP, CLS and INP) with a coarse mobile, tablet or desktop category. These performance events contain numeric values, an approved public page path and a random measurement identifier used only to update that document’s metric; they exclude element text, selectors, media URLs and individual performance-entry details. The first public landing page and a broad acquisition category are retained for the browser session. Event payloads exclude email addresses, account identifiers, captions, credentials and URL query strings. Private routes are recorded as a generic account page. Analytics and checkout attribution respect browser Do Not Track and Global Privacy Control signals, as well as the Umami opt-out.
On public pages and the sign-in page we also use Umami session replay and heatmaps to find where a page is hard to use. A replay rebuilds the page as your browser displayed it, with your pointer movement, clicks and scrolling, and the page address including any campaign parameters in it. A heatmap stores click positions and scroll depth for a page address. Anything typed into a form field is masked in your browser before it is sent. The working area of each free tool and of the API playground is left out of replays, so the text, files and API keys you enter there, and the results built from them, are never recorded. The recorder is not loaded in your signed-in workspace, on an address that carries a sign-in or authorization code, or when Do Not Track, Global Privacy Control or the Umami opt-out is on; opening your workspace from a recorded page loads it again without the recorder. Replays and heatmaps are stored in Reeling’s self-hosted Umami.
Last updated: November 11, 2026
Welcome to reeling.app ("Reeling," "we," "our," or "us"). We are committed to protecting your personal information and your right to privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use reeling.app and our social media management platform. reeling.app uses the TikTok API to publish and manage content on behalf of authorized users.
We use the information we collect to:
We may share your information with:
We do not sell, trade, or otherwise transfer your personal information to third parties for marketing purposes.
We implement appropriate technical and organizational security measures to protect your personal information. This includes encryption, secure servers, and regular security audits. However, no method of electronic storage is 100% secure, and we cannot guarantee absolute security.
You have the right to:
We use cookies and similar tracking technologies to track activity on our platform and hold certain information. You can control cookies through your browser settings, but disabling them may limit your ability to use certain features of our platform.
Our services are not intended for individuals under the age of 13. We do not knowingly collect personal information from children under 13. If you become aware that a child has provided us with personal information, please contact us immediately.
Your information may be transferred to and processed in countries other than your own. We ensure appropriate safeguards are in place to protect your information in accordance with this Privacy Policy.
We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date. We encourage you to review this Privacy Policy periodically.
Reeling uses YouTube API Services. When you connect a channel, we access and store its ID, name, handle and profile image, along with encrypted authorization tokens. We use these to identify the channel you selected and upload videos at your request or scheduled time. We store upload results so you can find your videos and resolve failures.
Your selected video, title, description, visibility and audience settings are sent to YouTube when you upload or schedule a post. Infrastructure providers host our application, database and uploaded files. Reeling does not sell Google user data, use it for advertising, or use it to train general-purpose AI models. Reeling’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Disconnect a channel on the Channels page to remove that project’s saved connection and tokens. The same channel can remain connected to other projects. You can revoke Reeling’s Google access for all projects in Google’s security settings. Disconnecting Reeling does not delete videos already uploaded to YouTube; manage those in YouTube Studio.
Contact mariano@reeling.app to request deletion of your stored videos, post history or account data. Database backup copies expire after 14 days. Google processes information under its Privacy Policy. Reeling uses browser storage for your sign-in session and project selection, and a short-lived cookie to secure channel connections.
When you connect TikTok, Reeling stores your account ID, name, handle, profile image and encrypted access and refresh tokens for the selected project. We use them to identify your account, retrieve your current publishing settings, send videos you authorize and check their status. TikTok fetches your selected video from our media hosting service.
“Finish in TikTok” sends the video to your TikTok inbox so you can edit and publish it there. Direct Post sends the caption, visibility, interaction settings and content disclosures you select. We save the publishing reference and result in your post history. Disconnecting on the Channels page removes that project’s connection and tokens; it does not delete videos already sent to TikTok. You can remove Reeling’s access in TikTok’s app permissions settings. Contact mariano@reeling.app to request deletion of stored media, post history or account data; database backups expire after 14 days.
When you connect Instagram, Reeling stores your professional account’s ID, handle, name, profile image and encrypted authorization token for the project you select. We request account information and content publishing access to publish Reels you submit or schedule. Your video, caption and feed preference are sent to Instagram, and Instagram fetches the uploaded video from our media hosting service. We store the publishing result and link in your post history.
Disconnect the account on the Channels page to delete that project’s connection and token. To remove access across all projects, revoke Reeling Channels in Instagram’s Apps and Websites settings. Disconnecting does not delete Reels already published; manage them on Instagram. Contact mariano@reeling.app to request deletion of your stored media, post history or account data. Database backups expire after 14 days.
If you have any questions about this Privacy Policy or our data practices, please contact us at:
reeling.app / Reeling Support
Email: mariano@reeling.app
Website: https://reeling.app