Privacy policy (summary)

This page summarizes how the ArcLogic Product may process information in connection with your use. It is a starting point for engineering and product communication, not a final privacy notice for all jurisdictions. Replace or supplement it with a counsel-reviewed document before you make broad public-facing privacy commitments in regulated contexts.

1. What we may collect

Depending on features you enable, we and our service providers (such as auth, hosting, and analytics) may process:

• Account identifiers, contact information, and authentication events from your identity provider (e.g. Clerk);
• Usage, performance, and error data from the app and APIs (e.g. health checks, Sentry) to operate and improve the service;
• Inputs you type into the Product (e.g. scenario parameters, watchlists) and, when applicable, the results of server-side calls you initiate (e.g. broker and market data requests configured in your environment).

2. How we use information

We use information to run the service, secure accounts, connect to the third-party services you or your administrator wire up (e.g. broker, market data), and understand reliability and product usage. We do not sell your personal information as a stand-alone “data broker” product. If you later add advertising, analytics, or model-training use cases, update this section with precise disclosures.

3. Retention and storage

Many builds are stateless for long-lived portfolio data — confirm your deployment. When a database, logs, or object storage is involved, set retention, deletion, region, and encryption to match your policies and the territories where your users sit (including GDPR, UK GDPR, and U.S. state laws where applicable).

4. Your rights and choices

Depending on where you live, you may have rights to access, correct, delete, or export information, or to object to certain processing. You may be able to exercise some controls through the identity provider’s account portal. For a formal request, provide a contact process on your public site and verify requests according to your counsel’s guidance.

5. International transfers

Vendors and infrastructure may be located in the United States or other countries. Use appropriate transfer mechanisms and vendor agreements (e.g. SCCs) if you have users in the EEA, UK, or other regions with cross-border rules.

6. Contact (placeholder)

Add a role-based email or ticketing path for privacy requests before you list this in production footers and app stores.