Privacy Policy

Last updated: September 20, 2026

This policy describes information handled by Trelic Technologies LLC through its website, trading app and companion services, and business platform work. It distinguishes Trelic's own services from storefronts operated by independent merchants.

1. Website, accounts, and billing

When you create a Trelic account, we store your email address, a password hash, account and session records, and information needed to provide licensing and support. Licensing records include license identifiers and device activation information. Billing records include Stripe customer, checkout session, and subscription references, subscription status, and checkout and payment events. Stripe processes free beta registrations without requiring payment-card details; paid checkout collects payment details through Stripe's hosted interfaces.

We also receive information you choose to send in support or business inquiries, including contact details and attachments. Do not send passwords, API keys, full payment-card numbers, or unnecessary sensitive records.

Our hosting and security systems may process IP addresses, request metadata, and error logs to operate and protect the service. Website fonts may load from Google Fonts, which receives ordinary request metadata.

2. Website storage and analytics

The website uses a session cookie for sign-in. Browser storage may hold preferences and referral information. These features are separate from trading data stored locally by the desktop app.

Our first-party pageview endpoint records timestamps, page paths, referrer hostnames, and campaign tags. Its analytics records do not include IP addresses, browser user-agent strings, or a persistent visitor identifier. Infrastructure logs may separately contain request metadata. The analytics endpoint honors a Do Not Track header where the browser sends it. This is not a promise that all third-party services honor that setting.

3. Trading app on your device

The desktop stores settings, strategies, trading history, paper-trading records, audit information, and saved connection credentials in your device's user profile. Saved credentials use operating-system secure storage where available. Brokerage login and API access use the relevant provider's authorization process.

When the agent runs, account and market information needed for analysis is sent to the AI provider using your configured connection. Brokerage requests, market-data requests, and authorized orders are sent to the connected provider. Those services process information under their own terms and privacy policies. Trading data is not confined to your device when these integrations are used.

The app also contacts Trelic for licensing and optional companion functions and contacts the update provider for software releases. Diagnostic reports may be sent to Sentry when reporting is configured; reports are intended to exclude credentials and sensitive trading details, but you should review anything you voluntarily send to support.

4. Companion relay and notifications

If you pair the companion, Trelic's relay forwards encrypted messages between the desktop and companion. The relay does not receive the pairing secret or message encryption key. It processes channel identifiers, connection metadata, and encrypted traffic.

Enabling push notifications stores subscription endpoints and related delivery keys and channel information needed to send notifications. Push providers process delivery metadata. Trading companion push messages are designed to be generic prompts to open the companion rather than trade details. Encryption does not hide connection timing or message size, and protecting paired devices remains important.

5. Merchant ordering and delivery deployments

Each merchant's storefront is operated for that merchant on its own deployment and service accounts. The merchant determines its own products, customer communications, delivery operation, and applicable policies. Contact the merchant first about its customer records or orders.

Depending on enabled features, the platform processes customer names, email addresses, phone numbers, delivery addresses, order contents, payment references and status, delivery schedules, stock records, and admin activity. Saved checkout recovery information can remain in the customer's browser. Address validation and suggestions send address information to the configured maps provider; payment fields send payment details to Stripe; confirmation emails send recipient and order information to the configured email provider.

Trelic may access the deployment as an authorized collaborator for provisioning, troubleshooting, and agreed support. The merchant's published privacy policy and the relevant project agreement govern that operational relationship. Driver location, delivery photos, SMS, and push data are processed only where those features are implemented and enabled with appropriate notices and permissions. Planned features are not representations that this data is currently collected.

6. Purposes and recipients

We use information to provide and secure services, manage accounts and payments, respond to requests, maintain software, investigate misuse, and meet legal obligations. Relevant providers can include hosting and infrastructure services, Stripe, email providers, error-reporting services, and providers you or a merchant connect, such as brokerages, AI services, Supabase, Vercel, Resend, and Google Maps.

We do not sell personal information. We disclose information to service providers as needed for these purposes, when legally required, to protect rights and safety, or as part of a lawful business transfer subject to appropriate protections. Merchant deployments may use different providers, described in the merchant's own notice.

7. Retention and security

Information is retained for the period needed to provide the service, support legitimate business purposes, resolve disputes, and satisfy legal requirements. Retention varies by record and provider; deleting an app does not delete separate billing records or merchant orders.

We use access controls, credential protections, and encryption appropriate to the service. No system is completely secure. Limit administrator access, protect devices and keys, and notify us of suspected compromise.

8. Your choices and requests

You can disconnect trading integrations, remove saved credentials, unpair the companion, disable notification permissions, and remove local application data. Cancelling a subscription does not automatically delete the account. Contact Trelic for account access, correction, deletion, or other privacy requests; we may need to verify identity and retain records where required or permitted by law.

For a merchant order or storefront account, contact that merchant using its published contact information. Rights depend on your location and applicable law. Where Trelic processes data on a merchant's behalf, we will direct or assist the request through the merchant.

9. Children and changes

Trelic's trading and business administration services are intended for adults. We do not knowingly solicit personal information from children under 13 through our own services. Merchants must establish appropriate rules for their storefronts.

We will update this policy as services change, publish the revision date, and provide additional notice where required.

10. Contact

Privacy requests: support@trelictech.com. Trelic Technologies LLC, Valrico, Florida. See Support.