A useful first message explains the business concern without including credentials or sensitive evidence.
01 /
Appointment requests
The booking form sends your consultation details and preferred time to the booking service for team review. A request is not a confirmed appointment. Use high-level notes; do not include passwords, keys, payment details, or incident evidence.
02 /
Project brief download
The homepage brief tool creates a downloadable outline on your device. It does not send a message to the team. Share the resulting brief through a contact process you agree with Saint.
03 /
Public contact routes
The telephone and Discord links help begin a conversation. Discord is a third-party community service; arrange a suitable process before sharing confidential business information.
Before sensitive work begins
Establish the boundaries before the access.
Ask these questions during scoping and record the answers in the relevant agreement.
Who may authorize the work and which assets are in scope?
What access and evidence are required, and can access be limited?
How will confidential materials be transferred and who may receive them?
What retention, return, closeout, and access-revocation arrangements apply?
Which deliverables, review steps, dependencies, and limitations are included?
Which confidentiality, data-processing, or supplier documents are needed?
Report a website security concern
A clear route to the team.
If you believe you have found a security issue affecting Saint’s website or services, call (737) 228-5044 to arrange an appropriate reporting channel.
Start with a concise description.
Describe the affected service and the observed behavior at a high level. Do not send credentials, personal data, exploit payloads, or sensitive evidence through a public form or Discord channel. Contacting us does not authorize testing, grant safe harbor, or establish a bug bounty program.