Cookie Policy & Preferences

Cookies are small values your browser can send with requests. Local storage keeps values on this device until removed; session storage generally lasts for a tab session. This policy covers all three. Some storage is needed for sign-in, security, and features you request. Optional activity measurement and referral attribution remain off unless you enable them.

You can reject optional uses, accept them, or select each category independently. Continuing to browse, closing the preferences dialog, or creating an account does not mean you accepted optional tracking. The same choices are available without signing in.

Authentication and security cookies support login, session verification, and authorized requests. These are managed by the backend authentication service. Their exact deployed names, domain attributes, and lifetimes depend on the backend configuration and must be verified in the production inventory.

bereel_consent is a first-party preference cookie that records the policy version, time of your choice, and the two optional categories. It lasts up to 180 days, uses SameSite=Lax, and is Secure over HTTPS. It contains no account ID. It is readable by the app to apply your choices. We may ask again when it expires or the consent version changes.

Project selection, editing handoffs, selected styles, and requested interface preferences use local or session storage. These values support the functions you use and are not advertising identifiers. Use the corresponding controls to change preferences or clear site data to remove them. Clearing all storage can sign you out and reset unfinished work or interface choices.

Activity analytics: when enabled, Bereel sends a signed-in presence request while the application is visible, generally every five minutes and on visibility changes. It uses your existing authenticated session rather than a separate analytics cookie. Rejecting this category stops these requests through this frontend. It does not prevent necessary security logging, requested generation, collection of social metrics for accounts you connect, or Microsoft Clarity session recordings described below.

Referral attribution: when enabled and you follow a valid referral link, the service can record that visit and set ov_ref, a first-party HttpOnly referral cookie with a documented lifetime of up to 30 days. It associates a qualifying signup or purchase with a referral. The link handler asks for a cookie choice before contacting the referral service when no current choice exists. Rejection lets you proceed to signup without referral attribution.

Microsoft Clarity is used to record how signed-in users move through onboarding and the product (session replays, heatmaps, and custom tags such as email and page). Clarity sets its own first-party cookies (_clck, _clsk). This frontend currently starts Clarity even if the cookie banner is ignored, rejected, or not shown. That is a temporary product setting; treat it as product-usage analytics, not advertising, until it is wired to Cookie settings.

The current client uses the following named values. ‘Local’ values have no automatic expiry in this code; ‘session’ values normally end with the tab session or are removed after use.

• bereel_consent — cookie, 180 days: remember the optional choices shown above.
• _clck, _clsk — Microsoft Clarity first-party cookies: persist a Clarity user id and the current recording session.
• ov_ref — optional referral cookie, up to 30 days: signed referral attribution; removed on rejection through Cookie settings.
• bereel_active_workspace_id — local: route requested work to the selected project.
• theme; onvideos.sidebar.collapsed; library:view-mode — local: chosen theme, navigation layout, and library view.
• onvideos:home-looks-density; onvideos:home-looks-density-chosen; onvideos.recent-colors; onvideos:first-four-steps:* — local: layout choice, recent selected colors, and dismissed setup guidance.
• onvideos_oauth_pending; onvideos_oauth_channel; onvideos_tiktok_connect_tab — session: resume a requested social-account connection and its chosen connection step.
• reels-studio-bootstrap; onvideos:look-pouch; onvideos:home-feed-return; onboarding.reveal; for-you:* — session: editor handoff, selected looks, return position, onboarding transition, and stable recommendation ordering.

Open Cookie settings from the legal footer on account pages or Settings, or return to this page. Select Reject optional to turn off both optional categories, or save individual choices. Rejection removes the app-origin referral cookie and stops future optional presence requests. Other open tabs refresh their choices through a browser notification or when focused. Withdrawal does not retroactively erase records already lawfully created; use the privacy contact for an erasure request.

Choices apply to this browser and site, not automatically to other devices or browsers. Clearing the preference cookie or using private browsing may cause the question to reappear. If saving is blocked, the application reports the problem and does not treat the selection as saved. Browser controls can block or delete cookies, but blocking necessary storage can prevent sign-in and other requested functionality.

Payment checkout and social authorization may take you to another provider’s site. Those providers control their own cookies and notices. Embedded or fetched third-party media may also involve network requests necessary for a preview you choose to open. Bereel’s preference controls do not operate the cookie settings of an external website.

For questions or requests about information processed through cookies, use the privacy contact on this page and see the Privacy Policy. The operator must verify backend cookies and infrastructure against this inventory before treating the policy as final.