Bullia

Privacy Policy

Last updated: May 4, 2026

This Privacy Policy explains what information Bullia ("Bullia," "we," "us," or "our") collects when you use our trading journal service at bullia.net (the "Service"), how we use it, who we share it with, and the choices you have. By using the Service you agree to this policy.

1. Who we are

Bullia.net is a registered business operating under the laws of the State of Israel. We act as the data controller for the personal information described below. For privacy questions or to exercise your rights under applicable law (including GDPR for EU/EEA residents and CCPA for California residents), contact us at bullia.net@gmail.com.

2. Information we collect

2.1 Account information

  • Email address and display name when you register with email and password.
  • Profile data from Google (name, email, profile image) when you sign in with Google OAuth.
  • A bcrypt hash of your password. We never store, log, or have access to plain-text passwords.
  • Email verification timestamps and password change timestamps used to enforce session security (e.g. invalidating sessions after a password reset).

2.2 Broker connection data

  • For SnapTrade-supported brokers (e.g. Robinhood, Coinbase): we store the SnapTrade user identifier and brokerage connection ID. SnapTrade itself holds the broker credentials; we never see them.
  • For Interactive Brokers (IBKR): we store the IBKR Flex Query token encrypted at rest using AES-256-GCM with an environment-scoped key.
  • For CSV imports: we store the parsed trade data, not the original file.

2.3 Trading data

Trade executions, positions, account snapshots, journal entries, strategy / setup definitions, and derived statistics. This is the core product data and is scoped strictly to your account.

2.4 Billing data

We use Stripe for subscription billing. Stripe collects and stores your payment details directly under their security controls (PCI-DSS Level 1). We store only your Stripe customer ID, subscription ID, current tier, and subscription status — never card numbers or full bank details.

2.5 Operational data

  • Email delivery metadata via Resend for transactional messages (verification, password reset, welcome).
  • Error and performance telemetry via Sentry. Stack traces and request context may be recorded; we redact known sensitive fields (passwords, tokens, API keys).
  • Rate-limit counters (Redis) keyed by user ID, IP, or email — used purely to prevent abuse and brute force.
  • Standard server logs (request method, path, status, timing). These are retained short-term for debugging.

2.6 Cookies and Local Storage

We use browser-side storage mechanisms strictly to make the Service work, and for nothing else:

  • Authentication session cookies / JWTs issued by NextAuth so you stay signed in across pages and so we can validate your identity on every request.
  • Local Storage for non-sensitive user preferences (e.g. selected language, theme, dashboard layout state) so the interface remembers your choices between visits.
  • Strictly-necessary security and rate-limit identifiers used to prevent abuse, CSRF, and brute-force attacks.

We do not use cookies, Local Storage, pixels, or any other browser-side mechanism for cross-site tracking, behavioral profiling, third-party advertising, or sale of data to ad networks. There are no advertising or marketing trackers on the Service.

3. How we use your information

  • To provide, operate, and maintain the Service.
  • To authenticate you, secure your account, and recover access (e.g. password reset, email verification).
  • To sync, parse, and analyze your broker-imported trading data so that the journal, analytics, and statistics can function.
  • To process subscription billing through Stripe and to send transactional emails about your account or subscription.
  • To detect, investigate, and prevent fraud, abuse, and security incidents.
  • To comply with legal obligations.

We do not sell your personal information. We do not use your trading data to train third-party AI models. We do not share your data with advertisers.

4. Service providers we share data with

  • SnapTrade — broker OAuth and execution data sync.
  • Interactive Brokers — only when you actively use your own Flex Query token; data flows from IBKR to us, not the other way.
  • Stripe — payment processing and subscription management.
  • Resend — outbound transactional email delivery.
  • Anthropic — when (and only when) the AI Coach feature is enabled and you actively request an analysis. The feature ships disabled by default. We access Anthropic exclusively through their Commercial API, which operates under a strict zero-data-retention policy for model training: requests and responses are not stored beyond what is required to serve the response, and they are not used to train, fine-tune, or improve Anthropic's public or shared models. Your private trading data and strategies are NEVER used to train public AI models.
  • Sentry — error monitoring (with PII redaction).
  • Hosting and database providers (e.g. Vercel, managed Postgres) for the underlying infrastructure.

5. Data retention

We keep your account data for as long as your account exists. When you delete your account, we delete your trading data, journal entries, connected broker links, and authentication records within 30 days, except where we are required to retain records for legal, tax, or fraud-prevention purposes (e.g. Stripe invoice records).

Verification and password-reset tokens are short-lived (minutes to hours) and are deleted immediately on use or expiry.

6. Security

  • HTTPS in transit; managed Postgres encryption at rest.
  • Passwords stored as bcrypt hashes (cost factor 12).
  • IBKR Flex tokens encrypted with AES-256-GCM before being written to the database.
  • Sensitive verification tokens (password reset, email verification) stored as SHA-256 hashes — the raw token is only sent to your email.
  • Per-IP and per-email rate limiting on authentication, password reset, and verification flows to mitigate brute force and abuse.
  • Session invalidation on password change so a compromised session cannot survive a reset.

No method of electronic storage is 100% secure. If we become aware of a breach affecting your data, we will notify you and the appropriate regulators as required by law.

7. Your rights

Depending on your jurisdiction, you may have the right to access, correct, port, restrict, or delete your personal information, and to object to certain processing. To exercise any of these rights, email bullia.net@gmail.com. We will respond within the timeframe required by applicable law (typically 30 days under GDPR).

EU/EEA residents have the right to lodge a complaint with their local data protection authority. California residents have the rights described in the CCPA, including the right not to be discriminated against for exercising them.

8. International data transfers

Our infrastructure providers may process data in the United States, the European Union, and other regions. Where data is transferred out of the EU/EEA, we rely on Standard Contractual Clauses or equivalent safeguards offered by those providers.

9. Children

The Service is not directed to anyone under 18 years of age. We do not knowingly collect personal information from anyone under 18. This strict minimum age is required because the Service handles financial trading data and integrates with regulated broker APIs (including SnapTrade and Interactive Brokers), whose own terms and underlying brokerages restrict account ownership to legal adults. If you believe someone under 18 has provided us with personal information, contact us and we will delete it.

10. Changes to this policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top reflects the most recent substantive revision. For material changes, we will notify registered users by email or through an in-product notice.

11. Contact

For privacy questions, requests, or complaints, email us at bullia.net@gmail.com.