Privacy

SEC API is operated by Gabriele Muratori. This page describes the data used by this service.

Information we store

We store your account ID, name and email through our authentication provider, subscription status, Stripe customer and subscription identifiers, and API key names and one-way key hashes. We record authenticated API paths, response status, request duration, and timestamps for usage and troubleshooting. Raw API keys are displayed once and are not stored.

Support messages

When you use our contact form, we store your email address, selected category, message text, submission timestamp, and resolution status in our support inbox. Authorized operators use these details to investigate your request and respond where appropriate. Messages are not published in the public journal or sent to editorial models. Avoid including passwords, API keys, payment card details, or confidential financial information.

Cookies and rate limits

Essential authentication cookies keep you signed in. The public playground uses a hash derived from your network address for hourly rate limiting. The contact form uses a hash derived from your network address and the UTC date to limit daily submissions. We do not use advertising cookies.

Service providers

Vercel hosts the application. Neon provides the database and authentication. Stripe handles checkout and billing; payment card details go directly to Stripe. Vercel AI Gateway processes public source material for editorial generation. We do not send account records or API keys to the editorial models.

Retention and requests

Account, billing, and support records are retained while needed to operate the service and meet applicable obligations. You can revoke API keys in your dashboard. For account deletion, access, or privacy questions, contact our support inbox. Operational records may remain where required for security, dispute handling, or legal obligations.

Public content

Published articles and corrections are public. Financial source records come from SEC public datasets. Do not include credentials or confidential information in any request to support.