Privacy & deletion

Data processed

BraidLane processes the catalogue you submit, the generated diagnostics and package, an essential anonymous session identifier, technical request metadata, checkout references, general feedback you choose to submit, and structured import outcomes you voluntarily report. It does not require store credentials and does not write to a store.

If you activate a pilot invitation, an essential invitation-choice cookie remembers your choice for up to 90 days to prevent unintended paid checkout. You can change that choice. It contains no invitation code or catalogue content. The encrypted invitation context is usable for up to 30 minutes; a service restart can interrupt it. Your review and already granted access remain separate, and you can retry the invitation.

Optional sign-in

When available, optional sign-in uses Supabase Auth to verify a Google account or an email sign-in link. BraidLane uses your verified email address and provider account identifier to recognize your session. Google may also supply basic profile details, such as your name or profile photo. BraidLane requests identity, email and basic-profile permissions only—not Gmail, Drive or store access. For email sign-in, your address is sent to Supabase to send a single-use verification link. Catalogue files are not sent to Supabase or Google as part of sign-in.

Sign-in cookies

Essential first-party cookies support sign-in and browser security. The server sets them for up to seven days at a time; a verified session can renew them. Temporary sign-in-flow cookies last up to ten minutes. On HTTPS, these cookies are Secure and HttpOnly. These limits do not specify when the identity records held for your account are deleted.

Automatic column suggestions

During import, the selected table’s headings and known field meanings, up to three aligned redacted source rows, and the selected shop and settings may be sent automatically to OpenAI to suggest meanings for unfamiliar columns. The full file is not sent. Empty columns and recognized unsupported source policies do not need this review. Formula-like content, common contact details, URLs, and secret-like values are removed where detected. Very wide tables may need manual review when that limited excerpt cannot be sent safely. Suggestions do not change your CSV until you confirm them.

If you ask a free-form question in the catalogue Guide, your question and a short review summary may be sent to OpenAI to understand it. This can include mapped field names and counts, selected shop settings, issue and omission codes, and the current decision. For a current product-tax choice or while preparing another shop, the summary can also include redacted product names, SKUs, descriptions and source values relevant to the displayed question, your current choices, and their import consequences. Common contact details, URLs, secret-like values and formula-like content are removed where detected. The excerpt is bounded; if the relevant evidence cannot fit safely, the Guide uses the local explanation. The complete file is not sent. The Guide cannot apply or approve a change or unlock files for you.

Purpose and providers

Data is used only to diagnose the source, generate the requested package, maintain payment authorization state, support optional sign-in, prevent abuse, investigate voluntary feedback, and provide support. Fly.io hosts the application and encrypted in-product feedback, Stripe handles hosted checkout, Supabase Auth and Google handle optional sign-in as described above, Google Workspace receives support and reply-request email, and OpenAI handles the automatic mapping suggestions described above. BraidLane does not sell catalogue data or use advertising analytics.

Retention and deletion

Without an account, source files and packages expire after 60 minutes; while the service is healthy, encrypted application copies are purged within 60 seconds after expiry. Catalogues saved to a verified account are retained by default until you delete them or the account/data lifecycle applies. The current limit is 5 catalogues and 64 MiB per account. Delete removes catalogue data immediately; minimal provider checkout cleanup may remain pending during an outage. This beta does not promise permanent, backup-restorable or unlimited storage. In-product feedback is encrypted at rest and retained for 90 days. General feedback contains your category and optional note plus privacy-minimized workflow context. A voluntary import outcome contains the target, self-reported status, failure stage and available evidence type, non-commercial destination settings, aggregate counts, and server-derived diagnosis and package references. No store name, URL, error text, rejection file, catalogue value, payment identifier, or session identifier is retained in that outcome. Deleting the package does not delete a submitted voluntary outcome, which follows its own 90-day retention window. Email sent to request a reply remains in BraidLane’s business inbox until manually deleted or you request its deletion. Provider records and encrypted infrastructure backups may follow each provider’s own legal and security retention requirements.

After verified sign-in, the active unexpired run can be attached to your account and new runs are retained there by default. Signing in does not grant a free export or change the payment state of a run.

Operational history

To deliver and troubleshoot your catalogue workflow, BraidLane retains a structured history of server operations, results, technical error codes, timings, selected platforms and aggregate counts. Pseudonymous browser, account and diagnosis references connect those operations to feedback. This history contains no automatic catalogue values, filenames, IP addresses, sign-in links, payment credentials, request URLs or raw error messages. It is used only by BraidLane for operating, protecting and improving the service, on the basis of our legitimate interest in providing a reliable service.

Operational diagnostics include page changes, blocked controls and browser error categories. They use the existing private session and are retained for 90 days. They do not record screens, keystrokes, catalogue contents or form values, and are not sent to an analytics provider.

For invited pilots, an organization reference assigned by BraidLane may link participating accounts to manage their invitations. It is not inferred from your email address or catalogue. Campaign source is not linked to your account or catalogue activity.

Operational events are encrypted on the existing application volume and available for 90 days; expired daily segments are physically removed within a further 24 hours while the service is running. The capacity is bounded and collection gaps are reported internally. Deleting a catalogue does not delete this separate operational history. Contact us to exercise access, objection or deletion rights using your account or support reference. This is not an off-site backup or a promise of complete browser capture. Free invitation use is retained separately to prevent repeated redemption; deleting a run does not renew an invitation.

Safe use

Do not include personal, regulated, confidential, or customer data in catalogue uploads. Use legally shareable ordinary catalogue data. No EU-only hosting or zero-data-retention promise is made.

Your requests

You can delete each retained run from the account menu. For account access, correction, objection, or deletion questions, contact contact@braidlane.com and identify your sign-in email address. There is currently no self-service account deletion control. Signing out hides retained runs on that browser but does not delete them or the account. Do not send passwords, sign-in links, or the catalogue itself; a separate secure channel must be agreed before sharing a catalogue.