๐ŸŒŒ
Privacy Village Academy
Join The Community!AcademyAbout HGPE
  • Hitchhiker's Guide to Privacy Engineering
    • โ“What is HGPE?
      • โš–๏ธWho is this for?
      • ๐Ÿง™โ€โ™‚๏ธPrivacy Engineering
      • ๐ŸŽจCreative Privacy
      • ๐Ÿ”ฎGenerative AI
      • ๐Ÿง‘โ€๐Ÿ’ปAbout the Author
  • ๐Ÿง™โ€โ™‚๏ธThe Ethical AI Governance Playbook 2025 Edition
    • ๐Ÿค–Chapter 1 : AI Literacy
    • ๐ŸŒChapter 2 : AI Governance in the 21st Century
    • โŒ›Chapter 3 - Getting Started with AI Act Compliance
    • ๐Ÿš€Chapter 4 : Rise of AI Governance: Building Ethical & Compliant AI
    • Chapter 5 : Introduction to the Lifecycle of AI
  • ๐ŸŽ“Privacy Engineering Field Guide Season 1
    • โ“Decoding the Digital World: Exploring Everyday Technology
    • ๐Ÿ‘๏ธIntroduction: Why Privacy Matters?
      • Age of Mass Surveillance
      • Privacy & Democracy
      • Privacy & Government Surveillance
    • โšกChapter 1 : How Computers Work?
      • Electricity
      • Bits
      • Logic Gates
      • Central Processing Unit (CPU)
      • Graphic Processing Unit (GPU)
      • Motherboard
      • Data Storage
      • Databases
      • Operating System (OS)
      • Computer Code
      • Programming Languages
      • The File System
      • Bugs and Errors
      • Computer Virus
      • Internet of Things (IoT)
      • Cloud Computing
    • ๐Ÿ›ฐ๏ธChapter 2 : How the internet works?
      • Physical Infrastructure
      • Network and Protocols
      • Switch
      • Routers
      • IP Address
      • Domain Name System (DNS)
      • Mac Address
      • TCP / IP
      • OSI Model
      • Packets
      • The Client - Server Architecture
      • Secure Socket Shell (SSH)
      • Transport Layer Security (TLS)
      • Firewall
      • Tunnels and VPNs
      • Proxy Server
    • ๐Ÿ–ฅ๏ธChapter 3 : How Websites Work?
      • HTML
      • CSS
      • Javascript
      • Web Server
      • Browser
      • HTTP
      • Databases
      • Front End (Client Side)
      • Back End (Server Side)
      • Cookies
      • Local Storage
      • Session Storage
      • IndexedDB
      • XHR Requests
      • Web APIs
      • Webhooks
      • Email Server
      • HTTPS
      • Web Application Firewall
      • Single Sign-on (SS0)
      • OAuth 2.0
      • Pixels
      • Canvas Fingerprinting
      • Email Tracking
      • Containers
      • CI/CD
      • Kubernetes
      • Serverless Architecture
    • โš›๏ธChapter 4 : How Quantum Computers Work?
      • Quantum Properties
      • Quantum Bits (Qubits)
      • Decoherence
      • Quantum Circuits
      • Quantum Algorithms
      • Quantum Sensing
      • Post-Quantum Cryptography
    • ๐Ÿ“ณChapter 5 : Mobile Apps and Privacy
      • Battery
      • Processor
      • Mobile Operating Systems
      • Mobile Data Storage
      • Cellular Data
      • Mobile Device Sensors
      • Wireless Connectivity
      • Camera & Microphone
      • Mobile Apps
      • Software Development Kits (SDKs)
      • Mobile Device Identifiers
      • Bring Your Own Device (BYOD)
  • ๐Ÿ•ต๏ธโ€โ™‚๏ธPrivacy Engineering Field Guide Season 2
    • โ“Introduction to Privacy Engineering for Non-Techs
      • ๐ŸŽญChapter 1 : Digital Identities
        • What is identity?
        • Authentication Flows
        • Authentication vs. Authorization
        • OAuth 2.0
        • OpenID Connect (OIDC)
        • Self Sovereign Identities
        • Decentralized Identifiers
        • eIDAS
      • ๐Ÿ‘๏ธโ€๐Ÿ—จ๏ธChapter 2 : De-Identification
        • Introduction to De-Identification?
        • Input / Output Privacy
        • De-identification Strategies
        • K-Anonymity
        • Differential Privacy
        • Privacy Threat Modeling
  • ๐Ÿ“–HGPE Story and Lore
    • ๐ŸชฆChapter 1 : The Prologue
    • โ˜„๏ธChapter 2 : Battle for Earth
    • ๐Ÿฆ Chapter 3 : A Nightmare To Remember
    • ๐Ÿง™โ€โ™‚๏ธChapter 4 : The Academy
    • ๐ŸŒƒChapter 5: The Approaching Darkness
    • โš”๏ธChapter 6 : The Invasion
    • ๐ŸฐChapter 7 : The Fall of the Academy
    • ๐Ÿ›ฉ๏ธChapter 8 : The Escape
    • ๐ŸชChapter 9 : The Moon Cave
    • ๐Ÿฆ‡Chapter 10: Queen of Darkness
  • ๐Ÿ“บVideos, Audio Book and Soundtracks
    • ๐ŸŽงReading Episodes
    • ๐ŸŽนSoundtracks
  • ๐Ÿ‘พHGPE Privacy Games and Challenges
    • ๐ŸŽฎData Privacy Day'23 / Privacy Treasure Hunt Game
    • ๐ŸงฉPrivacy Quest
  • ๐Ÿ“ฌSubscribe Now!
Powered by GitBook
On this page

Was this helpful?

  1. Privacy Engineering Field Guide Season 1
  2. Chapter 3 : How Websites Work?

Front End (Client Side)

The front end of a web application is the layer where users interact with the website.

PreviousDatabasesNextBack End (Server Side)

Last updated 2 years ago

Was this helpful?

The front end of a web application is the layer where users interact with the website. With HTML, a structure is created for how the content on the web page should be seen by the browsers.

Don't think of a mere interface that has to do with the design and layout of websites when you think about the front end. As in this layer, intense personal data processing activities are carried out. In comparison to the backend, the front end stores less sensitive data in your web applications.

Yet, the front end is the main gate to your web applications.

A modern website consists of many different layers, and some of the tools and technologies used include data sharing with third parties.

Implementing third-party libraries on your web application increases your privacy and security risks due to the constant data exchange.

Let's look at an example.

Let's create a registration form for our galactic website, we want our users to register with our website through this form.

Email address and password are all we need right now.

That's why we build a form where we request the email address and the password required for registration.

You can find the sample code snippet below to create a web form with HTML that allows users to enter their email addresses and password.

<form action="action_page.php"
  <div class="container">
    <h1>Register</h1>
    <p>Please fill in this form to create an account.</p>
    <hr>
    <label for="email"><b>Email</b></label>
    <input type="text" placeholder="Enter Email" name="email" id="email" required>
    <label for="psw"><b>Password</b></label>
    <input type="password" placeholder="Enter Password" name="psw" id="psw" required>
    <label for="psw-repeat"><b>Repeat Password</b></label>
    <input type="password" placeholder="Repeat Password" name="psw-repeat" id="psw-repeat" required>
    <hr>
    <p>By creating an account you agree to our <a href="#">Terms & Privacy</a>.</p>
    <button type="submit" class="registerbtn">Register</button>
  </div>
  <div class="container signin">
    <p>Already have an account? <a href="#">Sign in</a>.</p>
  </div>
</form>
>

We should not forget that we have to provide a privacy notice before asking the users for their input.

In addition, it's a best practice to collect as little information as possible at this stage due to both user experience and complying with the data minimization principle.

๐ŸŽ“
๐Ÿ–ฅ๏ธ
Page cover image