> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ardoiseeduc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Frequently asked questions

> Countries, languages, access, fees, account deletion and offline operation.

## Who can use each offering?

Marketplace and Business serve families, tutors and institutes in configured countries. Ardoise School is limited to the OHADA scope and is not an Austrian school offering. Learning requires the corresponding resources, permissions and activation; learner Academy is not a complete available journey. See [the four layers](/en).

## Which language is displayed?

French is primary in OHADA, with English possibly available; German is not an OHADA product language. German is primary in Austria, with English/French according to the journey. An explicit preference among allowed languages can override the country's default. German School documentation does not offer School in Austria.

## Can I delete my account?

Yes, for every role: **My account → Delete my account**, confirmation `DELETE` and password or Google identity verification. [See the steps](/en/guide-utilisateur/premiers-pas#delete-my-account). Access is removed, the profile removed/deactivated and the session closed. Necessary school or financial history can remain; this is not a total-erasure guarantee.

## Who can see data?

Permissions depend on role, organisation, family relationships and server authorisation. Institutes gain neither Django records nor private parent/tutor messages. A school controls its installation; explicitly configured integrations can transfer necessary data. See [architecture](/en/guide-technique/architecture) and [security](/en/guide-technique/securite).

## Is Ardoise free?

A free core exists; Enterprise modules, promotion and Marketplace fees follow the displayed policy. A self-acquired institute family can receive a commission exemption under verified attribution rules. No uniform or permanent price is promised here: [plans and fees](/en/plateforme/abonnement).

## What works offline?

An OHADA school can use authorised local operations while its server remains reachable. Licences, payments and remote services need synchronisation/connectivity. Installing the PWA does not make all data available offline: [getting started](/en/guide-utilisateur/premiers-pas).

**The roll call is the one deliberate exception.** A teacher or a surveillant who has already opened the day's register can keep marking it with no connection: the register is kept on the device, the screen says plainly that it is not on the server yet, and it is sent automatically as soon as the connection returns. The school stays the authority - nothing counts as recorded until the server has confirmed it, and a roll the server refuses is reported as refused. Marks, payments and messages do not work this way.

## Can I change the school server?

Use a verified backup and test a full restore into an isolated target; copying `data/` alone does not copy PostgreSQL. See [backups](/en/guide-technique/sauvegardes). Founders find their code in their dashboard; institutes do not use this School journey.

For a refused action, check role, country, activation and the exact error before repeating it. Use [school troubleshooting](/en/guide-technique/depannage) for OHADA installation issues.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.