Concepts

The app profile

A declaration is two lists: what the app does, and where it operates. LexLint matches obligations against those two lists and nothing else.

Activities

What the app does, from this list. It is read from the live server at each build, so it is always the server's own list:

• crawls_web
• trains_models
• generates_content
• deploys_chatbot
• automated_outreach
• high_risk_decisions
• processes_voice
• processes_biometrics
• publishes_adult_content
• operates_social_platform
• serves_minors
• operates_app_store
• ships_mobile_app
• aggregates_content
• distributes_software_product
• handles_health_records
• provides_financial_services
• operates_essential_service
• is_listed_company
• provides_telecom_services
• statutory_requests
• records_conversations
• tracks_devices

Jurisdictions

Where the app operates, as lowercase slugs whose levels are separated by /, such as us, us/ca, eu, de and kr. A slug is the jurisdiction's path in the UnGovr Atlas, and https://www.ungovr.org/atlas is where to find one. A deeper or unresearched path resolves to the nearest jurisdiction with law, and the jurisdictions whose law is researched are listed at https://lexlint.io/law for you to check.

Name every jurisdiction the app operates in: one left off is simply not linted.

lexlint.yml

The plugin keeps the declaration in lexlint.yml at the repository root, so a second run starts from the first run's answers. The fields are set out in the schema reference.