Privacy
Privacy notice
What officeunbound.com collects, why, where it is kept and for how long. The short version: reading this site sets no cookies and loads nothing from anyone else. Only the forms collect information, and only what you type into them.
Summary
Last updated .
- No analytics, tracking pixels or advertising cookies.
- No third-party scripts, embeds or fonts. Everything is served from this site, including the typefaces.
- One cookie,
ou_form, set only on form pages, to protect the form against cross-site request forgery. - The spam check on forms runs in your browser and contacts only this site.
- The hosting server keeps ordinary access logs for operations and security.
- What you send through a form goes to the Office Unbound team’s private support system and is used to reply to you and to understand interest in the project. It is not sold or shared, and it does not put you on a mailing list.
Reading the site
Pages on this site are plain HTML, CSS and one small script of our own; form pages also load the spam-check script described below, served from this site. There is no analytics service, no tag manager, no social-media widget and no advertising. Fonts are self-hosted, so loading a page does not send your IP address to a font provider. No cookies are set while you read.
Server logs
Like any web server, the server hosting this site records requests in its access logs: your IP address, your browser’s user-agent string, the URL requested, and the time and response. These logs are kept by the hosting server for operating the site and for security, for example to diagnose errors and to identify abusive traffic. They are not used to build profiles of visitors or combined with form submissions for marketing.
Using a form
Contact, early access, MSP partnership inquiry and developer interest.
The cookie
When you open a form page, the site sets one session cookie named ou_form. It holds an identifier for a server-side session that contains a single random token, used to check that a submission came from the form you loaded and not from another website (CSRF protection). It does not store what you type. It is marked HttpOnly, expires when you close your browser, and is strictly necessary for the form to work, which is why there is no cookie banner.
The spam check
Forms use ALTCHA, a proof-of-work check: your browser solves a small computational puzzle before the form is sent. The script is served from this site and contacts only this site. There is no third-party CAPTCHA service, no image puzzle and no tracking. The form also has a hidden field that people do not see and automated scripts tend to fill in.
What the forms collect
Only the fields on the form you use. Name and email are required on every form so that we can reply. Everything else is optional unless marked.
| Form | Fields |
|---|---|
| General contact | Name, work email, organization, role, what the message is about, message |
| Early access | Name, work email, organization, role, main interest, organization size, current platform, optional note |
| MSP partnership inquiry | Name, work email, company, role, number of managed customers, users across those customers, intended hosting model, existing infrastructure, migration interest, capabilities that matter most, optional note |
| Developer interest | Name, email, organization, areas you could help with, relevant experience, optional message |
Values for choice fields are kept only if they are one of the listed options; anything else sent with the form is discarded.
Where a submission goes, and how long it stays
A submission creates three records. Each has a different purpose and a different lifetime.
- Support ticket
- The submission is delivered as a private ticket in the Office Unbound team’s support system, which runs on infrastructure operated by the site’s operator, not by a third-party helpdesk service. This is where your message is read and answered. It is kept for as long as the conversation and the interest it records stay relevant, and is deleted on request.
- Delivery record
- The web server keeps a local record of each submission and whether it reached the support system. This is how a message is not lost if the support system is briefly unreachable, and how an accidental double submission is recognized instead of filed twice. These records are deleted after at most 90 days.
- Abuse log
- When a submission is refused, for example for failing the spam check or exceeding a rate limit, a short line records the time, the reason and shortened keyed hashes of the IP address and email address. It never contains your name, message, or raw IP or email address. It exists so repeated abuse from one source can be recognized, and is pruned after 14 days.
- Rate limiting
- To slow automated submissions, the site counts recent submissions per IP address and per email address over hourly and daily windows. The counters are stored under keyed hashes, not as readable addresses, and only hold timestamps from within the last day; older entries are discarded as the window moves.
How it is used
Form submissions are used for two things: to reply to you, and to understand interest in the project. For example, which workloads early-access registrants want to test first, or what MSPs need from multi-customer administration. That understanding informs the roadmap. If you registered for early access, we may contact you when a component relevant to your stated interest reaches early testing, or when the roadmap changes in a way that affects it.
Your information is not sold, rented or shared with anyone else, is not used for advertising, and is not added to a mailing list.
Access, correction and deletion
You can ask what we hold about you, ask for it to be corrected, or ask for it to be deleted. Send the request through the contact form, choosing General information, and use the email address you originally submitted with so we can find the records. We will confirm what was done. Deleting a ticket removes your submission from the support system. Delivery records and abuse-log lines expire on their own schedules described above.
If this notice changes, the date at the top of the summary changes with it.