Legal, licensing, privacy, and accessibility
Find the controlling Akashic terms, privacy, licensing, attribution, DMCA, and accessibility documents and understand which source governs each issue.
This page routes readers to the controlling legal and policy documents. It is an orientation page, not a substitute for the applicable terms.
Terms and privacy
Use the current Terms and Privacy pages published by Akashic for account, service, analytics, user-content, and data-handling rules. Product documentation does not override those terms.
When a feature involves authentication, billing, saved Places, profiles, or user-generated content, review the policy linked from that feature before use.
License and attribution
The repository LICENSE, public license file, and ATTRIBUTION.txt define the Akashic license and upstream notices. Upstream datasets retain their own licenses and attribution requirements.
Before redistributing a combined dataset or derived product:
- identify the Akashic material used;
- retain required Akashic attribution;
- identify upstream sources and their terms;
- verify whether raw-source redistribution is permitted;
- avoid implying endorsement by Akashic or an upstream agency.
DMCA
Use the published DMCA page for copyright notices and counter-notices. Include the required identification, contact, work, location, good-faith, accuracy, and signature information.
Accessibility
The accessibility statement describes the product's accessibility goals and contact process. Documentation and product changes should support keyboard operation, semantic headings, readable contrast, responsive layouts, reduced motion, descriptive links, and accessible alternatives for visual data.
An accessibility statement does not guarantee that every third-party source file or embedded product is accessible. Report a specific barrier with the URL, device/browser, assistive technology, and action attempted.
Data accuracy and limitations
Akashic publishes source-led records and methods but cannot eliminate limitations in upstream data, historical boundaries, survey estimates, or derived geography. A documented correction process does not create a warranty beyond the controlling terms.
Controlling-source order
For a conflict, use this order:
- applicable law and binding agreement;
- current published Terms or Privacy policy;
- repository/public license and attribution files;
- specific feature or data contract;
- this orientation page.
Legal and policy claims are reviewed more frequently than general guides because requirements and product behavior can change.