BlueBlips Privacy Policy

BlueBlips instantly connects people everywhere to what’s most meaningful to them. Any registered user can send a Blip, which is a message of 140 characters or less that is public by default and can include other content like photos, videos, and links to other websites.

Tip What you say on BlueBlips may be viewed all around the world instantly.

This Privacy Policy describes how and when BlueBlips collects, uses and shares your information when you use our Services. BlueBlips receives your information through our various websites, APIs, email notifications, applications, buttons (the "Services" or "BlueBlips"). For example, you send us information when you use BlueBlips from our website, post or receive blueblips from an application such as blueblips for Mac, blueblips for Android or TweetDeck. When using any of our Services you consent to the collection, transfer, manipulation, storage, disclosure and other uses of your information as described in this Privacy Policy. Irrespective of which country you reside in or supply information from, you authorize BlueBlips to use your information in the United States and any other country where BlueBlips operates.

Information Collection and Use

Tip We collect and use your information below to provide our Services and to measure and improve them over time.

Information Collected Upon Registration: When you create or reconfigure a blueblips account, you provide some personal information, such as your name, username, password, and email address. Some of this information, for example, your name and username, is listed publicly on our Services, including on your profile page and in search results. Some Services, such as search, public user profiles and viewing lists, do not require registration.

blips, Following, Lists and other Public Information: Our Services are primarily designed to help you share information with the world. Most of the information you provide us is information you are asking us to make public. This includes not only the messages you Blipped and the metadata provided with blips, such as when you Blipped, but also the lists you create, the people you follow, the blips you mark as favorites or Reblipped, and many other bits of information that result from your use of the Services. Our default is almost always to make the information you provide public for as long as you do not delete it from blueblips, but we generally give you to make the information more private if you want. Your public information is broadly and instantly disseminated. For instance, your public user profile information and public blips may be searchable by search engines and are immediately delivered >APIs to a wide range of users and services, with one example being the United States Library of Congress, which archives blips for historical purposes. When you share information or content like photos, videos, and links via the Services, you should think carefully about what you are making public.

Cookies: Like many websites, we use "cookie" technology to collect additional website usage data and to improve our Services, but we do not require cookies for many parts of our Services such as searching and looking at public user profiles or lists. A cookie is a small data file that is transferred to your computer's hard disk. blueblips may use both session cookies and persistent cookies to better understand how you interact with our Services, to monitor aggregate usage by our users and web traffic routing on our Services, and to customize and improve our Services. Most Internet browsers automatically accept cookies. You can instruct your browser, by changing its settings, to stop accepting cookies or to prompt you before accepting a cookie from the websites you visit. However, some Services may not function properly if you disable cookies.

Log Data: Our servers automatically record information ("Log Data") created by your use of the Services. Log Data may include information such as your IP address, browser type, operating system, the referring web page, pages visited, location, your mobile carrier, device and application IDs, search terms, and cookie information. We receive Log Data when you interact with our Services, for example, when you visit our websites, sign into our Services, interact with our email notifications, use your blueblips account to authenticate to a third-party website or application, or visit a third-party website that includes a blueblips button or widget. blueblips uses Log Data to provide our Services and to measure, customize, and improve them. If not already done earlier, for example, as provided below for Widget Data, we will either delete Log Data or remove any common account identifiers, such as your username, full IP address, or email address, after 18 months.

Our Policy Towards Children

Our Services are not directed to persons under 13. If you become aware that your child has provided us with personal information without your consent, please contact us at [email protected]. We do not knowingly collect personal information from children under 13. If we become aware that a child under 13 has provided us with personal information, we take steps to remove such information and terminate the child's account.

EU Safe Harbor Framework

blueblips complies with the U.S.-E.U. and U.S.-Swiss Safe Harbor Privacy Principles of notice, choice, onward transfer, security, data integrity, access, and enforcement. To learn more about the Safe Harbor program, and to view our certification, please visit the U.S. Department of Commerce website.

Changes to this Policy

We may revise this Privacy Policy from time to time. The most current version of the policy will govern our use of your information and will always be at https://twitter.com/privacy. If we make a change to this policy that, in our sole discretion, is material, we will notify you via an @blueblips update or email to the email address associated with your account. By continuing to access or use the Services after those changes become effective, you agree to be bound by the revised Privacy Policy.

Effective: July 3, 2013