Privacy Policy

Linestry is operated by Lineage Community Technologies Inc. ("Linestry", "we", "us"), a company incorporated in British Columbia, Canada. We are the organization responsible for the personal information described in this policy.

Questions, access requests, and complaints go to jay@lineage.community.

Account information. When you create an account we collect your email address and display name. If you sign in with Google or Facebook, that provider sends us your name, email address, and profile picture URL. We do not receive your password, and we do not receive your friend list, posts, photos, or any other content from those accounts.

Profile information you add. Username, avatar, home mountain, the year you started riding, era, bio, profile statement, and milestones. All of it optional beyond what is needed to create the account.

History you record. Timeline claims (where you rode, who you rode with, boards you owned, events you entered), riding days, stories and their text, dates, photos, and any YouTube links you attach. Photos are uploaded to our storage buckets and keep whatever information is embedded in the file you upload.

Information about other people. Linestry is a shared graph, so members add catalog records for riders, places, brands, boards, and events, and tag other people in their own history. This means records about you may exist before you ever create an account. See section 7.

Payment information. Memberships are processed by Stripe. Stripe handles your card details directly; we never see or store a card number. We store the Stripe customer and subscription identifiers, your tier, and its status.

Usage and diagnostic data. Page views, feature events (for example, starting onboarding or publishing a story), approximate location inferred from IP address by our analytics provider, browser and device type, and error reports when something breaks. Session replays are recorded with all input fields masked, so typed content such as emails, names, story bodies, and claim notes is not captured. If you arrive through a campaign link or a referral code (for example a code read out on a podcast), we record that code and the standard campaign tags on the link, along with the site that referred you, so we can tell which of our own efforts brought people here. This is first-party measurement only: we do not run advertising pixels and we do not share it with advertisers.

Bug reports and support email. Whatever you choose to include when you file an in-app bug report or email us.

• To create and secure your account and sign you in.
• To build and display your timeline and the shared community graph.
• To send transactional email: sign-in links, tag notifications, comment notifications, claim decisions, and membership receipts.
• To process memberships and track token and equity-offer balances.
• To moderate contributions, review claim requests, and enforce our terms.
• To understand which parts of the product work, fix errors, and improve it.

We do not sell personal information, we do not share it with advertisers, and we do not use your content to train third-party AI models.

In Canada we rely on your consent, given when you create an account and when you choose to publish content. Where the GDPR applies, we rely on: performance of a contract (running your account and membership), legitimate interests (security, moderation, product analytics, and maintaining an accurate historical record), consent (optional email and optional public sharing), and legal obligation (tax and accounting records).

Your timeline is private by default. Content becomes visible to others only when you choose it: by setting an entry's visibility, by turning on a public timeline at a public link, or by contributing a record to the shared catalog. Catalog entries (people, places, brands, boards, and events) are community data and are visible to other members by design.

Anything you publish publicly can be seen, copied, indexed by search engines, and archived by third parties. Turning public sharing off stops future access through Linestry but cannot retrieve copies already made elsewhere.

If you choose "Continue with Facebook" or "Continue with Google", we request only the basic profile fields listed in section 2 in order to create your Linestry account and match it to an existing email address if you already have one. We do not post to your Facebook or Google account, we do not read your friends, contacts, or feed, and we do not import content from those services.

You can disconnect Linestry at any time from your Facebook settings (Settings and Privacy, then Settings, then Apps and Websites) or your Google account permissions page. Disconnecting stops future sign-ins with that provider; to remove data already stored on Linestry, follow the data deletion instructions.

Members can add a rider to the catalog and tag them in their own history. These unclaimed records exist so that history can be recorded accurately, and they hold only what a member contributed: a name, and the claims or stories that reference it.

If a record refers to you, you can claim it and take ownership of the profile, set tag approval so that future tags need your consent, block specific members, or ask us to remove the record entirely. Write to jay@lineage.community and we will act on it. You do not need an account to make that request.

We use a small set of processors, each bound to use the data only to provide their service to us:

• Supabase: database, authentication, and file storage.
• Vercel: application hosting and request logs.
• Stripe: payment processing for memberships.
• Resend: delivery of transactional email.
• PostHog: product analytics and masked session replay.
• Sentry: error and performance monitoring.
• Google and Meta Platforms: only if you choose their sign-in button.

We also embed YouTube players when a member attaches a video. Loading an embedded player contacts Google's servers and is subject to Google's privacy policy.

Linestry is a Canadian company, but our providers operate in the United States and other countries, so your information is stored and processed outside Canada and may be accessible to courts and authorities in those jurisdictions. Where the GDPR applies, transfers rely on our providers' standard contractual clauses.

We keep your account and the history you record for as long as your account is open. Analytics and error data are kept for up to 24 months. Payment records are kept for seven years as required for Canadian tax purposes. When you ask us to delete your account, we follow the timelines set out in the data deletion instructions.

• Access and correction. You can edit your profile and entries in the app, and you can ask us for a copy of everything we hold about you.
• Deletion. See the data deletion instructions.
• Email preferences. Notification email can be turned off in your settings or through the unsubscribe link in any message. Sign-in and receipt emails are operational and cannot be turned off while your account is open.
• Tagging. You can require approval before other members tag you, and you can block individual members.
• Public sharing. You can turn your public timeline on or off at any time.

If you are in the EU or UK you also have rights to portability, restriction, objection, and to complain to your supervisory authority. If you are a California resident you have the rights to know, delete, correct, and to opt out of sale or sharing. We do not sell or share personal information as those terms are defined. If you are in Canada and are not satisfied with our response, you can contact the Office of the Privacy Commissioner of Canada or the Office of the Information and Privacy Commissioner for British Columbia.

Access to the database is governed by row-level security, traffic is encrypted in transit, and administrative access is limited to the people who need it. No service can promise perfect security; if a breach creates a real risk of significant harm we will notify affected members and the relevant regulator as the law requires.

Linestry is not directed at children under 13, and we do not knowingly collect their personal information. If you believe a child has created an account, write to jay@lineage.community and we will remove it.

We will update this page when our practices change and revise the effective date above. For material changes affecting how we use information you have already given us, we will notify members by email or in the app before the change takes effect.