LEGAL & TRUST
Policy Changes, Versions and Archive Policy
KRAVIA policies must show what version applies and when. Material changes are communicated appropriately; a new notice does not supply consent that the law separately requires. Drafts, approved future versions and current policies are distinct states.
1
Controlled documents
A major public policy carries its title, document identifier, version, effective date, last-updated date and approved canonical route. The website and official downloadable copy must match for that version. The register records approval and supersession so a reader can distinguish a current policy from an archive or a review draft.
Version 1.0 is the selected first controlled framework, with a target effective date of 1 November 2026. The date does not itself constitute approval or publication. A release must pass the legal and operational gates before it becomes the operative public version.
2
Changes and notification
Material policy changes ordinarily receive appropriate advance notice, with a target of 30 days where practical. Suitable channels include registered email, in-product notice or another method reasonably likely to reach affected users. Urgent legal or security requirements may need an earlier change, with a clear explanation where appropriate.
Routine corrections can have a different notice treatment where they do not materially change rights or processing. A new purpose requiring consent must obtain it before the processing begins. Continued browsing is not treated as consent to optional sensitive, marketing or AI uses merely because an updated policy is posted.
3
Existing contracts and regional rights
A public policy update does not automatically override a negotiated agreement or mandatory local rights. Changes to price and renewal follow the applicable commercial notice and authorization rules. Different regional requirements are isolated in the relevant supplement rather than weakening the global baseline for every user.
English is the controlling drafting language except where law requires otherwise. Necessary language options and locally mandatory terms must remain meaningful and usable.
4
Archives
Material previous versions remain accessible through an appropriate archive showing the effective period and replacement date. Archived copies are clearly labelled and excluded from current-version navigation where that avoids confusion. Removal may be necessary for a specific lawful or security reason, but an appropriate internal record is retained.
No historical version, signature or approval is fabricated. A first release may legitimately have no earlier adopted version even if earlier working drafts exist.
5
Reviews and responsibility
Policies are reviewed at least annually and when material laws, processing, providers, AI features, products, regions, security controls or commercial models change. The responsible owner verifies facts; counsel reviews applicable legal issues; the publication owner checks routes, PDFs and notices.
A feature can be technically complete while its policy is not approved, and a policy can be fully authored while the feature is not verified. The release record must preserve this distinction. Questions may be sent to legal@kraviaprivatelimited.com or privacy@kraviaprivatelimited.com.