Asked before every rollout.
The short answers. For the long ones — with your documents on the screen — book a call.
Where does GiDoc run?
On your infrastructure: a private cloud tenancy, an air-gapped data centre, or a single Windows server with managed services. Your documents never leave your control, and the platform makes no external calls.
Which languages does it support?
English, French and Arabic are first-class citizens across the entire interface, including full right-to-left layout — and OCR text extraction works in all three.
How do documents get into GiDoc?
Four doors: drag-and-drop or bulk upload with metadata import, mailbox capture from a connected inbox, and public forms. Everything arrives in one governed repository and is classified on the way in.
Can it replace our records-management process?
That's what it's built for: record declaration, retention schedules, legal holds, a closed archive and human-approved destruction — each step audited, so the lifecycle is defensible in front of an auditor.
Is it compliant with ISO 27001 / eIDAS?
GiDoc is built around ISO/IEC 27001-aligned security practices and eIDAS-ready signing with certificate-backed, content-bound signatures. Certification always applies to an organisation's deployment and processes — we'll walk you through the mapping on a call.
How does migration from our current system work?
Bulk import with metadata mapping brings existing files and their properties over in batches; a CSV/JSON import matches metadata to files by name. Most teams migrate one workspace at a time.
What does the audit trail cover?
Every governance event: views, downloads, permission changes, lifecycle transitions, workflow decisions and destructions — recorded in sequence and exportable as evidentiary CSV or JSON.
How do we evaluate it?
Register for a 30-minute call: your use case, a live walkthrough of the modules that matter to you, and a straight answer on fit, deployment and timeline.