Files, permissions,
all on record.

Your choice: your data is hosted in a company-specific space on Corex360 Cloud or on your own server. The hosting choice is written into the agreement; Corex360 Cloud servers run on DigitalOcean infrastructure. The same Corex360 Security layer runs in both, and access is logged; backups are encrypted and taken daily. Each customer signs in to Corex360 at its own subdomain. The own-server option is on the Run on your own server page.

The decision depends on your corporate policy, and the hosting choice is written into the agreement. If your policy does not allow personal data in the cloud, the installation runs on your own infrastructure; if it does, a company-specific space on Corex360 Cloud is used. On an own-server installation X AI runs on a local model; on Corex360 Cloud the company chooses its own AI provider. The KVKK difference between the two is in the KVKK: cloud or own server article.

Personal data is processed under KVKK, Turkey's data protection law. Access is role-based, and every open and download is recorded. Hosting runs on Corex360 Cloud or on your own server. The scope of the data processing agreement and how data subject requests are handled are on the demo list on the Security page. The terms data controller, data processor and data processing agreement are explained in the Glossary.

Yes, Corex360 has been through a comprehensive penetration test, carried out in-house with Corex360 Security, which the Corex360 team developed. It is tested regularly from an attacker's point of view. The same Corex360 Security layer runs on Corex360 Cloud and on an own-server installation, logging every sign-in, device, and access. How findings are closed is on the demo list on the Security page. All the layers are on the Security page.

If you run Corex360 on your own server, the data is already on your infrastructure; on Corex360 Cloud it sits in a company-specific space. The hosting choice is written into the agreement, and backups are encrypted and taken daily. Export formats and handover when the contract ends are not promised on this site; both are on the open topics list on the Security page.

In Corex360, access is role-based: every user sees only the records within their role. A permission change needs manager approval and is logged. Corex360 Security records every sign-in, device and access; failed sign-ins, new devices, unusual downloads and permission changes are reported to the account owner immediately, and the record also appears in the morning briefing.

Sharing happens through timed, permissioned links, and a link is revoked in one tap. The shared file stays inside the record it belongs to. Every view and download is logged, so who saw a shared file and when is always clear. The system does not decide on its own who a file is opened to: the role sets the permission and the user sets the share.

Corex Drive has shared spaces by department or topic, the company defines its own tags, and shared files gather in the Shared section. Each department sees the same file under its own permission, and sharing uses timed, revocable links. Every view and download is logged. A customer's files sit in the Files and Drive tabs of the customer card.

A document management system is software that stores a company's documents, decides who can reach them and logs that access. Corex Drive does this by keeping each file inside the customer or project record it belongs to; the customer card has Files and Drive tabs. The general picture is in the What is a document management system article.

The signed contract is kept in Corex Drive, tied to the customer record; the contract's start and end dates sit on the contract card, and the renewal decision stays with you. Only those whose role allows it open the contract, and who opened what in a legal file, and when, is read from the record. The archive is detailed on the Corex Drive module page.