| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 2723 |
| Technical Name |
do_school_privacy |
| License | OPL-1 |
| Website | http://doincredible.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 2723 |
| Technical Name |
do_school_privacy |
| License | OPL-1 |
| Website | http://doincredible.com |
School ERP — Privacy & Consent
Country-neutral data-protection engine: consent, retention policies & breach tracking with config-gated enforcement.
Consent
Retention Policies
Breach Tracking
Config-Gated
A structured, auditable way to govern personal data
Privacy & Consent gives the institution a clear, auditable framework to record consent, define retention policies and track data breaches. The engine is deliberately country-neutral: localizations set the country-specific dials such as minor age thresholds, statutory breach windows and verification providers, so the same core works in every jurisdiction.
Destructive retention runs only behind a configuration flag, so rollout is safe by default — until you enable enforcement, the scheduled job simply logs what it would change. A reusable consent gate lets any other suite module check a granted purpose before it processes data.
Key Features
Consent Records
Consent purposes and records with channels (portal, paper, email, more), statuses and stored evidence.
Verification Methods
Pluggable consent verification methods configurable per institution and locale.
Consent Gate
A reusable check other suite modules call to gate processing by a granted purpose.
Retention Policies
Per-model policies with date field, retention period and action: archive, anonymize or delete.
Safe Enforcement Cron
Scheduled enforcement that only acts when enabled; otherwise it logs what would change.
Breach Register
Breaches with severity, statutory deadline, workflow states, chatter and activities.
Screenshots
How It Works
User Roles
| Role | Access |
|---|---|
| Data Protection Officer | Manage consent records, retention policies and data breaches. |
| Principal | Oversight access to privacy records across the institution. |
| School Administrator | Full configuration of privacy data, settings and enforcement. |
Integration
Builds on do_school_core and reuses its Data Protection Officer role for scoped access.
Operates over partners and any suite model through configurable retention policies.
Exposes a reusable consent gate any module in the suite can call before processing data.Integrates with Odoo mail, scheduled actions (cron) and configuration settings.Technical Information
Odoo Version: 19.0 (Community)
Models: do.consent · do.consent.purpose · do.consent.verification.method · do.retention.policy · do.data.breach (extends res.config.settings)
Dependencies: do_school_coreLicense: LGPL-3Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module