Privacy Policy

Classic Programmers > Privacy Policy

Who we are

Welcome to Classic Programmers. Our goal is to develop software that improves the way other businesses work. That means keeping your information secure and our code clean is extremely important to us. This Privacy Policy is here to break down what info we gather, why we need it, and how you can stay in charge when you’re using our website, client areas, or anything else we offer.

1. Why This Policy?

Software, just like humans, needs instructions to be able to work, no? Well, posting a privacy policy proves that a company takes your privacy seriously. This document discusses the following key subject:

  • Sharing what kinds of personal info we gather.
  • Explaining the reasons for and methods of using that information.
  • Letting you know your privacy rights and how the law defends them.

    Regardless of where we are, we follow the rules of the EU General Data Protection Regulation (GDPR), UK GDPR, the California Consumer Privacy Act (CCPA) and other major regulations.

2. The Data We Collect & Generate

Let’s focus on what kinds of data it is that we collect:

  • Identity Data: Information about you such as your name, your company and your role, is called Identity Data. This information is often in client contact forms or proposals.
  • Contact Data: Contact Data is simply your email address, phone number and mailing address. Give it to us and we will take care of it for you.
  • Project Data: Details about the projects we are collaborating on such as design files, source code and other assets. Usually directly provided by you or your team.
  • Usage Data: This is more behind-the-scenes stuff. Things like your IP address, what kind of browser you’re using, the type of device, which pages sent you our way, and how long you hang out on our pages. We get this automatically through tracking tech.
  • Cookie & Tracking Data: Cookies and other goodies that work to record your activity on the site, collect analytics and save preference information. The operating system takes care of this on its own.
  • Marketing Data: If you sign up for our newsletter or register for an event, we’ll grab that kind of info.

    We don’t store private information (like health care or political opinions) anywhere. Anytime we need sensitive information for a project, you’ll be notified, and you’ll have to give your consent very clearly.

3. How We Use Your Data

So, you might be curious how we actually use your private details? Let’s crack open that mystery box:

  • Project Estimates: Asking for a project quote or statement of work results in our team using your information to create them. It all relies on a contract and your request to process.
  • Software Updates and improvements: We use data on continuous integration to improve our software, find and fix bugs and make it run more smoothly. This is part of our contract with you, sometimes we’d like to make our work better for you anyway. 
  • Support Inquiries: If you provide your information to our support team email (support@classicprogrammers.com) about any question or problem, we will use it to help you. We feel that helping our customers is something that helps both ourselves and our customers. 
  • Website Analytics and Improvements: With Google Analytics and server logs, we analyze how our internet users access our website. It enables us to see the issues and improve the site. We do this with your consent or from something that benefits both parties.
  • Marketing Stuff: We will email you with newsletters and updates, as long as you express your permission. You give us this permission by accepting our privacy statement.
  • Security and Legal Stuff: We use data to stop any fraud, check our operations during audits and meet all the laws required. This comes from a legal requirement.

4. Cookies & Similar Tech

The Tiny Ninjas of the Internet are Cookies. Like a lot of websites, we make use of cookies. They’re small text files that help us remember things about you so we can create a better experience. Here’s what we use them for:

  • Strictly Necessary Cookies: Everything on the site needs these cookies to operate correctly. They allow the browser to stay logged in and use basic features.
  • Performance Cookies: Mechanisms that help identify the parts of your site that need improvement (or are not working properly). With these we can observe site usage, the sources of traffic and if there are delays. This way we can fix any issues.
  • Functionality Cookies: These cookies ensure your language stays the same as well as allowing you to use dark mode.
  • Marketing Cookies: They will be used just when they are allowed by you. They assist in giving you ads and email messages that may suit your interests.

You can edit how cookies work on your browser settings or by using the cookie banner on our site. However, some parts of the webpage might behave strangely if you block a required cookie.

5. Data sharing & Disclosure

We only pass along your information when it’s really important, either to improve our service for you or according to the law. Here’s a breakdown:

  • Cloud Hosting: To keep our site, apps and development going well, we rely on AWS, Azure and Vercel. They work behind the scenes to get everything working right.
  • Analytics and Marketing: Department of Analytics and Marketing relies on Google Analytics and HubSpot to check user behavior and send info that is useful for people considering our brand.
  • Payment superheroes: When you send us money, we use payment processors to handle invoices and credit card stuff.
  • Subcontractors and Partners: There are situations where we involve subcontractors and partners, as some tech tasks are too specific for anyone to know. When required, we might need to pass some information on to people involved in the project under strict security terms.
  • Legal Reasons: It’s our duty to obey the law. If the police, government or a court makes a request, we may need to send them the data.

Speaking of safety, no one can get their claws on your data until we conduct a background check, make them sign important documents and use proper legal wrapping if it’s moving to another country (Standard Contractual Clauses and such).

6. International Data Transfers

Our office is in Oslo, Norway, though our servers could be based in different states. We ensure that European or UK data is protected by the following means when it is being transferred:

  • EU-US Data Privacy Framework: Which includes the laws that govern how data is protected in both the EU and US as well as other countries.
  • Standard Contractual Clauses: The purpose of this is to ensure your data is well looked after.

Extra security measures: Data safety is covered by encryption magic for any online activity as well as keeping your data at rest.

7. Data Security

Security is important to us as a company:

  • We rely on SSL/TLS to encrypt the entire platform.
  • Access to your personal information can be granted only to verified and approved people.
  • All data backups are encrypted.
  • We test our systems by finding points where they might fail. Frequently performed penetration testing.
  • We make sure to check our vendors more than once.

If, by some weird chance, there’s a security problem, we’ll let you and the authorities know as fast as the law requires.

8. Data Retention

We let you know how long your information is stored with us:

  • Contract and billing info: We hold onto contract and billing information for a period of 7 years. These are requirements stated in tax and accounting rules, so we’re all covered by the taxman.
  • Marketing subscriptions: Our messages will keep coming until you unsubscribe or are gone for 2 years.
  • Website analytics: We have Google Analytics turned on and by default, Google keeps the data for 26 months.
  • Project files: Code, designs and other project materials are all files you might need during the development process. The storage time for these records is set by the Master Services Agreement (MSA). When there is no MSA detail, we continue to save files for 12 months and once the project finishes, we go with the longer option.

As soon as we finish with your data, we either erase it or scramble it to ensure your privacy (the process is called anonymizing).

9. Your Rights

Depending on where your home is, there are probably ways for you to manage your own data. Due to these rights, you are able to:

  • Access: If you want, you can find out what data we maintain about you.
  • Fix Mistakes: Noticed something you think is missing or wrong? We can change it if you ask us to.
  • Erase: You are welcome to ask us to delete your personal data. People also refer to it as the right to be forgotten.
  • Take a break: If we can’t find a solution right away. You can request that we halt using your data until we confirm everything is correct. 
  • Move your data: You can request to get a copy of your data in a computer-friendly way so you can move it from the company if you want. 
  • Opt out of marketing: You can decide anytime to stop receiving marketing content. All of our emails contain an unsubscribe link.
  • Withdraw Consent: If we’re using your data based on your permission, you can take back that permission whenever you want.


Just writing an email to (privacy@classicprogrammers.com) will allow you to use any of these options. You can expect a response within 30 days (unless local laws require us to answer you sooner).

10. Children’s Privacy

The services and the website are for adults. Under 13 years of age (or under 16 years if belonging to the European Union). We will not intentionally collect data from children, and we want to avoid it completely. Should you suspect that your child gave us their data, email us and we will delete it right away.

11. Privacy Updates

From time to time, we might need to update this privacy policy because of changes in tech, laws, or how we do business. Part way through this process, we’ll show the updated policy here and change the Last updated date at the top. For major updates, we’ll give you a heads-up using a notice in the app or by email (when we’re able to).