Summary: ArchaeoHub collects only the data necessary to provide the platform. We do not sell your data. Payments are processed exclusively by Google Play — we never see your payment card details. You can request deletion of all your data at any time.
1Who We Are
ArchaeoHub ("we", "us", "our") is a digital excavation management platform developed for archaeological teams and researchers. Our web application is accessible at tot-archaeohub-demo.vercel.app and our mobile app is available on the Google Play Store.
This Privacy Policy explains what personal data we collect, why we collect it, and how we protect it.
2Data We Collect
We collect the following categories of data:
Account Data
- Email address (used for login and team invitations)
- Display name (optional, set via Google sign-in or manually)
- User ID (randomly generated by Firebase Authentication)
Excavation & Research Data
- Excavation site names, locations, periods, and descriptions
- Logbook entries including text, images, and metadata
- 3D model files (OBJ, STL, PLY, GLB) uploaded to Firebase Storage
- Reconstruction results and assembly diagram PDFs
- Team membership records (email addresses of invited collaborators)
Credits & Transaction Data
- Current credit balance (stored in Firestore)
- Transaction history: purchases and credit deductions (amount, SKU ID, Google Play order ID, timestamp)
Technical Data
- Device type and operating system (collected by Firebase)
- App version
- Crash logs and performance metrics (Firebase Crashlytics/Analytics if enabled)
We do not collect: payment card numbers, bank details, precise GPS location, microphone or camera data, contacts, or any data unrelated to the archaeological management workflow.
3How We Use Your Data
- Authentication: To verify your identity and maintain a secure session.
- Platform functionality: To store and retrieve excavation sites, logbook entries, 3D assets, and reconstruction results.
- Team collaboration: To invite and manage team members and enforce permissions.
- Credit system: To record your credit balance and transaction history so purchased credits persist across sessions and devices.
- PDF generation: To produce assembly diagrams that include artifact metadata from your account.
- Service improvement: Aggregated, anonymized usage data may be used to understand how the platform is used and improve its features.
We do not use your data for advertising, profiling, or any purpose unrelated to operating ArchaeoHub.
4Third-Party Services
ArchaeoHub relies on the following trusted third-party services:
-
Google Firebase (Authentication, Firestore, Storage, Hosting) —
Privacy Policy.
Firebase may collect usage and diagnostic data as described in their terms.
-
Vercel (Web hosting) —
Privacy Policy.
Vercel may log request metadata for security and performance.
-
Google Play (In-app billing) —
Google Privacy Policy.
All payment processing is handled exclusively by Google Play. We never receive your payment card details.
-
Render.com (3D reconstruction API server) —
Privacy Policy.
3D model data is temporarily transmitted to our reconstruction server to perform the assembly and is not stored permanently.
Each third party operates under its own privacy policy. We encourage you to review them.
5In-App Purchases & Payments
Credit purchases are made through Google Play Billing in our Android app. The payment flow works as follows:
- You select a credit package in the app.
- Google Play handles the entire payment transaction — we never see, store, or process your payment method.
- Upon successful payment, Google Play notifies our app with a purchase token and order ID.
- Our app writes the corresponding credit amount to your Firestore account, along with the order ID for traceability.
We do not store payment card numbers, bank details, or any financial information. All billing is managed entirely by Google Play under Google's privacy terms.
For refund requests, please contact Google Play support directly, as refunds are processed through their platform.
6Data Storage & Security
All user data is stored in Google Firebase infrastructure:
- Firestore: User profiles, excavation data, logbook entries, credits, and transactions. Access is restricted by security rules — users can only read/write their own data.
- Firebase Storage: Uploaded 3D model files and generated PDFs. Files are stored with authenticated access — only authorized users can read or write their site's files.
Data is stored in Google Cloud's secure infrastructure with encryption at rest and in transit (TLS). We apply role-based access control through Firestore Security Rules to prevent unauthorized access.
7Data Retention
- Account data: Retained as long as your account is active.
- Excavation data, 3D files, logbooks: Retained until you delete the site or individual records.
- Transaction history: Retained for 3 years for accounting traceability, then deleted.
- On account deletion: All associated data (sites, assets, logbook entries, credits) is permanently deleted within 30 days.
8Children's Privacy
ArchaeoHub is not directed at children under the age of 13. We do not knowingly collect personal data from children under 13. If you believe a child has provided us with personal data, please contact us at the address below and we will promptly delete it.
9Your Rights
Depending on your location, you may have the following rights regarding your personal data:
- Access: Request a copy of the personal data we hold about you.
- Correction: Request that we correct inaccurate data.
- Deletion: Request deletion of your account and all associated data.
- Portability: Request your data in a portable format (JSON).
- Objection: Object to certain uses of your data.
To exercise any of these rights, please contact us at gulerege.tr@gmail.com. We will respond within 30 days.
10Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will update the "Last Updated" date at the top of this page. If the changes are material, we will notify you via the app or by email.
Continued use of ArchaeoHub after changes take effect constitutes acceptance of the updated policy.