Skip to main content

Privacy Policy

Last updated: 2026-10-26

The short version

We never sell, rent, or trade your data — period. Your financial information is encrypted with AES-256 at rest and TLS in transit, protected by account-scoped access controls (row-level security for browser sessions, ownership checks in code for server jobs), and shared only with the subprocessors needed to run the platform (Clerk, Supabase, Stripe, Vercel, Anthropic, Resend, Sentry, Upstash), with the teammates you invite into a shared workspace, and with anyone you send a read-only snapshot link to. You can export your data at any time. Integrations transmit account data only after you connect and authorize them: Plaid for bank transaction import (in validation, not yet generally available), Google Drive and Gmail, Microsoft Outlook and OneDrive, Dropbox, and configured sponsor-portal adapters such as Carta and CrowdStreet. When you close your account in Settings by typing DELETE MY ACCOUNT, Stripe billing is cancelled and your profile is anonymised immediately. Portfolio records, documents, and exports are kept for 30 days after closure so support can reverse a mistake, and are then deleted automatically by a daily job. Audit, legal and consent, compliance, and billing-notice evidence is deliberately retained. Data shared into a workspace stays with that workspace: fields naming you as author, inviter or sender are cleared, and the internal identifier left on those records no longer maps to any account. If you cannot sign in, submit an erasure request through the contact form; identity verification still applies.

Quantified Holdings LLC, a West Virginia limited liability company doing business as SyndTrack (“we”, “us”, or “our”) is the controller of the personal information described in this policy, and is committed to protecting the privacy of our users. This Privacy Policy describes how we collect, use, and safeguard your information when you use the SyndTrack platform.

Information We Collect

Account Information

When you create an account, we collect your name and email address through our authentication provider, Clerk. We do not store passwords directly — authentication is handled entirely by Clerk.

Financial Data

You may enter information about your real estate syndication investments, including deal details, capital calls, distributions, and related documents. This data is stored securely in our database hosted on Supabase (PostgreSQL) with row-level security enabled.

Payment Information

If you subscribe to a paid plan, payment processing is handled by Stripe. We do not store credit card numbers or bank account details on our servers. Stripe's privacy policy governs the handling of your payment information.

Usage Data

We collect basic usage analytics (page views, feature usage) to improve the product. Product events, such as sign-up, onboarding, first-deal, first-upload, and upgrade milestones, are recorded against your account (not aggregated). Usage data does not include your financial information.

Technical and Security Data

Technical and security data: IP address and browser user agent, recorded in audit-log entries for account and portfolio changes (such as creating, editing, or deleting records, and team or webhook changes) and with your acceptance of these policies; retained as part of audit and consent records.

Email Import Data

Email import is optional and off until you set it up. When you set up an import address and accept the AI notice, email sent to that address is received by our email provider, Resend, and passed to SyndTrack. We store the message details (sender, subject and date) and its PDF, PNG, JPEG, text, CSV and JSON attachments in your account. While AI extraction is on for that address, and within your plan's AI parsing allowance, PDF, PNG and JPEG attachments are sent to our AI provider, Anthropic, to extract structured data (amounts, dates, deal identifiers); the body of the email is not sent. Nothing is added to your portfolio until you review and confirm it. You can turn AI extraction off for an address at any time, and files sent to it are then stored without being read. Deactivating an address stops new mail being accepted; documents already stored follow the retention described below.

Separately, our domain accepts mail for the contact addresses listed on our Contact page (support, privacy, security, and legal). Our email provider, Resend, receives that mail, including any attachments, and forwards it to us as ordinary correspondence. It is read to answer you, is not sent to an AI provider, and is not added to your portfolio. Resend also sends our outbound transactional email.

AI Document Parsing and Deal Scoring Data

Documents you upload, or import from a cloud-storage source you have connected, are sent to our AI provider, Anthropic, to extract structured data (amounts, dates, deal identifiers) only when you choose AI parsing for that upload or import. Each has a way to proceed without AI, and files imported from a connected source are stored without AI parsing unless you opt in. Scheduled syncs never send documents to an AI provider. Attachments emailed to an import address you created are sent to Anthropic only while AI extraction is on for that address, as described under Email Import Data above. If you use AI Deal Scoring, your deal data (including deal details, financial terms, and operator information you have entered) is also sent to Anthropic to generate scores and analysis. Anthropic states that commercial API data is not used to train its models by default; customer opt-in or deliberate feedback may create an exception. Extracted fields, scores, sub-scores, and AI-generated reasoning are stored in your account. See our AI methodology page for details on how scoring works.

How We Use Your Information

  • To provide and maintain the SyndTrack platform
  • To process your subscription and payments
  • To send transactional emails (e.g., capital call alerts)
  • To extract data from documents you upload, and to generate AI deal scores when you request them (both via Anthropic)
  • To improve our product and user experience
  • To respond to support requests

Data Storage & Security

All data is encrypted in transit (TLS) and at rest (AES-256). Requests made from your browser session run under Supabase row-level security scoped to your account; server jobs and API-key requests enforce account ownership in code. A deal you share is visible to the teammates you invite. We regularly review our infrastructure and document our current controls on our security page.

We Do Not Sell Your Data

Based on how the product operates, we do not sell personal information. We disclose information to service providers needed to operate the platform, including Clerk for authentication, Supabase for database hosting and storage, Stripe for billing, Vercel for application hosting, Anthropic for document parsing and deal scoring, Resend for outbound transactional email and for receiving and forwarding to us mail sent to our published contact addresses, Sentry for error monitoring, and Upstash for rate limiting, idempotency, and webhook deduplication. Integrations transmit account data only after you connect and authorize them: Plaid for bank transaction import (in validation, not yet generally available); Google Drive and Gmail; Microsoft Outlook and OneDrive; Dropbox; and configured sponsor-portal adapters such as Carta and CrowdStreet. See our security page for the full subprocessor list. We update this subprocessor list and note the change in our public changelog before a new subprocessor receives customer data.

Data Retention

We retain your data for as long as your account is active. When you close your account through Settings with the required typed confirmation, Stripe billing is cancelled immediately and your profile (name, email, avatar) is anonymised. Portfolio records, transactions, uploaded documents, and generated exports are kept for 30 days after closure so support can reverse a mistaken closure, and are then deleted automatically by a daily job. Audit, legal and consent, compliance, billing-notice, and webhook records, and our internal records of the deletion itself, are deliberately retained. Data shared into a workspace stays with that workspace: fields naming you as author, inviter or sender are cleared, and the internal identifier left on those records no longer maps to any account. Backups made before deletion are not edited and expire on their own schedule.

Cross-account benchmarking

Consent is recorded, but no cross-account pooling or comparison runs today. If we switch it on, your deal financials contribute only in aggregate and only once a cohort reaches at least 10 opted-in accounts and 50 contributed data points. The peer benchmark cache holds aggregate statistics only; it holds no user or deal identifiers. Consent is opt-in and withdrawable in one click from Reporting → Cross-account benchmarking, and withdrawal invalidates the cache immediately. This policy will be updated before any pooling is switched on.

Your Data Rights

These are the things you can do today and how:

  • Access and export your personal data through Settings → Download data export. The JSON export includes your portfolio records, profile data, document metadata, temporary links for owned storage files, and up to 5,000 audit-log rows.
  • Correct your information by editing portfolio records through the dashboard. Identity fields are managed by our authentication provider, Clerk, and synchronized to your profile.
  • Close your account in Settings by typing DELETE MY ACCOUNT. Stripe billing is cancelled and your profile is anonymised immediately; portfolio records, documents, and exports are kept for 30 days after closure and are then deleted automatically. If you cannot sign in, submit an erasure request through the contact form on our help page; identity verification applies.
  • Request restriction of processing or object to processing through the same help channels. We do not provide a separate restriction or objection preference center.

To exercise a right, use our help page. We may need to verify your identity before acting on a request.

California Privacy Rights

We collect identifiers and account information such as your name, email address, and authentication identifiers; commercial and financial information such as deal records, capital calls, distributions, transactions, subscriptions, and payment-related information; internet or electronic activity information such as account and product usage; professional or operator-entered information; and document contents and extracted information when you upload documents or use document parsing. We do not sell personal information based on how the product operates.

California residents may request access to or deletion of personal information, and may request correction where applicable. Submit a request through our help page. You may submit a request through an authorized agent using the same channel. We do not discriminate against you for exercising these rights.

Cookies

We use application cookies, identity-provider cookies, and infrastructure cookies. The signed-out public experience we observed set the following cookies:

  • ab_hero_cta_copy: product measurement for an experiment on homepage call-to-action wording; 90 days.
  • syndtrack.funnel_anonymous_id: an anonymous identifier that links signed-out marketing page views and CTA clicks for funnel measurement; one year. If you later sign up, it is linked to your account for the same funnel measurement.
  • syndtrack.onboarding.completed: remembers onboarding completion; one year when set.
  • syndtrack-demo-origin: remembers entry to the public demo experience; 30 days when set.
  • oauth_state, outlook_oauth_state, google_drive_oauth_state, onedrive_oauth_state, gmail_oauth_state, and dropbox_oauth_state: OAuth security state; 10 minutes when set.
  • __client_uat and the suffixed __client_uat_<instance-suffix> form, observed as __client_uat_imnCTLjM: Clerk identity-provider cookies on .syndtrack.io; the observed signed-out expiry was September 13, 2027.
  • __client: Clerk identity-provider cookie on .clerk.syndtrack.io; the observed expiry was around September 13, 2027.
  • _cfuvid: Cloudflare infrastructure cookie on .clerk.syndtrack.io; a session cookie in the observed session.
  • __cf_bm: Cloudflare infrastructure cookie on .clerk.syndtrack.io; the observed lifetime was approximately 30 minutes.

The Clerk and Cloudflare cookies on .clerk.syndtrack.io are not application-owned cookies on www.syndtrack.io. We did not observe a Stripe-domain cookie from the public pricing page. This enumeration reflects the signed-out experience. Additional authentication cookies are set when you sign in.

We do not currently provide a cookie banner, consent manager, or cookie preference center, and cookie setting is not gated on an in-product consent choice. You can control cookies through your browser settings. We do not use third-party advertising cookies.

Security Incidents

One operator handles incidents personally; we do not staff a round-the-clock rotation. If we confirm an incident that affected your personal information, we email the address on your account (Resend is our only outbound path) and publish a note on the public changelog when more than one account is affected. We send notice within 7 days of confirming which accounts were affected. We notify regulators or others only where the law requires it. Internal steps live in our incident-response runbook.

Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy on this page and updating the “Last updated” date.

Contact Us

If you have questions about this Privacy Policy, or want to exercise any of your privacy rights, please contact us via our help page.