Privacy Policy

Roostr is operated by Fleapo. For any question about this policy, or to make a request about your data, contact avilash@fleapo.com.

• Account information — name, email address, and the role you hold (brand, creator, or agency). Email is how we sign you in; we do not store passwords.
• Profile information you choose to provide — for creators, this includes demographic answers, interests, portfolio links and uploaded sample work; for brands and agencies, company details and logo.
• Content you upload — product images, briefs, and submitted videos.
• Messages you send through the platform.

A brand may connect its Meta advertising assets to Roostr so that approved creator videos can be published as ads on the brand’s behalf. When a brand administrator authorizes that connection, we receive and store:

• The ad account identifier for the ad account they selected.
• The Facebook Page identifier for the Page they selected, and the Business Portfolio identifier if the assets belong to one.
• An access token permitting us to act on those assets. It is encrypted at rest and is never displayed, exported, or shared.
• An app-scoped user identifier for the administrator who authorized the connection. This is specific to Roostr, is not that person’s public Facebook identity, and cannot be used to identify them on other services. We store it so that if they later remove Roostr from their Meta settings, we can tell which connection they meant.
• Advertising performance metrics for the brand’s own ads — for example impressions, video views, watch time and link clicks.

We do not receive, request, or store the personal Facebook or Instagram profile data of anyone who sees or interacts with those ads.

A brand may install the Roostr app on its Shopify store so that its product catalogue syncs to Roostr and its sales can be attributed to the creators whose ads led to them. When the store owner approves the app in Shopify, we receive and store:

• An access token for the store. It is encrypted at rest and is never displayed, exported, or shared.
• The store’s products — titles, descriptions, images, variants and their availability — so creators can choose what to feature.
• Order and refund records — order and refund identifiers, totals, currency, line items, discount codes, and the click identifier described below. We do not store the customer’s name, email address, phone number or addresses from these orders.
• Shipment tracking for product samples the brand sends to creators through Roostr.

When a brand turns on the Roostr app embed in its Shopify theme, a small script runs on the store. If a shopper arrived through a Roostr ad link, and the store’s cookie consent settings show the shopper allowed marketing and attribution, the script keeps a random click identifier in their browser for up to 30 days and adds it to their cart, so the purchase can be credited to the right creator. Without that consent, nothing is stored. The script also records whether the shopper allowed their data to be shared with third parties; we report an attributed purchase to the brand’s own Meta dataset only when they did.

When someone follows a Roostr ad link, our link redirector records when it happened, which ad it was, and technical details of the request: IP address, browser user agent, language, referring page, and Meta’s click identifier when present. We use these to tell automated traffic apart from real visitors and, for Meta’s click identifier, to report an attributed purchase to the brand’s own Meta dataset. After 90 days we delete the IP address, language, referring page and Meta click identifier. We keep the user agent, which on its own identifies no one, because our filtering of automated traffic uses it.

When a creator requests a product sample and the brand approves it, Roostr creates a $0 order for the sample in the brand’s Shopify store. It includes the creator’s name, shipping address, phone number and email address, so the brand can ship it and Shopify can send delivery updates. This is the only change Roostr makes to a brand’s store.

Meta advertising data is shown only to the business that owns it. A brand’s ad account identifier, Page identifier and performance figures are visible to members of that brand’s own team on Roostr, and to an agency only where the brand has an active partnership with that agency and the data concerns work done under it. Creators see performance figures for their own submitted videos. No brand can see another brand’s advertising data.

We do not sell personal data. The one thing we send to an advertising platform is an attributed purchase reported to a brand’s own Meta dataset, at that brand’s request and only when the shopper allowed sharing with third parties. It carries the order value and Meta’s own click identifier, and no name, email address, phone number or postal address.

• Meta access tokens — until the connection is removed, at which point the stored token is deleted outright rather than archived.
• Ad account, Page and app-scoped user identifiers — for as long as the connection exists, and after removal only where we must retain a record of work already performed.
• Account and profile data — for as long as the account is open, and for a limited period afterwards where we have a legal or accounting obligation to keep it.
• Submitted videos and messages — retained as records of the collaboration between a brand and a creator.
• Shopify access tokens — until the app is uninstalled from the store or the brand disconnects it in Roostr, when the stored token is deleted.
• Ad click details — the IP address, language, referring page and Meta click identifier for 90 days; the rest of the click record for as long as the attribution records it supports.
• Order records — kept as financial records, because creator commissions were calculated from them. They contain no customer identity.
• An install not yet confirmed — if a store installs Roostr and no brand confirms it within an hour, the held access token is deleted.

Access tokens are encrypted at rest with AES-256-GCM. Sessions are server-side records that can be revoked. Access to production data is limited to personnel who need it to operate the service.

We will update this page when our practices change, and will revise the date at the top. For material changes affecting existing accounts, we will provide notice through the product.