Scoped requirements and data-flow documentation
We interview the events team and their vendors, then hand you an exact list of endpoints, objects, field mappings, and required permission scopes.
For IT and security teams
Security & Trust: everything you need to review and approve us, in one place.
Your events team wants their platforms connected before registration opens, and you need a clear answer on credentials, scopes, data residency, and offboarding. We wrote this page so you can evaluate how we operate without sitting through a discovery call first.
Sound familiar?
The Friday afternoon ticket asking for CRM admin credentials.
A ticket lands in your queue: the events team signed a contract with an event platform and wants a full-admin API user in your CRM before Monday. Nobody has documented which objects will be written, where attendee PII is stored in transit, or how access gets revoked when the conference ends.
- The business side picked the event software first and looped in security two weeks before launch.
- Vague vendor answers about where attendee data is cached and who can query it.
- Requests to email shared admin passwords or long-lived API keys with unrestricted scope.
- Hard conference dates that leave very little runway for a thorough architecture review.
We live in your world
Hard event deadlines don’t mean security controls have to slip.
Conferences run on fixed dates and requirements often shift close to show time. We handle that pressure with least-privilege credentials, full sandbox validation before production sign-off, and an immutable audit log of every record we move. We gather the functional requirements directly from your events team and bring you a complete specification early, rather than dropping an urgent request in your lap.
How we do it
What we take off your team’s plate
Managed build, sandbox testing, and monitoring
We build, test, and monitor the integration end to end. Your team reviews and approves the architecture without having to write or maintain glue code.
Record-level observability whenever you want it
You get access to a live status dashboard showing every run, payload count, error alert, and record-level audit log.
Scheduled decommissioning after the event
When the post-event sync window closes, we shut the pipeline down on the date you set, purge transient logs, and confirm credential revocation.
What done looks like
You have a documented architecture, least-privilege API scopes, a named approver before production cutover, and a scheduled revocation date once the event wraps.
Security & trust
The questions reviewers ask us
These are the questions reviewers ask us most. Where an answer depends on your project, we confirm it in writing during the free consultation, before any access is granted.
How we connect to your systems
We use each platform’s approved sign-in method for integrations where one exists. Where it does not, we ask you to create a separate integration user with only the permissions the work needs. We never use a staff member’s personal login.
Exactly what we can access
Before anything is built you receive a written list of each system, each type of record, and whether we read it, write it, or both.
Read-only until you approve
While we plan, we ask for read-only access to confirm your systems and data support the plan. Write access is enabled for the test build, and for production only after your approval. In test mode the platform blocks any change to a live system.
Where your data goes
You receive a one-page diagram showing what data enters the integration, where it is held, which services touch it, and where it ends up. Your own systems remain the source of truth.
Hosting and location
The platform runs on Google Cloud in the United States. Your data and its backups stay in US locations. If a contract requires data to stay in another region, tell us during the consultation.
Your credentials
The keys and tokens you give us for your systems are encrypted at rest and in transit. They are never written to logs. Values are hidden in the dashboard. An administrator can reveal one value at a time, and each reveal is limited and recorded with the name of the person who did it.
Encryption
Data is encrypted in transit. Stored data sits on Google Cloud, which encrypts data at rest by default.
Kept separate from other customers
Each customer’s data is separated by design, not by a filter someone has to remember to apply. Automated tests check on every change that one customer can never see another’s data.
How your team signs in
Your team signs in to the dashboard with their own Microsoft work account, so we never hold your passwords and your own sign-in policies apply. Access is by invitation only, tied to the invited email address and to your organization.
A record of every change
The dashboard keeps a log of each record the integration handled, when it last synced and the data it carried. Administrative actions, such as stopping a run or revealing a credential, are recorded with the person who took them.
What we store
The platform keeps a copy of the records it moves, along with their change history. That is how it knows what changed and avoids sending repeats. Your own systems remain the source of truth.
How long we keep data
Run logs are kept for 30 days and delivery logs for 90 days, then deleted automatically. The integration runs until the shut-off date you set with us.
Backups and recovery
Daily and weekly backups, the ability to restore to any point in the previous seven days, and a second copy held in a separate US region. We rehearse a full restore every quarter.
Third parties
Google Cloud for hosting, Microsoft for sign-in, and Postmark for notification emails.
Testing before production
Everything is built and tested in a sandbox first. For platforms without a sandbox, we can use a test event or set up a simulated sandbox. Your team reviews it against a checklist, and nothing goes live without your sign-off. Show day fixes and changes have an expedited process that ensures safety and speed.
If something goes wrong
Our team is alerted automatically when a run fails, stalls or cannot recover.
Independent assurance
We complete your security questionnaire and provide our documentation on request.
When the project ends
We switch the integration off on the agreed date, remove our access, and hand over the documentation, so you are never locked in.
What we will not do
Our red lines
We never ask for a shared password or a staff member’s personal login.
We never ask for more access than the work needs.
We never change anything in production without written approval from a named person on your side.
Where a system has no API, we work from scheduled exports and reports first. Anything beyond that happens only with the system owner’s written consent, through a dedicated account your IT team creates, with every action logged.
For your review
Want this as a document?
Email us and we will send a security summary you can attach to your review, and complete your vendor questionnaire. A downloadable version is on the way.
How every project starts
We start with a free consultation - about two hours of discovery kicking off with a 30-minute call. We map out where your data lives, the business rules your event follows, and what your IT team will need to see. You keep that document whether you hire us or not.
If you do hire us, a first integration is typically $3,500 to $7,500, and reusing it for your next event costs 40 to 90 percent less. No subscription. No annual contract.
Money back guarantee. If you’re not satisfied with the integration, we’ll refund you.
Start with a free consultation.
No obligation. You’ll leave with a clear requirements document whether or not you work with us.
Not sure if we’re the right fit? contact@eventdata.pro
All solutions · For your role