Skip to main content
Selfhost terms

The fine print, in full.

Event Schedule LLC

These are the terms for running your own instance. The clauses below are reproduced word for word; the notes in the margin are a plain-language summary and are not part of them.

At a glance

Selfhosting Terms

Applies to
Any instance you run yourself
Counterparty
Event Schedule LLC
Code license
Attribution Assurance License
Governs
Support, connected services, future releases
Does not govern
The data on your own server
Feature gates
None on a selfhosted instance

Every Pro and Enterprise feature is included when you run it yourself: with hosting turned off, the app's plan checks pass for every schedule. Two things exist only here, on the far side of that switch: one-click updates from inside the admin panel, and Auto Import, which reads a list of web pages you choose once a day and imports the events it finds there, optionally keeping only those in cities you name. The license asks only that the original attribution stays in place.

Recital

All features from the hosted app are included in the open-source code. By self-hosting Event Schedule, you accept the platform "as is" and "with all faults," assuming all risks associated with running and maintaining your own instance. Use of the source code is governed by the Attribution Assurance License; these Terms govern your relationship with Event Schedule as a service and support provider.

The boundary

Most of these clauses exist because of one line.

On a selfhosted instance the data sits on your side of it. That single fact is why the clauses below spend most of their words on what Event Schedule cannot do.

Scroll the table sideways for the second column.

What runs on your infrastructure and what Event Schedule sees, item by item
Item On your infrastructure On eventschedule.com
The database Schedules, events, sales, followers, all on your MySQL server No access
Uploaded files Flyers, logos and event graphics on your disk or object store No access
Payments Your own Stripe or PayPal account, and your own payouts No platform fee, no access
Outgoing email Your mail server, configured in your .env Not routed through us
AI features Your own provider API key, read from your .env Not proxied by us
Crash reports Off unless you set REPORT_ERRORS=true Received only if you opt in
Update checks Your instance asks GitHub for the newest release Nothing, that request goes to GitHub
Public listings Federation stays off until an admin turns it on Public event details and your site's address, name and contact email, if you opt in
Translation edits Interface wording an admin changes Only edits an admin shares

The rule between the last two columns is the whole argument of this page. Nothing on the left of it is reachable from eventschedule.com. Only the last four rows reach anyone other than you and the providers whose keys you add, and the three that carry any of your own data are off until you turn them on.

What crosses it

Five things cross it. Four start off.

The Data Use clause below only reaches data your instance actually transmits. This is that list in full: four switches that begin in the off position, and one read-only version check.

Off by default

Crash reports

Error reporting is off out of the box. Until REPORT_ERRORS is set to true there is no reporting endpoint configured at all, so nothing is sent when something breaks. Turned on, it sends the server's errors and the errors your visitors' browsers hit to Event Schedule's Sentry project: the error, the browser and the IP address it connects from, and the page address with its query string and its ticket and unsubscribe secrets removed and email addresses masked. Never form contents. An install that sets IS_HOSTED to run its own hosted service reports nowhere either, unless it sets REPORT_ERRORS or names its own project in SENTRY_BROWSER_DSN.

Off by default

Public listings

Federation shares your public events with the eventschedule.com listings, and every listing links back to the event on your own site. Turning it on also registers your instance: its address, its name and the contact email the admin enters. An admin has to turn it on, and a schedule is only listed once someone who manages it chooses to list it.

Your keys

Anything you connect

Stripe, PayPal, Google and Microsoft calendars, CalDAV, Google Wallet passes, AI parsing: each one runs on credentials you add yourself, and each one talks to that provider directly rather than through Event Schedule.

Off by default

Translation sharing

If an admin edits the interface translations, they can choose to share the edits so they reach every install. Sharing sends the edited strings with the install's random ID and version number, and nothing else. It only happens when an admin presses Share, or turns on automatic sharing.

Read only

Update checks

The updater compares your installed version against the public releases of the eventschedule/eventschedule repository. It reads a version number; it does not send your data anywhere.

Everything else stays where you put it. Read the clause it belongs to

The terms

Ten clauses, word for word.

Nothing here has been shortened for the rebuild. The margin note beside each clause is a summary and is not part of the terms.

Data Ownership & Access

Self-hosters own their data and bear full responsibility for it. Event Schedule cannot access, modify, or remove self-hosted data stored on your private infrastructure. Users must handle any losses or damages affecting their clients independently.

Amendment Rights

Event Schedule may modify these terms regarding support, connected services, and future releases with notice via email, dashboards, or websites. Changes become binding seven days after notice, unless longer periods apply by law. While the open-source license for a specific version of the code is permanent, users must accept updated Terms to continue receiving official updates or technical support.

Eligibility

Users must be 18 years of age or older and confirm compliance with applicable laws. Prior suspension or removal from Event Schedule services disqualifies new access to our official support and update channels.

Personal Responsibility

Users are responsible for securing their credentials and handling all legal obligations regarding data privacy, copyright, and international regulations independently.

Your Obligations

Users remain solely responsible for goods, services, and customer obligations facilitated through the platform.

Customer Service

Users provide their own customer support. Event Schedule only assists account users with platform functionality on the hosted version or via specific enterprise support agreements.

Data Use & Privacy

For self-hosted instances, this section applies only to data explicitly transmitted to Event Schedule (e.g., via opted-in crash reports, update checks, or cloud-relay features). In such cases, you grant Event Schedule a non-exclusive, fully sublicensable, worldwide, royalty-free right to use, copy, and store that specific data solely for the purpose of providing services to your instance.

Restricted Businesses & Sanctions

Illegal activities and use in high-risk jurisdictions (Cuba, Iran, North Korea, Crimea, Syria) are prohibited. While the software is open source, Event Schedule does not provide support or services to prohibited categories, including gambling, telemarketing, unauthorized multi-level marketing, or weapons sales.

Indemnity & Liability

Users indemnify Event Schedule against claims arising from platform use, agreement violations, or third-party rights infringement. Event Schedule disclaims liability for damages, lost profits, or data loss, as further detailed in the Attribution Assurance License.

As is
All faults

Communication & Resolution

For privacy and data concerns, contact: [email protected]

Running the hosted app at eventschedule.com instead? The Terms of Service and Privacy Policy cover that arrangement.

Execution

Run it yourself. Own the whole of it.

No license fee, no per-event charge, no platform fee on ticket sales, and no plan gates once hosting is turned off. What you pay for is the server, the processing fees Stripe or PayPal charge, and whatever the keys you add yourself cost.

Event Schedule LLC

Provides the code under the Attribution Assurance License, and the support, connected services and releases these terms govern.

You, the operator

Hold the server, the database, the uploads and every key in the .env, and carry the risk that comes with holding them.