Terms of service

Previous version — no longer in effect. This is the version of 2026-10-26. Read the current version.

Last updated: 2026-10-26

1. Who provides this service

ERDism is operated by Cutaway Works, based in the Republic of Korea. In these terms, "we" and "us" mean Cutaway Works, and "you" means the person using ERDism.

You can reach us at [email protected].

2. Accepting these terms

These terms cover ERDism at erdism.com: the website, the application, and the public documentation.

By creating an account or using the service, you accept these terms and confirm that you have read our Privacy policy. The Privacy policy explains how we handle personal data; it is not something you are asked to agree to. There is no separate box to tick. Every screen where an account can be created — signing up with an email address, or continuing with Google or GitHub — says so directly under the button, together with the minimum age (section 4).

If you use ERDism on behalf of a company or another organisation — for example by signing up for it, or by working in a workspace that stands for it — you confirm that you have the authority to accept these terms for it, and these terms then apply to it as well as to you.

3. The service

ERDism is where a team keeps its database schema. Everyone who works with the database reads the same live schema, every change to it is recorded, and changes are reviewed before they are published.

ERDism is in beta. Features may change, move, or be withdrawn while we learn what works, and we do not promise any level of availability. Because of that, you can always take your schema with you: any project can be exported as SQL.

Keep your own copies

ERDism is not a backup service. Keep your own copies of anything that matters to you: any project can be exported as SQL at any time, and while ERDism is in beta this matters even more.

Connected databases

You can connect a database to a project, so that ERDism reads its structure and tells you when it differs from your design.

You may connect only a database you are allowed to access with the credentials you give us, and by connecting it you confirm that you are.
ERDism uses those credentials only to read the database's schema — the definitions of its tables — and never the rows in it. The Privacy policy explains how the password is kept.
You can disconnect a database at any time.
We tell you about the differences we find. We do not promise to find every difference, or to find it by a particular time.
The availability, load and costs of your database, and of the network that reaches it, are yours.

What you export, and what we suggest

ERDism can export your design as SQL and can suggest changes to it, such as adding a primary key or a join table. Review any SQL, and any suggested change, before you run it against a real database. ERDism does not run anything against your database: you decide what to apply, and the results of applying it — including changed or lost data and interruptions — are your responsibility.

Other services

Some parts of ERDism rely on other companies: signing in with Google or GitHub, the company that handles payments once paid plans start, and the network that carries traffic between you and us (Cloudflare). When you use those parts, those companies' own terms apply as well, and we are not responsible for their outages or for changes they make.

4. Accounts

You can open an account with an email address and a password, or by continuing with Google or GitHub. A password must be at least 8 characters and at most 255. There are no other composition rules.

An account is identified by its email address, and there is one account per address. When you sign up with a password we email you a link to confirm the address. Until you confirm it, you can only confirm it, have the link sent again, correct the address, sign out or close the account — you cannot use the rest of ERDism. An account that is not confirmed within seven days is deleted. If someone signs up with an address whose account has not been confirmed, the new sign-up replaces it: whoever confirms the address first owns it. If you later continue with Google or GitHub using an address that already has an account, that provider is attached to the existing account rather than creating a second one.

You must be at least 16 years old to open an account.

You are responsible for your password and for the Google or GitHub accounts that can sign in as you. Choose a password you do not use anywhere else, and do not let anyone else use your account. If there are too many failed attempts to sign in to an account, or from one network address, in a short time, further attempts are refused for about fifteen minutes. The account is not locked: you can try again once that time has passed.

5. Acceptable use

You may not use ERDism to:

store or share content that is unlawful, or that infringes someone else's rights;
try to get into accounts, workspaces or projects you have not been given access to, or into the systems that run the service;
put an unreasonable load on the service, for example with automated requests;
use another person's account, or let someone else use yours;
resell the service, or access to it, without our written agreement.

If you do, we may remove the content concerned or suspend your account, as described in section 10.

Reporting content

If content shown through ERDism — for example a project opened through a public link — invades your privacy, defames you or otherwise infringes your rights, you can ask us to remove it. Write to [email protected] with the address of the content, what in it infringes your rights, and why.

When we receive a request, we remove the content without delay or, if it is unclear whether it infringes your rights or the person who posted it disputes the request, block access to it for up to 30 days while the matter is settled.
We tell both sides. We tell you what we did, and we tell the workspace that holds the content what was requested and what we did. Its owner can tell us why the content should stay.
After a temporary block, if within the 30 days the matter is not settled in favour of keeping the content, we remove it.

6. Your content

The schemas, diagrams, SQL and documentation that you upload or create remain yours — or, if you work in an organisation's workspace, that organisation's.

You give us permission to store, process and display that content as far as we need to in order to run the service for you and for the people you share it with.

You also allow us to learn from it in one limited way. We may derive knowledge from it that does not identify you, your workspace or your project — totals, and patterns or shapes in which every name has been replaced by a placeholder — and use that knowledge to improve ERDism, including to train machine-learning models. We never train models on your schemas, SQL or documentation themselves. Section 9 of the Privacy policy sets out what we derive and the rules it follows, as well as what we keep, what we delete, and what becomes public only when you choose.

We do not use your content for advertising, and we do not sell it or anything derived from it.

Public links

A public link lets anyone who has it open the project's published version without signing in. Whoever turns a link on is responsible for what it shows and for whom they give it to. We may turn a link off if it is reported to us as described in section 5, or if it puts someone at risk.

Feedback

If you send us ideas, suggestions or other feedback, we may use them freely, without paying you or owing you anything for them.

Our name

The ERDism name and logo belong to us. Do not use them without our permission in a way that suggests we made, endorse or are connected with something. You are always free to say that you use ERDism.

Your responsibilities

You are responsible for your content, for the databases you connect, for the public links you turn on, and for how you use ERDism. If someone else makes a claim against us because of any of these, you will cover the losses and costs it causes us, including reasonable legal fees — unless the claim arises from something we did wrong. If you use ERDism as a consumer, this applies only as far as the law allows.

7. Workspaces and members

A workspace holds projects, and a project holds diagrams, SQL and documentation. A workspace stands for one organisation. Every account gets a personal workspace when it is created, and you can create more.

The owner of a workspace has the highest authority in it and can open every project in it, whatever the project roles say. Members are invited to the workspace and carry a role there; an invitation can be accepted for seven days. The owner can hand the workspace to another member, and the previous owner then stays on as a member.

Content belongs to the workspace, not to the member who typed it. When a member leaves or is removed, they lose access straight away, but what they created stays, and the history keeps showing them as the person who made each change.

When you delete a project or a workspace it goes to the trash. Anything in the trash is permanently deleted seven days after it was put there. For the first three days it can be restored but cannot be permanently deleted by hand, so that a mistake can still be undone.

If you own a workspace that has other members, you cannot close your account until you have handed that workspace to another member or deleted it, so a team never loses its work because its owner left. A workspace you own with no other members is closed together with your account.

8. Fees

ERDism is free during the beta. No payment is taken, and no payment details are asked for or stored.

During the beta there is no limit on how many members of a workspace can have editing rights, apart from a technical ceiling of 30 people with editing rights per workspace. If you need more, contact us.

Paid plans will come after the beta. A plan belongs to a workspace, and the workspace owner is responsible for paying for it. Plans differ in how many people can edit in the workspace and how many databases it can connect. People who only view are free on every plan. The pricing page shows each plan and its price.

When the beta ends, we will tell workspace owners at least 30 days in advance, by email and inside the service. Nobody is removed from a workspace when it ends, and nothing anyone made is lost. In each workspace, everyone who had editing rights before that announcement and edited during the beta keeps them. Other people with editing rights become viewers: they stay members, and their history stays. The workspace's free plan then allows as many people with editing rights as kept them this way, or three if that is more.

After the beta, when a workspace already has as many people with editing rights as its plan allows, giving them to one more person needs a paid plan. On the free plan that number is three, or the number the workspace kept when the beta ended. People who already have editing rights keep them; when one of them leaves, their place is not filled again without a paid plan.

We will tell workspace owners at least 30 days before any of this changes, by email and inside the service. Payments may be handled by a reseller (a merchant of record). When that happens the reseller is the seller, and its purchase terms apply alongside these. Refunds are covered by our Refund policy.

Trying a connected database on the free plan

Once paid plans start, a workspace on the free plan can connect one database for 14 days, without a card. When the 14 days end, ERDism stops reading that database and the workspace stays on the free plan: it does not move to a paid plan on its own, and nothing is charged. The connection, what it found and its history stay, and choosing a paid plan starts the reading again. A workspace can have this trial once, and an account can start it once.

Changing plans

Moving to a larger plan takes effect at once. You pay the difference for the rest of the current billing period straight away, and you see the amount before you confirm.
Moving to a smaller plan takes effect on your next renewal date. Until then you keep your current plan, and nothing is refunded for the period you have already paid for.
Moving from monthly to yearly billing takes effect at once. What is left of the month you paid for is taken off the yearly price.
Moving from yearly to monthly billing takes effect when the yearly period ends, with no refund.

Extra databases

On a paid plan you can connect more databases than the plan includes, for an extra charge for each one. An extra database you add works at once, and you pay for it for the rest of the current billing period straight away. One you remove leaves your bill on your next renewal date, with no refund.

Renewal

A paid plan renews automatically at the end of each billing period, monthly or yearly, until you cancel it. When you choose a paid plan, we ask you to agree separately to the renewal terms — the amount, how often you are charged and how to cancel — and we email you a copy of them.

Yearly plans: we remind you 30 days before each renewal, by email and inside the service, with the amount and how to cancel. Monthly plans: you receive a receipt for each charge.
Price changes: if the price of your plan goes up, we tell you 30 days before the new price applies and ask for your agreement. We never charge the new price without it; if you do not agree, your plan does not renew at the new price.

If a payment fails

If a payment fails, we tell you at once, by email and inside the service, and try the payment again over the next 14 days. During those 14 days everything keeps working as before. If the payment still has not gone through after 14 days, the workspace moves to the free plan:

nobody is removed from it, and nothing anyone made is lost;
every project can still be opened and exported as SQL;
people who have editing rights keep them, and giving them to anyone else follows the free plan's limit, as described above;
ERDism stops reading its connected databases, and their connections and history stay.

As soon as you fix the payment method and the payment goes through, the paid plan comes back.

Cancelling

You can cancel a paid plan at any time from the workspace's settings, without having to contact us. The plan stays active until the end of the period you have paid for, and the workspace then moves to the free plan. Our Refund policy explains when a payment is refunded.

9. Availability and changes to the service

We work to keep ERDism running, but during the beta we make no promise about uptime and the service may be interrupted for maintenance or by faults. We may add, change or remove features.

10. Suspension and ending the agreement

We may suspend or close an account, or remove content, if it breaks these terms, if the law requires us to, or if it puts the security of the service or of other users at risk. We will tell you first and give you a chance to respond, unless the situation is urgent or the law does not allow us to.

You can close your account from your account page at any time. You confirm it with your password, or — if your account signs in only with Google or GitHub — by signing in with that provider again. Closing an account hides the account, your profile, your memberships, the invitations you sent or received, and the workspaces and projects you own — which, as section 7 says, can only be workspaces with no other members. You are signed out everywhere.

For thirty days after you close it, you can reopen the account — with your email address and password, or by continuing with the same Google or GitHub account — and everything that was closed with it comes back. During those thirty days its email address cannot be used to open a new account. After thirty days the account is erased as section 8 of the Privacy policy describes, and can no longer be reopened. If you want it erased sooner, ask us as described in section 10 of the Privacy policy.

11. Warranties and liability

ERDism is provided "as is" and "as available". As far as the law allows, we make no promises about the service beyond those written in these terms.

As far as the law allows, we are not liable for indirect or consequential losses, such as lost profits, lost revenue or lost business opportunities. Our total liability to you for any claim is limited to the amount you paid us for the service in the 12 months before the claim arose. If you paid nothing, it is limited to USD 100.

Nothing in these terms limits a liability, or takes away a right, that consumer protection law does not allow to be limited or taken away.

12. Governing law and disputes

These terms are governed by the laws of the Republic of Korea. Any dispute about them is heard by the Seoul Central District Court.

If you use ERDism as a consumer, you keep the protection of the mandatory laws of the country where you live.

13. General

The whole agreement. These terms, the Privacy policy and the Refund policy are the whole agreement between you and us about ERDism.
If one part does not hold. If part of these terms is found invalid, the rest still applies.
Waiting is not giving up. If we do not enforce a right straight away, we have not given it up.
Passing the agreement on. We may transfer this agreement to whoever takes over ERDism — for example if the business is sold, or moved into a company set up to run it. We will tell you when that happens. You may not transfer your account or this agreement without our agreement.
Things outside our control. We are not responsible for failing to do something these terms promise when the cause is outside our reasonable control, such as a natural disaster, a failure of the internet or of power, or a failure of a company we rely on.
Notices. We send notices about these terms and your account to your account's email address, so keep it up to date.
Languages. These terms are written in English. The Korean version has the same effect as the English one, and if they differ, the one more favourable to you applies. The Japanese version is a reference translation, and if it differs from the English version, the English version prevails.

14. Changes to these terms

When we make an important change to these terms, we will tell you at least 30 days before it takes effect, by email and inside the service. If you keep using ERDism after a change takes effect, you accept the new terms. If you do not accept them, you can close your account before then.

The date at the top of this page shows when these terms were last changed.

15. Contact

Questions about these terms: [email protected].