1. Privacy Policy and Terms of Use

    Updated: Friday, May 21, 2021

    AS A GENERAL RULE, technology companies — and especially social media companies — don’t want you to read contracts like the one you’re reading right now. They don’t want you to fully understand how they work and what they do with your personal information because they know that it’s unsettling and unethical. So they hide the truth in contracts that are so long, boring and confusing they’re virtually impossible to read.

    As a result, we keep clicking “I agree” to legally binding documents without much of a clue what we’re even agreeing to. It’s a huge problem.

    Readup has nothing to hide. We’re proud of what we’ve built. And we actually want you to read this whole thing closely, so we’re keeping it short, sweet, clear, and hopefully even interesting. In a word: readable.

    For starters, keep in mind that the word “Readup” can refer to any of the following:

    • The technology platform (readup.com, Readup apps and extensions, etc.)
    • The community of readers (real human beings) who use the platform
    • The corporation, reallyread.it, inc., which owns and operates the platform
    • The two-person team, Bill Loundy and Jeff Camera, who co-own and co-operate the corporation and platform.

    Currently, Bill and Jeff each own 50% of reallyread.it, inc. As new employees and investors acquire ownership stakes in Readup, we promise to always disclose this information to our community of readers.

    When you read on Readup, you create data. Sometimes you finish reading articles and sometimes you don’t. Readup keeps track. It needs to, in order to function. For example:

    • On Readup, if you want to comment on an article you need to read the whole thing.
    • Anonymized, aggregate reading data powers the algorithm that curates content and selects the Article of the Day (AOTD). Readup is able to identify the best reading material because Readup “knows” the articles and stories that real humans are really reading to completion. As far as we know, Readup is the only social media platform with a 100% transparent algorithm.

    Your reading data is strictly private by default. The only way that other readers can see what you have read is if you explicitly choose to post or comment on an article after you have read it. There is no “bulk post” or “default public” option; the choice is yours to make on an article by article basis.

    If you want, you can use Readup anonymously or pseudonymously, but once you choose a reader name you can’t change it.

    You own your data. We store and use your data, but you own it. That means:

    1. You own the rights to the comments you make on Readup.
    2. At any time, you can request a complete copy of your personal data and we will send it to you. We do this manually, so it might take a few days.
    3. You can delete your account whenever you want.
    4. We never share your reading data with any third parties under any circumstances. We don’t even use common services like Google Analytics or Hotjar which monitor everything you do in the background. The only third party script that runs on Readup is Stripe.js (for fraud detection) during checkout, which Stripe requires us to do.

    We work very hard to avoid collecting data that we do not need. As a result, we’re proud to be able to provide you with the following comprehensive overview of ALL data that we collect when you use Readup.

    Before you create an account on Readup

    • If you read an article on the Readup Blog, we generate a random, temporary user ID and store your reading progress in case you want to leave a comment after you finish.
    • If you want to get notified when we launch the Android app, we need your email address.

    When you create an account on Readup

    • We require you to provide an email address. (If you confirm your email, we store that too.)
    • We require you to choose a reader name and password. Only the salted password hash is stored in our database.
    • We automatically detect your time zone and preferred color scheme (light mode or dark mode) from your device.
    • We also collect the following analytics to help us understand how new people find us. We need this information to improve the onboarding experience for new readers:
      • The referrer URL tells us which website (if any) sent you to Readup.
      • The initial path tells us where on Readup you first landed.
      • The current path tells us which page on Readup you created an account on.
      • The action button tells us which button you pressed to create an account (such as “Header Button” or “Footer Button.”)
      • When you complete the onboarding process, we mark onboarding complete.

    If you use a third party authenticator

    • You can create an account (or connect your existing account) using Apple or Twitter. These companies give us the following data:
      • Your email address (This is optional if you use your Apple ID.)
      • Your identifier which is a random value used to identify your account
      • Twitter also gives us your display name, handle, verification status and an access token to tweet on your behalf (with your explicit permission, of course.)
      • Apple gives us your real user rating.

    When you install a Readup browser extension

    • We generate a random installation ID to determine when an extension is installed, updated or removed.
    • We detect your operating system and processor type. (It’s necessary for us to know if readers are using Linux, Windows or Mac.)

    When you install the Readup iOS or macOS app

    • You can allow or deny notifications. We store an installation ID and device name. If you allow notifications, we also store a token.
    • If an unexpected error occurs, an error report is automatically sent to Readup.

    When you get an email from Readup

    • We detect email opens using a tracking pixel image and link clicks with tracking URLs. (This helps us improve the quality of our emails.)

    When you subscribe

    • You can subscribe to Readup using Apple (iOS only) or Stripe (browser only). These companies give us the following data:
      • An identifier, your subscription price, start and end dates, payment status, refund status, auto-renew preference, and any pending upgrades or downgrades.
    • Stripe also provides us with a random ID to reference your payment method, your wallet (if you pay using a wallet service), your credit card brand, and the last four digits and expiration date of your credit card.
    • Your credit card number is never transmitted to (or stored on) any Readup servers.

    When you read on Readup

    • We store your complete reading history in our database. This is absolutely essential in order for Readup to work.
    • We also store your stars, ratings, posts and comments. (Comments can be easily deleted at any time.)
    • We store any article issues that you report.
    • We keep a record of how your subscription payments get distributed to (1) Apple and/or Stripe (2) Readup and (3) the writers you read.

    When you update your preferences

    • We store your notification preferences and we make it very easy to unsubscribe from everything.
    • We store your reading preferences (text size, links on/off.)

    COOKIES: Sometimes we use cookies, but never for marketing purposes. And since we only use “strictly necessary cookies,” we’re not required to make you click “I agree” when we use them.

    CANARY: Readup has never received a government request for information.

    FEEDBACK: This contract will continue to evolve. Please share your suggestions on GitHub.

    CONTACT: Email us. You will always get a reply from a human: support@readup.com