Brarie · private pilot
Privacy Policy
Draft pending legal review · Effective date: [Effective date]
Service operator: [Company legal name]
Registered address: [Registered address]
1. Data we use to run Brarie
We store account information such as your email and any name you provide; workspace and brand names; memberships, invitations and access roles; uploaded files, previews and metadata; collections, versions, recorded usage rights, share settings and recipient email addresses. We also record service activity and storage and AI usage to operate the library, enforce access and limits, and help investigate problems.
These records support account access, file organization, search, sharing and support. Team members may see account information and content where their workspace or brand permissions allow it.
2. Private storage and access
Account records, workspaces, brands, uploaded files and metadata are stored in Lovable Cloud. File storage is private. Database and file access rules deny access unless an applicable permission allows it. Workspace, brand and share permissions control who can read content; permitted file access uses short-lived signed links.
Private storage is not a claim of end-to-end encryption. Do not share a file with someone unless you intend them to receive it.
3. Optional Brarie AI
Brarie AI is off for a brand unless a brand admin enables its suggestion or search controls. Workspace owners and admins can also disable AI across the workspace; workspace availability alone does not enable a brand’s AI controls.
When visual suggestions are enabled, preview images (a preview frame for video) and limited brand vocabulary are sent through the Lovable AI Gateway to an AI provider for tag and description suggestions. Original files are not sent for visual analysis. When search interpretation is enabled and used, search text, field labels and choices, and limited brand vocabulary are sent to an AI provider to interpret the search.
AI results are suggestions, not approvals, permissions or legal clearance. Brarie records task usage and count-only review feedback. Brarie does not train a Brarie-wide model on your private content. This draft makes no guarantee about provider-side retention or training practices; those terms have not been verified for this pilot.
4. Google Drive and Dropbox
Connections are optional and available only when the provider is configured. You choose the provider account and folders to bring into Brarie. Provider permissions are read-only and can cover more than the selected folders; Brarie uses your folder selections to scope imports and sync. Google permissions include sign-in identity information and Drive read-only access. Dropbox permissions include account information, file metadata and file content read access.
Brarie stores connection tokens encrypted on the server, not in the browser. Files in Google Drive or Dropbox are never modified by Brarie. Disconnecting destroys Brarie’s stored tokens and stops future connection access; files already imported into Brarie are not automatically deleted. You can also revoke authorization through the provider.
Brarie’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5. Shares and recipients
Brarie stores recipient email addresses and share configuration to enforce access to selected files and versions. Invite-only shares require the recipient to sign in with a verified allowed email address. Shares can have an expiry, can be revoked, and can control original-file downloads. Recorded rights are checked when content is delivered.
Anyone with an explicitly created public link can view the frozen shared collection or brand home without an account until expiry or revocation. Public links expire after 14 days by default and no later than 30 days. Original downloads are off by default and limited per link when enabled. We store only a hash of the access token, count views and original-download allocations, and use short-lived hashed IP-address counters to limit abuse. Public-link pages do not use analytics or tracking scripts.
Revocation and expiry prevent new authorized access, but previously issued short-lived preview links may work until they expire and downloads already underway may finish. Downloaded files cannot be recalled or deleted from a recipient’s device by Brarie.
6. Email and browser storage
We use transactional email for account confirmation, password recovery and workspace invitations where delivery is configured. We do not send marketing email.
Browser storage is used for your sign-in session and per-device preferences, including your selected brand and display preferences. This pilot does not use browser storage for advertising or marketing tracking.
7. Data requests and account deletion
Contact support@brarie.com to request a data export, data deletion or account deletion. Account deletion is handled on request, not through a self-service button. We may verify your identity and authority before responding, particularly for content belonging to a shared workspace or brand.
Removing a connection is not the same as deleting imported files. Removing content from Brarie cannot remove copies already downloaded by others. We do not promise a deletion deadline or backup-retention period in this draft; any limitations relevant to your request will be explained during support handling.
8. Changes and contact
We will notify you by account email of material changes to this policy and identify the effective date. For privacy questions, support or feedback, contact support@brarie.com.