Developer Guide: Business
How things work on Flickr
Flickr has a very passionate and enthusiastic community, and we encourage relevant companies to jump into the conversation. There are several ways to do so:
Do's and Don'ts
- Do identify content that comes from Flickr: Please attribute Flickr as well as the Flickr member whose work you're presenting.
- Do acknowledge that the Flickr member who creates the content owns their content, such as photos, comments, buddy icons, etc.
- Do encourage participation with Flickr and not just consumption.
- Don't use Flickr for a backend storage: Because Flickr is so easy to use, it's tempting to use the site as a content hosting service. However, that's not why we're here, and it diminishes the quality of the community. We're pretty sure you must have realized by now that Flickr is infinitely more than just an image hosting site -- Flickr also has a very robust and quick backend particularly aimed at photographers interacting real-time in many different ways. So please don't use Flickr to host content you don't intend to share.
- Don't use the Flickr trademarks, unless you have explicit written permission. This includes calling an app built for a specific platform "Flickr". Please note that using the Flickr API does not include Flickr trademarks, such as the Flickr logo, dots, or the string "Flickr". At this time, if you want to use these trademarks, you can apply via our trademark permission process.
- Don't replicate the Flickr design and service in a way that could be misleading or confusing.
- Don't ever spam members via FlickrMail. This will garner community complaints, and we will shut down abusive accounts. FlickrMail is available for photographer-to-photographer communication, and should be used as such. Spammy FlickrMails include announcements, solicitations, and comments to a high number of Flickr members a day.