What Creo keeps, and what it does not.

Draft. This page is a draft awaiting review by Factor Dynamics and may change before it is final. Questions? Get in touch.

Last updated November 8, 2026

What we collect

• Keys: a hash of each API key, its creation time, its plan and how many calls it made each day. Creo never stores the key itself.
• Email, if you give one when creating a key or writing to us.
• Rate limits: for keyless calls, key creation and the contact form, a one-way hash of your IP address and a daily counter. The address itself is not stored by Creo.
• Payments: Stripe handles card details; we keep only the Stripe customer and subscription identifiers and the subscription status.
• Messages you send through the contact form.

What we do not collect

Portfolio requests (positions and prices) are processed in memory to compute the response and are not stored. The public pages set no cookies and load no advertising or analytics trackers. The account page keeps your key only in that browser tab.

Who processes data for us

• Render hosts the service; its logs record request paths and IP addresses for operations and security.
• Neon hosts the database.
• Stripe processes payments under its own privacy policy.

We do not sell personal data or share it for advertising.

How long we keep it

Key records and usage counts are kept while the key exists. Contact messages are kept as long as needed to reply. Billing records are kept as long as tax law requires.

Your choices

Ask us to see, correct or delete data tied to your key or email through the contact form. Deleting a key's record ends that key.