|
Log in Sign up

privacy policy

Last updated: 3 février 2026
Privacy · Cookies · Terms
This page aims to clearly explain the technologies used by Piastro and provide transparency about audience measurement (without advertising trackers).

Objective

Piastro seeks to be transparent about its tech stack and how usage statistics (if enabled) are collected.

Main stack components (by category)

Backend (application)

  • Python 3.12 — runtime principal
  • Django 5.x — framework web
  • Gunicorn — serveur applicatif WSGI
  • python-decouple — gestion de configuration via variables d’environnement
  • psycopg2-binary — driver PostgreSQL
  • python-dateutil — outils de manipulation de dates
  • Python-Markdown + Bleach — rendu et nettoyage de contenu riche

Database

  • PostgreSQL 16 — primary production database
  • SQLite — can be used locally (depending on the dev environment)

Static/media files

  • WhiteNoise — serve static files in Django
  • Nginx — reverse proxy and static/media delivery in production

Deployment & infrastructure

  • Docker — conteneurisation
  • Docker Compose — orchestration
  • Nginx — TLS + reverse proxy
  • Certbot / Let’s Encrypt — TLS certificates
  • Ansible — deployment automation, including analytics

Analytics (without advertising trackers)

  • Plausible Analytics (Community Edition), self-hosted (domain analytics.piastro.ca)
  • Plausible dependencies: PostgreSQL + ClickHouse

Front-end (libraries)

Some pages load UI/chart libraries from CDNs:

  • Chart.js
  • Apache ECharts
  • Lucide — icônes
  • Google Fonts — fonts

Trackers: what Piastro does not use

  • No advertising trackers (e.g., Google Analytics/Tag Manager, Meta Pixel, etc.).
  • Usage statistics, when present, go through self-hosted Plausible (privacy-oriented solution).
Note: using CDNs (fonts, JS libraries) implies network requests to these providers. If you want a 100% "no external calls" version, contact us: these resources can be self-hosted.

Official links