REA Privacy
Privacy
Our web servers keep access logs, including masked IP addresses and user agent, for security and operations. Log files are rotated when they reach a size limit, and rotated files are deleted 30 days after rotation.
This page covers the server access logs for reacontrolplane.com (including www.reacontrolplane.com) and console.reacontrolplane.com. Requests to api.reacontrolplane.com are handled by our API gateway, which keeps its own operational logs. If you sign up for a Trial, we also store the name, work email, company and optional phone you enter, and, for API use, per-request usage records (such as model, token counts and status) and TraceGuard receipts without message content. Questions: elijah@reacontrolplane.com.
Server access logs
- Our web server logs each request: the time, the site name and page requested (with sensitive query values removed), the method, protocol, response status, size and timing, the connection's source port, the TLS version, cipher and server name, the request headers your browser sends (for example user agent, referring page, language and browser hints), and the response headers we send back, except the headers we remove from the log entry: the sensitive and forwarding headers described below, and the From header (which can carry an email address).
- Your IP address is masked before it is written: to /24 for IPv4 (the last of the four numbers is dropped) and to /48 for IPv6. Forwarding headers that can carry IP addresses (such as X-Forwarded-For) are removed from the log entry.
- Keys, tokens, cookies and authorization headers are stripped from each entry. Values of sensitive query parameters are replaced with
REDACTED. - Log files are rotated when they reach a size limit; rotated files are deleted 30 days after rotation; an entry can stay in the current file longer on a low-traffic site. Logs are used for security and operations.
Contact
Questions about this page: elijah@reacontrolplane.com