Skip to content
rextail
Home Architecture Company
Become a design partner ↘
Rextail / Privacy Rev. 03 Design-partner intake and site analytics Website data handling

Privacy

What we collect,and what we do not.

This page describes the information recorded by the Rextail website. It covers design-partner requests, pageview counts, and the form’s abuse-prevention checks.

Who is responsible

For questions about information submitted through this website, contact [email protected].

If you fill in the form

The design-partner form is the only place this site asks for anything about you. It stores exactly the six fields you type, plus six the system adds:

What the design-partner form stores
Name, work email, company, roleSo we can reply to you, and know who we are replying to.
Engineering team sizeOne of five ranges. Used to judge whether the architecture questions we would ask you are the right ones.
Your answer on lifecycleUp to 1,000 characters, in your words. This is the part we actually read.
Source, status, counters, timestampsAdded by us: a row id, which page the request came from, where it has got to in our reply queue, how many times you have submitted, and when the first and most recent arrived.

The form records your request so the Rextail team can assess it and contact you about becoming a design partner.

If you only read the page

Successful page loads can record: the path, the site host, the referring site's hostname when you arrived from another site, the country your request came from, a row id, and the time. These are the fields in the website’s pageview table.

Only page loads are counted — not assets, not API calls, not requests that fail — and there is a per-worker ceiling on how many rows can be written, so under a traffic spike some page loads are simply not recorded. The log is deliberately lossy; it is a traffic count, not an audit trail.

Deliberately not stored: your IP address, your full user-agent, and any per-visitor identifier in the pageview table. This answers how much traffic, from where, to which page. It cannot answer who, and it cannot follow you between visits or between sites.

Abuse prevention

The form uses a hash derived from the date and your network address to count submission attempts. The throttle table stores that key, an attempt count, and the start of its time window. It does not store the raw address.

Hashing is not a guarantee of anonymity. The hash changes with the date, but stored rows do not disappear just because the date changes.

When Cloudflare Turnstile is enabled, the form sends a challenge token and your IP address to Cloudflare for verification.

Who else sees it

Cloudflare serves this website and hosts its database. Requests pass through Cloudflare’s infrastructure, so the database fields listed here do not describe all information the hosting provider may process. The website code does not install advertising trackers or third-party analytics scripts.

How long it is kept

The website currently has no automatic deletion schedule for design-partner requests or pageview records. Expired throttle rows are eligible for cleanup during subsequent form submissions; cleanup is not a scheduled task.

To ask about retaining or deleting information you submitted, email [email protected].

Changes

This description is maintained with the website. Contact [email protected] if you have questions about these records.

Become a design partner↘ Back to Rextail↗
rextail

AI-native infrastructure for software development and operation.

Built for autonomous software / Rextail rev. 03[email protected] ↗Privacy