Request a pilot.
Auth0 verifies your work email and keeps authentication logs. RedactWall records verified email, identity-provider and account references, request ID and timestamps. Request records are kept for the life of the service. Support email is deleted 24 months after receipt. Do not include customer records, credentials or prompt contents.
When the in-app pilot entry is available, choose Request a guided pilot and complete Auth0 verification with your work email. The app records your request after it verifies your identity and email. A RedactWall employee reviews the request before a workspace can be created. Sending a request grants no access, enrollment, or coverage.
Pilot: up to 50 managed Windows 11 devices in Chrome; typed or pasted text in the signed-in ChatGPT composer. Excludes files, images, voice, other modes or responses, Edge, BYOD and other apps. Managed-device proof undated.
Before you enroll
Contact data and pilot terms.
The full contact-data notice is below. Contact records follow a retention schedule with disclosed gaps, and the pilot terms are a draft awaiting counsel; review both before sharing further details. Requesting a pilot is not workspace access.
Before you share contact details
Email to support@redactwall.com sends your address, message and any attachments to Microsoft 365 for support and pilot inquiries. Only the owner, Eric, has access to that mailbox: its access list was verified on 2026-09-25, with no delegates, send-as grants or forwarding.
When identity-based requests are enabled, Auth0 handles verification and keeps authentication logs. RedactWall records your verified email, identity-provider and account references, a request identifier and timestamps. Authorized RedactWall employees review the contact and request; approval and setup status are recorded separately. Verification does not grant pilot access.
Contact records follow a retention schedule adopted on 2026-09-25, not yet reviewed by counsel. Support and pilot-inquiry email is deleted 24 months after receipt, enforced by an Exchange Online retention policy applied on 2026-09-25; the oldest message was received on 2026-08-24, so none reaches that age before 2028-08. A deleted message is then purged after Exchange's recoverable-items window. Auth0 keeps its own authentication logs for 1 to 30 days by plan; the plan on this tenant was not read back. Our streamed copy of those logs is deleted after 365 days by an enforced retention setting. Auth0 identities with no workspace and no sign-in for 24 months are removed at a quarterly review. Pilot request, requester, contact and approval records in the platform database have no deletion today: the database refuses to delete them because they anchor the identity audit chain, so they are kept for the life of the service. A backup set expires about 9 weeks after it is superseded, but new backups keep capturing the retained database records. Requests about your own data are answered within 30 days. The employee activity and training retention periods do not cover these records. Ask about the status of the pilot terms before sharing more information.
For an initial email, use your work email address and ask about the status of the pilot terms. Keep organization and workflow details, customer records, credentials, prompt contents and attachments out of the initial message.
Read the contact-data noticeEmail contact options
Ask about the pilot terms by emailOpens your mail app with a question about the pilot terms. A pilot request follows later; this email does not submit one. Do not include organization or workflow details in the initial message.
No mail app connected? Copy this address into your email service.
If you copy this address, ask about the status of the pilot terms. Keep organization details, customer records, credentials and prompt contents out of your first email; copying the address does not reserve a place or provision workspace access.
The guided pilot is free. A draft pilot agreement with processing terms has been prepared for counsel review. It has not been reviewed by counsel, agreed or signed, and it must be reviewed and agreed before any enrollment. Paid conversion uses manual invoicing by default, or card where configured.
The guided setup path
A clear next step at every stage.
- 1
Confirm the fit
Review the contact-data gaps before sharing any of these details. Name a policy owner, the managed Windows 11 and Chrome cohort, and the ChatGPT workflow you want to govern. Identify any separate Anthropic application path.
- 2
Request guided setup
In the app, choose Request a guided pilot and complete Auth0 verification with your work email. The app records your request after it verifies your identity and email. A RedactWall employee reviews the request before a workspace can be created. Sending a request grants no access, enrollment, or coverage. A draft pilot agreement with processing terms has been prepared for counsel review. It has not been reviewed by counsel, agreed or signed, and it must be reviewed and agreed before any enrollment. Billing applies to paid conversion.
- 3
Approve workspace access
After a RedactWall employee approves the request, the workspace is provisioned and the requester is emailed as its owner. Your organization approves the policy and the people allowed to review evidence before enrollment.
- 4
Enroll one managed device
Start with one Windows 11 device and its managed Chrome profile. Confirm device health, the installed extension and the approved policy before use.
Open the one-device setup path - 5
Prove the path with synthetic data
Run an agreed safe test, check what reached the destination, and match the decision to its evidence. Verify the Anthropic gateway separately when included.
- 6
Expand after the proof
Review failures and coverage gaps before moving to five devices, then the agreed cohort of up to 50. Each expansion requires a verified release and a working rollback path.
Open the IT rollout path - 7
Convert
Request conversion from the Overview banner in the console. A RedactWall employee confirms the seats and the terms, you pay by invoice or by card where that deployment is configured for it, and the pilot expiry is lifted once the payment is recorded.
What the last step converts to is published on the pricing page.
Who supports the pilot, and when
- Assigned operator
- EricThe named person accountable for the pilot during its declared hours.
- Declared support hours
- Monday to Friday, 09:00 to 17:00 US Central (America/Chicago), excluding US federal holidays. First response within 1 business day. No on-call or out-of-hours coverage.Stated with an IANA time zone, so the hours mean the same thing on both sides of the agreement.
- If there is no response
- If there is no response within 2 business days, you may pause or cancel the pilot with no obligation.What you may do when the assigned operator does not answer.
Before you share contact details
Email to support@redactwall.com sends your address, message and any attachments to Microsoft 365 for support and pilot inquiries. Only the owner, Eric, has access to that mailbox: its access list was verified on 2026-09-25, with no delegates, send-as grants or forwarding.
Contact records follow a retention schedule adopted on 2026-09-25, not yet reviewed by counsel. Support and pilot-inquiry email is deleted 24 months after receipt, enforced by an Exchange Online retention policy applied on 2026-09-25; the oldest message was received on 2026-08-24, so none reaches that age before 2028-08. A deleted message is then purged after Exchange's recoverable-items window. Auth0 keeps its own authentication logs for 1 to 30 days by plan; the plan on this tenant was not read back. Our streamed copy of those logs is deleted after 365 days by an enforced retention setting. Auth0 identities with no workspace and no sign-in for 24 months are removed at a quarterly review. Pilot request, requester, contact and approval records in the platform database have no deletion today: the database refuses to delete them because they anchor the identity audit chain, so they are kept for the life of the service. A backup set expires about 9 weeks after it is superseded, but new backups keep capturing the retained database records. Requests about your own data are answered within 30 days. The employee activity and training retention periods do not cover these records.
For an initial email, share only a brief, non-sensitive description. Keep organization and workflow details, customer records, credentials, prompt contents and attachments out of the initial message.
Read the contact-data noticeWrite to support@redactwall.com. Declaration last checked 2026-09-25.
Before you enroll
Read what the pilot inspects, stores and keeps in the privacy notice, and who processes what on subprocessors. A draft pilot agreement with processing terms has been prepared for counsel review. It has not been reviewed by counsel, agreed or signed, and it must be reviewed and agreed before any enrollment. The data processing addendum is an unreviewed internal draft. See their status under documents for procurement.
Already have workspace access?
Sign in to the console assigned to your organization. Requesting a pilot does not grant access.
Log in to the console