Your information.
Your choice.

Who we are & what this covers

FORJ Inc is responsible for the personal information described in this notice. We are based at 702 W 400 S, Centerville, UT 84014, United States. You can reach us at ravish@getforj.com.

This notice covers the FORJ marketing website at getforj.com and its private enablement hub, including inquiries and requests for hub access. It is not a blanket privacy policy for the FORJ fitting application, or for a partner’s booking website. Those services have their own applicable notices.

What we collect & why

When you get in touch

Inquiry and access-request forms may ask for your name, email address, company, and message. We use the information you submit to answer your question, consider an access request, or take steps you request before a business relationship. Where applicable, our basis is those requested pre-contract steps or our assessed legitimate interests in relevant business correspondence.

There is no mandatory privacy-consent checkbox and no newsletter signup associated with these forms. Reading this notice is not consent to optional analytics or marketing.

When you use the private hub

We use your verified email address, access approval, sign-in challenges, and session information to provide requested hub access and protect private materials. Our basis, where applicable, is our legitimate interests in administering requested access and preventing unauthorized use. Hub messages and access requests are used to respond and manage that relationship.

When the website runs

Our platform and hosting services process technical security and access logs, which may include IP addresses, request times, requested paths, browser information, and response details. We use these to operate the site, diagnose faults, and protect it from abuse, based on our legitimate interests in reliable, secure services. Necessary cookies support sign-in and remember your privacy choice.

Only if you accept analytics

Google Analytics 4 (GA4) helps us understand use of public pages through browser, device, and page-visit information. Optional analytics is based on your consent. We configure analytics page locations to exclude query strings and fragments, omit the page referrer, disable Google signals and advertising personalization signals, and do not send user IDs or custom identity or form-message payloads.

With that same analytics choice, we measure selected clicks from public pages to the Trackman Portal, including the source page, fixed button label and placement, and destination domain/path. A click indicates an outbound action, not a confirmed portal visit, login, or purchase. We cannot observe activity inside Trackman’s portal through these events.

We disable automatic form-interaction measurement as far as website configuration permits; enhanced-measurement settings also require review in the GA4 property. We do not load Google Analytics on private hub pages.

Cookies. A real choice.

Necessary cookies keep sign-in working and remember your privacy preference. Optional analytics cookies are different: we make no Google Analytics requests before you accept. If you reject, optional analytics stays off.

Use Cookie settings to accept, reject, or withdraw. Withdrawal stops further analytics collection on this page and removes accessible GA cookies; it does not require reloading a form you may be filling out. It does not undo processing that already took place before withdrawal. Your choice applies to this browser, not automatically to other devices.

We ask again when your preference expires or the consent-notice version changes. You can also delete cookies using your browser. If your browser cannot save the preference cookie, analytics remains off and you may see the choice again on another page. Rejecting analytics does not delete necessary sign-in cookies.

Who receives information

We use suppliers to deliver this website and requested services. Relevant recipients include:

• Railway and database hosting services for running the website, storing submissions, managing hub access, and platform security.
• Plunk for transactional email, including sign-in codes and requested correspondence.
• Google for GA4 analytics, only when you accept optional analytics on public pages.
• HubSpot as a video host when you play hosted video; playback may involve sharing browser and connection information with that host.

We may also disclose information where a legal obligation requires it or where necessary to protect legal rights. We do not promise that information is never shared.

Links to partner fitting or booking websites take you to independent services. Their information handling, cookies, and booking practices are governed by their own policies; review those before providing information.

International processing

FORJ is a United States entity, and our suppliers may process information outside your country, including outside the European Economic Area. Privacy protections may differ between countries.

Applicable international-transfer safeguards and provider arrangements must be verified for the processing concerned. We do not make unverified claims about hosting regions, vendor certifications, or contractual safeguards. Please contact ravish@getforj.com to request information about the arrangements applicable to your data.

How long we keep information

We use the following retention schedule. We may preserve narrowly necessary records for a legal hold or other legal requirement.

Inquiries, hub messages & access requests

12 months after resolution or the last meaningful correspondence. Reviews and deletions are manual because the database records creation timestamps rather than a complete correspondence lifecycle. Mailbox copies follow the same inquiry schedule.

Approved hub guests

Kept while access is needed, with access reviewed every 6 months.

Sign-in challenges & sessions

Email codes are valid for 10 minutes, single-use, and limited to 5 attempts. Challenge data is swept every minute. A hub session lasts 30 days; signing out clears the session.

Routine provider & access logs

A 30-day retention target, subject to confirmation of provider-managed settings.

Transactional email delivery logs

A 30-day retention target, subject to confirmation of provider-managed settings. This is separate from correspondence retained in our mailbox.

Backups

A 30-day retention target, subject to confirmed provider settings. Deleted information may remain in a backup until that backup expires.

Consent preferences & receipt evidence

Your browser preference lasts up to 6 calendar months. Minimal hashed consent-receipt evidence may be retained for up to 3 years after expiry or withdrawal to demonstrate the choice recorded.

Google Analytics data

We intend a 2-month retention setting for GA4 user- and event-level data. This requires property administrator configuration and has not yet been verified. Aggregated reporting is not governed by the same retention setting.

Your rights & requests

Depending on the law that applies to you, you may have rights to access, correct, delete, or receive a portable copy of personal information; restrict processing; or object to processing based on legitimate interests. These rights are subject to applicable conditions and exceptions.

You can withdraw optional analytics consent at any time through Cookie settings. Withdrawal does not affect the lawfulness of processing before withdrawal.

Send privacy requests to ravish@getforj.com. We may need proportionate information to verify your identity before acting. Requests are normally answered within one month, subject to legal exceptions and permitted extensions; we will explain if an extension is needed.

If you are in the EEA, you can complain to your local data-protection supervisory authority. You may also have complaint rights with another regulator under the law that applies to you.

Questions? Talk to us.

For privacy questions, rights requests, or information about our suppliers and transfer arrangements:

We may update this notice as the website or our practices change. The date at the top identifies the latest update. Where a change requires a new analytics choice, we will ask again before enabling it.