Last updated:
This policy describes the Parezen website. Parezen is the name used on this site. Questions about it are handled under applicable law.
What this website is
The site is a sample-data web app. Organisations, requests, invoices and savings figures are samples. They are not records of a live customer system. Signing up does not create an account. Contact forms do not send a message. The site does not run a hosted gateway, and it does not send a wizard or playground request to a model provider.
What you can enter
Sign-up asks for three things:
- Your name.
- A work email.
- A password of at least 8 characters.
The password stays in the browser tab. It is not written to storage. The name, email, organisation name, first project, monthly spend band and the providers you select can be kept in this browser’s session storage so the later steps still have them. That storage ends with the session. None of it is sent to Parezen to open an account.
Log in asks for an email and a password. The page checks that the email contains an @ and that the password is long enough. It does not check them against a directory, and it does not store them. The single sign-on screen does not talk to an identity provider.
The usage step can read a CSV or JSONL file in the browser. The file stays in the browser. Session storage keeps the file name and a row count, not the file. A provider key is not accepted. The page does not ask for one, and it does not keep the last four characters. Encryption in transit, encrypted key storage and rate limits are not in place.
Contact, waitlist and enterprise forms ask for a name, a work email, a spend band and a note. Submitting them shows a notice that nothing was sent. The details stay in the browser.
The sample app does not show a survey, and public pages do not show business-note panels.
Cookies and storage on your device
The site does not run a website analytics or advertising service. There is no third-party analytics script. Spend charts inside the sample app are sample product views, not a record of how you use the website.
The site sets these first-party cookies so the interface can match on the next view:
- pz.banner — whether the sample banner is collapsed.
- pz.sidebar — whether the sidebar is collapsed or open.
The theme control stores a light, dark or system choice in this browser’s local storage. Session storage holds the onboarding draft described above, without the password. If you enable or ignore a sample recommendation, that choice is kept in session storage for the tab.
Payments
The site does not process payments. There is no payment provider, and the site does not collect a card number. Published list prices are on the pricing page. Figures inside the app are sample data. Nothing on this website charges you.
Gateway and content logging
Docs show a planned hosted base URL, https://api.parezen.com/v1. This website does not operate that gateway. A setup request and a playground reply stay in the browser.
Sample request logs show metadata: organisation, project, environment, key id, route, task, agent, workflow, trace, model, token counts, cost, latency, status and which levers ran. Prompt and response text stay off unless content logging is on for that project. In the sample, content logging is off except for one project that is opted in so the switch can be shown.
The privacy settings page can show a retention choice, redaction ticks for email, phone and secrets, and a residency choice of eu, us or customer-vpc. Saving shows a notice and does not store the change. It does not enforce a region. Full prompt capture is a paid extra and is off by default. A self-hosted install uses your Postgres. The open-source gateway needs no licence key. A lapsed licence switches to pass-through and does not block traffic. This site does not publish that image.
Replays, connected providers and review
In development. Replay, provider connection and secret-manager loading are not running on this website. The gateway is not deployed. It does not encrypt traffic, it does not encrypt stored keys, and it does not rate-limit. This site does not accept a production provider key. A later replay would go only to a provider you had connected and left enabled, with your own key. A later dashboard save would keep the last 4 characters and who connected it. The full key would not be shown again. A self-hosted gateway would read the key from an environment variable or a secret reference, and the key would stay in your environment. This site would learn only that the provider is connected. Fetching a secret from a cloud manager is not built. Disconnecting a provider would stop pending replays and return a switched route to the original model. That control is a preview in this browser, not a route on a gateway.
In development. Human review of a replay sample would happen only after you opt in. Voice and audio are treated as sensitive personal data and would not be included in human review unless you turn that on separately. Without those consents, only automatic checks would be used. You would set a monthly cap and a per-test cap on replay spend, and the estimated cost would be shown before a test runs. None of that runs here. This sample site does not keep replay audio, images or video. A hosted gateway would keep replay samples in the customer database for the retention period you set. That hosted service is not running here, so no retention period is in force on this website.
What this policy does not say
Parezen does not claim a security certification. This policy does not name a sub-processor. Sign-up and form details are not sent to one. The data-handling docs describe the same metadata rules for the sample product.
Contact
Privacy, legal, support, sales and security questions go to [email protected]. That address is the contact for this site.
The terms cover use of the website.