AncientArtifacts.co

Privacy policy

The site is designed to provide research tools without requiring users to upload sensitive collection details.

Information the site may collect

When configured for production, the site may collect standard server logs, aggregate analytics, page interactions, referral information and voluntary contact-form submissions. The current package contains placeholder analytics and form identifiers that must be replaced.

The operator should document the actual data processors and retention periods after deployment.

Browser-based tools

The provenance, due-diligence, authenticity, document, conservation, cost and inventory tools run in the visitor's browser. In this static version, entered collection details are not intentionally transmitted to AncientArtifacts.co.

Printing an inventory may expose information to local printer or browser systems controlled by the user.

Sensitive provenance information

Exact storage locations, insurance values, private addresses, unpublished excavation coordinates and security details can create theft, privacy or cultural-property risks. Use secure professional channels for complete files.

Avoid sending passport copies, financial records or unredacted third-party addresses through ordinary web forms.

Third-party links

Official resources and marketplaces have their own privacy practices. Opening an external link can disclose ordinary browser and referral information to that service.

External services may operate in different jurisdictions and apply their own cookies, accounts and access rules.

Cookies and analytics

Production analytics may use cookies or similar technologies. The operator should implement consent where required and publish accurate controls.

Do not retain the placeholder measurement ID in production.

Contact submissions

Messages may be retained to answer editorial questions, correct content, manage partnerships or protect legal rights. Do not use the form for urgent restitution claims or anonymous artifact offers.

The operator should create a separate secure process if it later accepts sensitive submissions.

Security

No website can guarantee absolute security. Use HTTPS, limited administrative access, backups, updates and minimal collection of personal data.

Collection inventories should be stored with access controls appropriate to their theft and ownership sensitivity.

Children and changes

The site is educational but is not designed to collect personal information from children. Guardians should supervise purchases and communications.

This starter policy should be reviewed after the final analytics, forms, hosting, business address and jurisdiction are known.

Data minimization

The safest collection database is one that gathers only what is needed. Public-facing forms should not request object storage locations, full ownership chains, legal identification documents or high-resolution security-sensitive images unless a secure professional workflow has been established.

Retention and deletion

Production operations should adopt written retention periods for contact messages, logs, analytics and partnership records. Records should be deleted or anonymized when they are no longer needed for the stated purpose, legal compliance, security or dispute handling.

Access and correction requests

Where applicable law provides rights to access, correct or delete personal information, the operator should publish a verified request process. Requests involving provenance files may require identity verification to avoid disclosing sensitive ownership information to the wrong person.

International visitors

Visitors, hosting providers, analytics services and merchants may be located in different countries. Production disclosures should accurately describe any international processing and the safeguards used by the actual vendors.