Skip to content

Security

Xyreka separates organisation knowledge, private project submissions and architecture-board discussion through application-level permissions. Access is checked on the server, not inferred from a menu, job title, email provider or email domain.

Security controls

Data handling

Organisation knowledge stores versioned pages and scanned Word/diagram assets. Private project intake retains checklist responses, design documents and the exact published guidance used in a submission. File uploads require configured private storage and malware scanning. Reference URLs are not automatically fetched or archived. The public site is served over HTTPS.

Current boundaries

The pilot shares an application process and database infrastructure. These permission boundaries are not separate service, database or storage isolation. Organisation SSO and assignable custom roles are not available yet. Formal decisions require an explicit human approval grant; AI output is advice only. Do not use the pilot as your authoritative approval system before supervised acceptance.

Xyreka supports a review process; it does not certify a design or guarantee compliance. Contact support@xyreka.com to report a security concern. Do not include passwords or private project documents in your first message.

For detailed commitments and legal terms, review our Privacy and Terms pages.

Back to home