Writing an EULA

Hello friends!
I'm writing an EULA to distribute my typefaces through MyFonts.
I have a lot of doubts and I hope you can help me with some of these points:
Which points should I consider to start writing an EULA?
I know an EULA is the way the foundry conceive the permission to use its fonts and I just want to protect my work as much as possible from piracy.
Can I submit an EULA, for example, to distribute my typefaces via MyFonts and update it after a while?
What's the difference between selling fonts to 1-5 cpus or individually? I just want to know some advantages and disadvantages of these options.
Does it make any sense to prohibit copying font files to a store device or sending them by email?
Is it convenient to allow font embeding for websites?
How can I protect my typefaces from piracy if I allow font embeding for websites?
Thanks in advance and sorry for my english.


"I just want to protect my work as much as possible from piracy"

A EULA has pretty much nothing to do with preventing 'piracy'. Those folks really don't care what's in the EULA.

The EULA is an agreement between you and your paying customers.

The EULA is a license agreement, you make the rules for this license. You can make it as complex or simple as you like, as long as it's fair for both parties.
Selling fonts for 1-5 cpus, is that you can install it on 5 cpus, so 5 people can use the font at ones. Individually; only one person can use it on one cpu. Fonts for 1 cpu (1 person) are mostly cheaper than for 1-5 cpus.

Does it make any sense to prohibit copying font files to a store device or sending them by email?

Transactions will go slower if you only prohibit sending the fonts by email.

Preventing piracy is very difficult, you can better make a good EULA, after that you can always take legal steps if you find someone is abusing your work.


I agree with both.

- Most people who license your fonts, even single work-at-home freelancers have more than one computer. It really is more user-friendly to at least allow for 5 computers.
- Web embedding is the new frontier. I think foundries should allow for embedding in Flash (SIFR) but understand if they don't want to allow for @Font-Face because it is not protected.
- Consider allowing for PDF Print & Preview embedding as well as, and at least, distribution to clients and press houses.

Here is another useful thread about EULAs here on Typophile.

Just to throw out some things to think about if you're going the EULA route...

As a designer, I'd love it if you licensed the font per users, rather than per CPU. I'm one user, but I own 2 computers and use them both. I'd love a license that allowed me to use the purchased font on computers I own.

So, one way to think about it might be a user license vs. small studio license vs. corporate license.

Yes, you know I meant to say as Darrel said, by user not computer.

I think SIFR embeding is not a threat for typeface designers and I´m agree with this permission but to store a font in a server is very risky, I found an interesting article about web fonts at http://talleming.com/2009/04/21/web-fonts/ Thanks for your help.