askrobots / dbbasic-object-server
Public
Runs live, versioned Python application objects on one VM, with a suite of apps: projects, notes, tasks, files and more.
danq9
signup: the person chooses the password and name on the confirm page
83c7aa6
2 weeks, 5 days ago
History
dbbasic-package.json · 3.6 KB · 46 lines
| 1 | { |
| 2 | "id": "app-privacy", |
| 3 | "name": "Privacy", |
| 4 | "version": "0.1.0", |
| 5 | "description": "A privacy policy generated from the server's live configuration, and the subject-access export that goes with it. Almost every privacy policy on the web drifts, and not because anyone lied: the policy is written once by a template and the software changes weekly, with nothing connecting the two. site_privacy is a FOLD over configuration -- the same family as app-nav's registry and the attention counts -- so it cannot claim a 30-day retention while the box keeps 180, cannot name a payment processor nobody configured, and cannot stay silent about a cookie the server sets. Analytics off says plainly that no traffic data is collected; on, it names the fields actually recorded and states the retention by reading DBBASIC_ANALYTICS_RETENTION_DAYS and DBBASIC_ANALYTICS_MAX_ROWS. The cookie table lists exactly the cookies this configuration can set with their real Max-Age and whether each is strictly necessary -- and tests/test_privacy.py sweeps the whole codebase for anything that sets a cookie and FAILS naming any cookie the table does not disclose, so a new cookie added anywhere breaks the build until somebody writes down what it is for. Sections appear only when the thing exists: payments with app-payments, delivery with app-shipping, email when SMTP is configured, AI when a provider key is stored. The sub-processor list is derived from credentials actually present (Stripe keys set, a carrier chosen, an SMTP host, an AI key), so it is a list nobody has to remember to update. Controller identity comes from app_settings (privacy.controller_name, privacy.contact_email, privacy.jurisdiction) and the page REFUSES to publish a policy until they are set, naming the missing settings -- an unsigned policy is worse than none, because it looks like compliance while giving a reader nobody to write to. privacy.extra_markdown carries the operator's own reviewed legal text, rendered under its own heading so a reader can tell generated fact from human statement. What it will not do is invent legal text: no lawful bases, no Standard Contractual Clauses, no transfer mechanisms. It states facts about the system and stops. /cookies is the table alone and /privacy.json the same fold machine-readable, with no timestamp in it so it can be diffed between deploys. action_export_subject_data folds every collection keyed to one email -- orders, invoices, carts, disputes, contacts, then payments through those invoices and shipments through those orders -- into one document, operator-executed only, and returns nothing keyed to anyone else. Erasure is deliberately absent: it needs a redaction-with-tombstone design and a doctrine decision about which fields are contact and which are evidence, and code written before that decision would make the choice silently in the one place it can never be undone.", |
| 6 | "compatibility": { |
| 7 | "dbbasic_object_server": ">=0.1.0" |
| 8 | }, |
| 9 | "dependencies": [ |
| 10 | "app-settings" |
| 11 | ], |
| 12 | "objects": [ |
| 13 | { |
| 14 | "id": "site_privacy", |
| 15 | "path": "objects/site/privacy.py" |
| 16 | }, |
| 17 | { |
| 18 | "id": "action_export_subject_data", |
| 19 | "path": "objects/action/export_subject_data.py" |
| 20 | } |
| 21 | ], |
| 22 | "schemas": [], |
| 23 | "permissions": [ |
| 24 | { |
| 25 | "path": "permissions/rules.json" |
| 26 | } |
| 27 | ], |
| 28 | "seed": [ |
| 29 | { |
| 30 | "collection": "site_routes", |
| 31 | "path": "seed/site_routes.tsv" |
| 32 | } |
| 33 | ], |
| 34 | "migrations": [], |
| 35 | "nav": [ |
| 36 | { |
| 37 | "id": "privacy", |
| 38 | "label": "Privacy", |
| 39 | "path": "/privacy", |
| 40 | "blurb": "What this server records, folded from its own configuration", |
| 41 | "surface": "public", |
| 42 | "group": "System", |
| 43 | "order": 690 |
| 44 | } |
| 45 | ] |
| 46 | } |