Privacy Policy

About this policy

Rails is operated by Hitch Intelligence, Inc. This policy explains how we handle information when you use getonrails.com, sign in, build courses, or request a demo. Contact us at seth@usehitch.ai.

Google sign-in

When you sign in with Google, Rails receives your Google account identifier, name, email address, email-verification status, and profile image when available. We use this information to authenticate you and display your account. The current sign-in flow requests basic identity information, not access to your Gmail, Drive files, or spreadsheets. Google handles your Google password; Rails does not receive it.

Rails uses an encrypted session cookie to maintain your sign-in. Sessions are configured for up to seven days and may be renewed through continued use. Temporary cookies and identifiers help protect the sign-in flow.

Course drafts and validation

The current Studio stores course drafts, canvas layouts, and locally published revisions in your browser's local storage. They are not shared online by the local publish action. When you request validation, course content is sent to the Rails server for that check. Browser data can be lost if you clear site storage or change devices; save an exported copy of work you want to keep.

Demo requests and contact information

If you submit a demo request, we collect your email address and the information you provide, such as name, company, company size, role, country, optional phone number, and marketing preference. We use this information to respond to your request and manage our contact records. We use AWS for hosting and storage and HubSpot for contact management. The current integration sends submitted email addresses to HubSpot.

Cohort applications and ad measurement

When you apply to a cohort, we store your email, application answers, and supported campaign labels from the link you used, including UTM parameters and the Meta click identifier when present. We use these records to handle applications and understand which campaigns lead to saved applications. Campaign labels are kept in this browser tab for up to 24 hours before submission. Submitted application records do not expire automatically; contact seth@usehitch.ai to request deletion.

Ad measurement on job-hunt pages is off unless you choose to allow it. If you allow it, the Meta Pixel sends page visits and newly saved application events to Meta, including a generated event identifier, browser and cookie identifiers, page and referring URLs, and network information such as your IP address. Meta may use this information to measure and improve ads under its own privacy policy. We do not add your email or application answers to these events, and automatic advanced matching is disabled.

You can apply without allowing Meta measurement. Use the Ad measurement control on job-hunt pages to change your choice. We save that choice in local browser storage and keep Meta measurement off when your browser sends Global Privacy Control. Turning measurement off stops future events from this integration; it does not delete information already sent to Meta. Campaign labels can still be saved with your application when Meta measurement is off.

Technical information

Our hosting and security systems process request information needed to operate the service and investigate errors or abuse. The demo form processes your IP address to enforce rate limits using a salted identifier. Temporary rate-limit records are marked for automatic expiration.

Sharing and service providers

Google provides sign-in, AWS hosts and processes the service, and HubSpot supports contact management. These providers process information needed for their roles. Google sign-in information is used for account functionality; it is not passed to the demo-form CRM integration by the sign-in code. If you separately submit a demo request, that submission follows the contact handling described above.

Your choices

You can sign out, clear Rails cookies and local browser storage, and revoke Rails access through your Google Account settings. Clearing browser storage removes local drafts from that browser and does not itself delete submitted contact records. Contact seth@usehitch.ai to request access, correction, or deletion of information held by Rails, or to change your communication preferences. Requests may require verification of your identity.

Retention

Sign-in sessions are configured for up to seven days and may be renewed through continued use. Local course data remains in your browser until you remove it or clear site storage. Temporary rate-limit records are marked for expiration. Demo and contact records do not expire automatically; contact seth@usehitch.ai to request deletion. Clearing browser storage does not remove records already submitted to Rails.

Updates

We will update this policy when our information practices change and show the effective date on the published policy.