Privacy policy

What data we collect, why, and what you can do about it. Written plainly — no lawyer paragraphs unless we have to.

Last updated: 2026-06-06 (clarified the hardware settings included in manually attached support bundles).

Who we are

FFB-Bridge is developed and published by Rohsam Inc., a software publisher based in Toronto, Ontario, Canada. Rohsam Inc. operates ffb-bridge.com and the FFB-Bridge download and update list. You can reach us about any privacy matter at supportffb-bridge.com. Publisher verification details are available at rohsam.com/legal.

What we collect

When you sign up for the download email, we store:

  • Your email address — so we can send you the confirmation link and, if you consent, occasional release-related updates.
  • Your IP address at signup — logged once, for abuse triage only. Never shown publicly, never shared.
  • A random token we generate to authenticate your confirmation and download links. It has no link to your personal identity beyond your signup row.
  • Signup, confirmation, and download timestamps — so we know when a subscriber confirmed and how many downloads they've used against their quota.

When you send feedback through the feedback form, we store the report text, optional category, optional reply email, submission timestamp, user-agent string, and a keyed hash of your IP address for abuse prevention. We do not publish feedback reports.

If you attach screenshots, we store the uploaded image files so we can inspect the bug or UI state you chose to share. Screenshots may contain anything visible on your screen, so review them before sending.

If you attach or upload a support bundle, we store the ZIP and parse its allow-listed text files into structured triage data: app version, build hash, operating system, hardware identifiers, simulator connection details, active tuning values, hardware-settings.json details (force-feedback backend, smooth steady forces, axis polarity, pitch/roll swap, and compatibility settings), Support checks, and warning/error log lines. Passwords in SimConnect config are stripped by the app before the bundle is created. See Support bundles for the full file list and limits.

If you choose to make an optional Support the Dev payment, checkout is hosted byStripe. Rohsam Inc. does not receive or store full card numbers. Stripe may provide us payment records such as amount, currency, payment status, Stripe session/payment identifiers, receipt email, and limited billing details needed for receipts, refunds, accounting, tax, fraud prevention, or support.

Outside that optional Stripe-hosted payment flow, for ordinary site visitors, download subscribers, and desktop app users, we don't collect names, addresses, phone numbers, credit cards, flight data, or any telemetry from the desktop application. The desktop app itself makes no outbound network calls except to your local simulator. It does not automatically upload flight data or settings; you choose whether to attach screenshots or a support bundle to feedback. See the FAQ on the home page.

Language choice and translations

The website is available in multiple languages. Language pages use visible URL prefixes such as /fr-ca/, /de/, and /ja/. When you explicitly choose a language, we store one first-party preference cookie named ffb_lang for up to 180 days so the bare home page can remember that choice. The cookie contains only the selected language code, such as fr-CA. It is not a tracking ID and is not shared with anyone.

Site translations are automatically generated and may contain mistakes. If you send translation corrections or language requests through the feedback form, we handle that message under the same feedback rules described on this page.

Separately, we may directly invite a very small number of specific people to review translations. This is not a public feature, is not advertised on the site, and is not visible or available unless we personally send someone an invite link. For those invited reviewers only, we store the reviewer's name, email address, review language, invite status, expiry or revocation timestamps, temporary review cookie, and any translation notes they submit. We use that information only to manage translation review and improve localized site text.

What we don't do

  • We don't use third-party analytics that set cookies or track you across sites. The site uses self-hosted Umami for aggregate page-view counts, referrers, device type, and browser/OS summaries; it is cookie-free and does not profile individual visitors. Query strings and URL fragments are excluded from analytics, and browser Do Not Track is respected.
  • We don't sell, rent, or share your email address with any third party for marketing. We only use service providers needed for services you request, such as email delivery and optional Stripe-hosted payment processing.
  • We don't send you marketing on behalf of anyone else.

Why we collect it

Three reasons:

  • Delivery of the download links you asked for — your signup is the explicit request for this service.
  • Release updates (when you tick the consent box): new releases, breaking changes, bugs we discover after you've installed. Low volume — important product updates, not general marketing.
  • Abuse triage, if we see a signup pattern or feedback upload pattern that looks like an attack.
  • Support and debugging, when you choose to send feedback, screenshots, or a support bundle.
  • Optional support payments, when you choose to contribute through Stripe, for payment processing, receipts, refunds, accounting, tax, fraud prevention, and related support.
  • Language preference, when you choose a site language and ask the site to remember it on future visits.

Feedback reports are voluntary. You decide whether to include an email address, screenshots, or a support bundle.

We will never send you anything outside of those categories without separate, explicit consent.

Consent and withdrawal (CASL)

Under Canada's Anti-Spam Legislation, we only send commercial electronic messages to people who have given express consent. That's the checkbox on the signup form. You can withdraw consent at any time:

  • Click the Unsubscribe link at the bottom of any email we send you. That instantly marks your row as opted out and prevents any further send.
  • Or email supportffb-bridge.com from the subscribed address with "unsubscribe" in the subject. Processed within one business day, always faster than the 10-business-day CASL maximum.

Changed your mind after unsubscribing? Re-enter your email on the home page and tick the consent box again. You'll see a confirmation prompt that acknowledges the re-opt-in, then a fresh link lands in your inbox — no need to email anyone.

Community profiles and forum

Draft — pending legal review. The description of the community profile-sharing data flow below is new and is being reviewed alongside the Profile Library Terms. It accurately reflects what the software does today; the binding wording may change after review.

If you join the community (a free, passwordless account), we store only what you contribute: a display handle, any tuning profiles you share, your reviews, and your forum posts. There is no behavioural tracking — no "who viewed what", no per-user event log. Community membership is separate from the marketing list: joining never adds you to broadcast email.

Sharing a profile from the app

When you click "Share" on a tuning profile in the FFB-Bridge desktop app, the app transmits that profile to ffb-bridge.com and we hold it transiently — about 30 minutes — only so we can pre-fill the submission form for you. This is the one time the desktop app sends profile data to us; the app otherwise makes no outbound calls except to your local simulator. A shared profile that you do not go on to Publish is automatically deleted when that short window lapses. It is held in temporary server memory only, is never made public, and is never written to our database unless you publish it.

A shared profile carries a little environment metadata to make it useful to other pilots: the force-feedback stick model it was tuned on, the aircraft it is for, and the FFB-Bridge app version that created it. Tuning profiles are settings, not personal data — a shared profile is designed to contain no personal information, and your email and account identity are never placed inside it. You are credited publicly only by the display handle you choose (or "Anonymous").

The act of sharing from the app happens before you sign in. To stop abuse of that anonymous upload endpoint, we process your IP address only as a keyed (hashed) value for rate-limiting — the same abuse-prevention basis described above for the feedback form. We do not store the raw address for this purpose, and it is never shown publicly or shared. This applies to anonymous, not-yet- signed-in requests to our community upload endpoint just as it does to requests from signed-in members.

Deleting community data

If you ask us to delete your account, we anonymise your contributions — your handle is replaced with "[deleted member]" so threads and published shared profiles stay readable for everyone — or remove them entirely on request. Your sign-in identity (handle, login tokens, any moderator notes) is deleted outright.

Deletion concerns apply to published profiles only. Profiles that were shared from the app but never published are not retained — the transient staged copy is auto-deleted within about 30 minutes, so there is nothing for us to delete after that.

How long we keep it

Your subscriber row persists until one of:

  • You unsubscribe — we keep the row marked opted-out so we honor your choice even if the same address re-signs up later. No further messages are sent.
  • You email us asking us to delete your data — we delete the row entirely within 30 days of the request.
  • You stop using the product and ask us to remove your subscriber record — we delete it within 30 days unless we need to retain an opt-out marker to honor an unsubscribe.

Feedback reports and screenshots are retained as long as needed for product support and bug history. Raw support-bundle ZIP files are retained for a short triage window, 30 days by default, so we can re-parse them if the parser improves; parsed support data may be kept with the feedback report after the raw ZIP is removed. You can ask us to delete a feedback report or bundle at any time.

Aggregate analytics are kept without cookies or visitor profiles. Server logs and abuse-prevention records are kept only as long as needed to operate and secure the site.

Optional support-payment records are retained as long as needed for fulfillment, activation, recovery, receipts, refunds, chargeback handling, accounting, tax, fraud prevention, support, and legal obligations.

Your rights under PIPEDA

As a Canadian resident you can, at any time:

  • Access the personal information we hold about you. Email us from the subscribed address and we'll reply with your row contents.
  • Correct any information you believe is inaccurate.
  • Delete your data. We'll remove the row within 30 days.
  • Complain to the Privacy Commissioner of Canada if you're not happy with our response: priv.gc.ca.

Non-Canadian users

We welcome users from anywhere. For users outside Canada, the principles above still apply — express consent, easy unsubscribe, no third-party sharing, minimal data collection. If you are a resident of the European Economic Area, United Kingdom, or California, the corresponding rights under GDPR / UK-GDPR / CCPA are honored through the same email-based access and deletion process described above.

Changes to this policy

If we make material changes we'll update this page and notify active subscribers by email before the change takes effect. Minor wording edits are logged via the "Last updated" date at the top.

Contact

Questions, access requests, unsubscribe requests, complaints — all to supportffb-bridge.com.

Postal address:
Rohsam Inc.
2727 Steeles Ave West, Unit 103-886, Toronto, ON M3J 3G9, Canada