Security & Compliance
Klynke is built to run entirely inside your Microsoft 365 environment. All data stays within your tenant and is protected by the same enterprise‑grade security, governance, and compliance controls already enforced across Microsoft 365, Azure, and SharePoint.
Klynke operates fully within your Microsoft 365 tenant. This architecture ensures:
-
No external servers
-
No third‑party data processors
-
No data transfer outside your tenant
-
No AI, machine learning, or automated decision‑making
-
No credential storage
Your organization retains full control over access, permissions, and data lifecycle management.
Microsoft 365‑Native by Design
1. Data Residency & Storage
All customer data is stored exclusively inside your Microsoft 365 tenant.
-
Time entries, projects, tasks, and metadata are stored in SharePoint Online.
-
Configuration and operational data are stored in Azure Storage within your tenant.
-
No external databases, servers, or cloud services are used.
-
Data never leaves your Microsoft 365 security boundary.
Your data inherits Microsoft’s encryption, retention, governance, and compliance controls.
2. Identity & Access Management
Authentication and authorization are handled entirely by Microsoft Entra ID (Azure AD).
-
Single Sign‑On across Teams, Outlook, and the web
-
Inherits Conditional Access, MFA, and identity governance policies
-
No separate credentials or identity stores
-
Role‑based access control (RBAC) managed by your administrators
Klynke never stores or processes user credentials.
3. Network & Data Flow
Klynke does not proxy, replicate, or transmit customer data outside Microsoft 365.
-
All data access occurs through Microsoft Graph and standard Microsoft 365 APIs
-
All communication remains within your tenant’s Microsoft 365 trust boundary
-
No external compute, middleware, or data routing
Your data never passes through Klynke‑controlled infrastructure.
4. Administrative Control
Your Microsoft 365 administrators retain full control over:
-
User provisioning and access
-
Permissions and group assignments
-
Data lifecycle management
-
App deployment across Teams, Outlook, SharePoint, and Azure AD
Klynke introduces no new administrative identity surfaces.
5. Compliance Alignment
Because Klynke stores and processes data exclusively inside your Microsoft 365 tenant, your data inherits Microsoft’s compliance posture, including:
-
ISO/IEC 27001
-
SOC 1/2/3
-
GDPR alignment
-
Microsoft’s global security and privacy certifications
Klynke does not introduce additional data processors or external compliance obligations.
6. Architecture Overview
Klynke runs entirely within your Microsoft 365 tenant using:
-
Microsoft Teams app
-
Microsoft Graph API
-
Tenant‑scoped Azure AD app registration
All logic, data, and authentication remain inside your tenant boundary.
No external servers.
No external data flow.
No third‑party processors.
7. Security FAQ
Where is Klynke data stored?
Inside your Microsoft 365 tenant (Azure + SharePoint Online).
Does Klynke use external servers?
No. All data stays within your tenant.
Does Klynke use AI or machine learning?
No. Klynke does not use AI, ML, or automated decision‑making.
How is authentication handled?
Through Microsoft Entra ID with SSO, MFA, and Conditional Access.
Does Klynke store credentials?
No. Klynke never stores or processes passwords.
How does Klynke access data?
Via Microsoft Graph with delegated, consent‑based permissions.
Does Klynke introduce new data processors?
No. All processing occurs within Microsoft 365.
Who controls access?
Your Microsoft 365 administrators.
8. Summary for Security & Procurement Teams
-
100% Microsoft 365‑native
-
No external data flow
-
No external compute
-
No external identity system
-
No AI or automated decision‑making
-
All data stored in your tenant
-
Inherits Microsoft’s compliance certifications
-
Full administrative control remains with your organization
Klynke is built for organizations that require the highest level of security, data residency control, and compliance alignment.