See how this website handles your details.
Review how the website handles your company context and visits. Forms display a summary in your browser, while website requests and visit statistics support page delivery and improvements.
Understand forms, page requests and visit statistics.
The product pages explain OrgRelay’s workflow through text and diagrams. The security page describes the files and scripts supplied by this website, and the website terms explain the preview interaction. This notice covers that website behavior.
The company request, demo context and contact page use company name, email, size band and industry. When you send the form, these four fields are stored, together with the page, language, time, IP address and browser type, in a database on a server that OrgRelay manages. Only the OrgRelay team uses them, to reply to your request and arrange a demo; they are not sold or used for advertising. To see or delete what you sent, reply to our email or tell us through the contact page, and we will delete it.
Check your details before you send them.
Selecting preview checks required fields and email format. The script inserts the values as text in a summary. You can return to edit; refreshing resets the application display. Browser features, extensions and copies you make are controlled through your own device and browser.
Use the company-setup guide to think through an initial workflow. The integration requirements and knowledge workflow discuss company-data questions separately from this four-field interaction.
- 01
Enter four details
Provide only the company label, email, size band and industry requested.
- 02
Read the summary
The values appear as text in the current page.
- 03
Return to edit
Adjust the displayed context or refresh to reset the application view.
Information in the local preview
| Information | Use in this website | Application handling |
|---|---|---|
| Company and email fields | Display a local summary | Current page only |
| Size band and industry | Display the chosen context | Current page only |
| Requested page path | Serve the requested document | May appear in terminal request logs |
| Menu and billing selection | Change current page presentation | Current page only |
Page requests retrieve website files.
Opening a page or an asset makes an HTTP request to the preview origin. The local server may print the requesting address, path, time and response status in its terminal. Keep sensitive information out of page addresses and query strings.
The site serves its own fonts, core interface scripts, styles and illustrations. Cookie information explains page-level state. Reading the Agent pages or workflow illustrations retrieves those website files.
The public website uses 51LA and Google Analytics 4 to understand page visits, traffic sources and device categories. These providers receive visit information through their own services and may use cookies or similar identifiers. Form fields are not sent to these analytics providers; the analytics setup reads page activity separately. Local previews keep visit measurement switched off.
| Mechanism | Website behavior | Information path |
|---|---|---|
| Page and asset requests | Served by the preview origin | Requested path and ordinary HTTP details |
| Form preview | Runs in the page | Four values displayed in the browser |
| Form response storage | Not implemented | Current page display only |
| Website analytics | 51LA and Google Analytics 4 | Page visits, traffic sources and device categories |
Evaluate company data as its own requirement.
A service handling company records needs clear purposes, access, providers, retention, deletion and contact arrangements. People in control and the approval workflow help identify which people need the information and which decisions they own.
The resource library helps define a focused first process. Read about OrgRelay and compare plan directions while recording the data questions your company needs answered before a service agreement.
Questions, answered.
Which details do the forms ask for?
Company name, email, company-size band and industry.
Where do those four details go?
They are sent to OrgRelay so the team can reply within 1 business day, and kept on OrgRelay’s own server until you ask us to delete them.
What may the preview server record?
Ordinary HTTP request details may appear in its terminal, including address, path, time and response status.
How can I change the summary?
Return to edit the fields. Refreshing resets the application display.