The short version
- MyEventScape does not currently use generative AI or large language models anywhere in the product. Nothing you read in the app is written by a model.
- Your event data, documents, and messages are not used to train any AI model — ours or anyone else’s — and are not sent to any AI provider.
- The platform does compute things for you. Every one of those figures is an estimate or a checklist, offered to speed up your work and never to replace a professional judgment or an official decision.
- No automated process makes a decision about a person that produces legal or similarly significant effects. People approve, deny, and sign.
What is actually automated
These features are rule-based and arithmetic — the same inputs always produce the same output, and the logic is fixed by us rather than learned from data. None of them is a prediction engine.
- Permit requirement matching. Selecting an event type and its activities produces a checklist of permits and approvals that commonly apply, with links to the responsible office.
- Event readiness scoring. A weighted score computed from rows already in your workspace — tasks, vendors, documents, dates — to rank what is furthest behind.
- Site-plan geometry. Areas, lengths, and distances derived from the shapes you draw on the map.
- Crowd-area estimates. A headcount produced by multiplying the area you drew by a density figure you selected.
- Address lookup. Third-party geocoding that turns a typed address into approximate map coordinates.
- Budget totals and projections. Sums, variances, and forecasts calculated from the line items you enter.
- Document and compliance tracking. Status, expiry, and reminder logic applied to files that people upload.
Limits you need to take seriously
Four of the outputs above sit close to public safety or legal exposure. For those, the estimate is a starting point for a conversation with a qualified person, not a substitute for one.
- Crowd-area headcounts are not occupant load calculations. The figure is area multiplied by a density preset. It does not perform an egress analysis, apply an adopted fire or building code, account for exits, aisles, terrain, stage geometry, structures, or assembly classification, and it is not the work of a licensed engineer or fire protection professional. Occupancy limits for your event are set by the fire marshal and the authority having jurisdiction.
- Map measurements are not a survey. Dimensions come from web map geometry over third-party basemap imagery that may be outdated, seasonally different, or misaligned with the ground by a meaningful margin. Nothing produced here is a boundary survey, a legal description, or an as-built drawing, and it should not be used to locate a property line, easement, or utility.
- Permit checklists are not a legal determination. Requirements vary by jurisdiction, parcel, date, and the details of your event, and they change without notice to us. The checklist may list permits you do not need or omit ones you do. Confirm every requirement with the issuing authority.
- Tracking a document is not verifying it. Recording that a certificate of insurance or a license was uploaded and marked approved says nothing about whether the policy is genuine, in force, adequate in limits, or correctly endorsed. That verification is yours to perform.
More generally, nothing MyEventScape produces is legal, engineering, insurance, financial, tax, or public safety advice, and no output is an official act of any government body. Where a figure from the platform will inform a safety decision or a regulatory submission, have the responsible professional check it first.
People make the decisions
Approvals, denials, conditions, signatures, and permit issuance are actions taken by identified people with the authority to take them, and the record shows who did what and when. The platform routes work, computes totals, and keeps the trail; it does not approve an event, deny an application, score an applicant, rank a vendor’s trustworthiness, or otherwise profile anyone. If that ever changes, the change will be disclosed here and in the product before it affects anyone, along with the means to obtain human review.
Our commitments on AI and your data
- We will not use customer content — event records, documents, site plans, messages, or personal information — to train generative AI models, and we will not license it to anyone else for that purpose.
- We will not send customer content to a third-party AI provider without disclosing it on this page and updating our subprocessor list first.
- If we introduce an AI-assisted feature, output generated by it will be labeled as such in the interface, and its purpose, limits, and provider will be described here.
- AI-assisted features, if added, will remain advisory. A model will not be given authority to approve, deny, or condition an event.
Automated outputs you did not ask for
Some automation runs quietly: reminder emails on approaching deadlines, expiry flags on compliance documents, scheduled archiving of past events, and rate limiting that may temporarily block unusual traffic. These act on schedules and thresholds we set. If one of them affects your access or you believe a reminder or flag fired incorrectly, tell us and we will look at it.
Telling us something is wrong
If an automated figure, checklist, or measurement looks wrong, please report it to legal@myeventscape.com with the event and the value you saw. Corrections to permit data and calculation logic are a standing part of our work, and a report from someone who knows the jurisdiction is the fastest way we learn about a gap.