Notitie
Voor toegang tot deze pagina is autorisatie vereist. U kunt proberen u aan te melden of de directory te wijzigen.
Voor toegang tot deze pagina is autorisatie vereist. U kunt proberen de mappen te wijzigen.
Last updated by the developer on: August 31, 2026
General information
Information provided by to Microsoft:
| Information | Response |
|---|---|
| App name | SYNCDATE |
| ID | ddss.syncdate |
| Company's website | https://syncdate.app |
| App's Terms of Use | https://syncdate.app/terms |
| Core functionality of the app | SYNCDATE keeps one person's calendars in step across providers. The user connects accounts over OAuth (Microsoft 365/Outlook via Microsoft Graph, Google Calendar, and CalDAV servers), picks which calendars pair with which, the direction (one way or both ways), and what copies across (busy only, or full details). SYNCDATE creates, updates and deletes only its own copies on the target calendars, driven by Graph change notifications with 15-minute polling as fallback. Originals are never modified. |
| Company headquarter location | Romania |
| App info page | https://syncdate.app/features |
| What is the hosting environment or service model used to run your app? | Iaas_Hybrid_Onprem |
| Which hosting cloud providers does the app use? | Other |
| Is AI functionality part of the app�s core features or workflows? | No |
| Online Service interfaces | Microsoft Graph REST API v1.0, delegated permissions only (Calendars.ReadWrite, User.Read, offline_access, openid, email, profile). |
Endpoints: /me; /me/calendarGroups; /me/calendars; /me/calendars/{id}/calendarView; /me/calendars/{id}/events (GET/POST/PATCH/DELETE); /me/calendars/{id}/events/delta; /me/calendars/{id}/events/{id}/instances; /me/outlook/masterCategories; /$batch; /subscriptions (change notifications).
OAuth 2.0 via login.microsoftonline.com. No EWS, SharePoint or Teams. |
Questions
Questions or updates to any of the information you see here? Contact us!
How the app handles data
This information has been provided by about how this app collects and stores organizational data and the control that your organization will have over the data the app collects.
| Information | Response |
|---|---|
| Does the app or underlying infrastructure process any data relating to a Microsoft customer or their device? | Yes |
| What data is processed by your app? | Identity from OAuth sign-in: name, email address, provider account id. Calendar metadata: calendar names, ids, colours, time zones. Event data from the calendars the user explicitly selects: start/end times, title, description, location, attendees, organiser, recurrence rules, free/busy status, provider event ids. OAuth access and refresh tokens. Stripe customer and subscription ids (no card data). Operational logs with correlation ids. |
| Does the app support TLS 1.2 or higher? | Yes |
| Does the app or underlying infrastructure store any Microsoft customer data? | Yes |
| What data is stored in your databases? | PostgreSQL 15 in Germany: user records (name, email); OAuth access and refresh tokens encrypted at rest with AES-256-GCM; connected calendar lists; sync configurations and per-calendar rules; a mapping of source event id to the SYNCDATE-created copy id; a short-lived event cache (purged at 14 days, or 48 hours if stale); sync run logs; entitlement and Stripe subscription ids; email preferences. No payment card data. |
| If underlying infastructure processes or stores Microsoft customer data, where is this data geographically stored? | Germany |
| Do you have an established data rentention and disposal process? | Yes |
| How long is data retained after account termination? | Less than 30days |
| Do you have an established data access management process? | Yes |
| Do you transfer customer data or customer content to third parties or sub-processors? | Yes |
| Do you have data sharing agreements in place with any third party service you share Microsoft customer data with? | Yes |
Questions
Questions or updates to any of the information you see here? Contact us!
This information has been provided by SYNCDATE about the security practices this app employs.
| Information | Response |
|---|---|
| Do you perform annual penetration testing on the app? | No |
| Does the app have a documented disaster recovery plan, including a backup and restore strategy? | Yes |
| Does your environment use traditional anti-malware protection or application controls? | ApplicationControls |
| Do you have an established process for indentifying and risk ranking security vulnerabilities? | No |
| Do you have a policy that governs your service level agreement (SLA) for applying patches? | No |
| Do you carry out patch management activities according to your patching policy SLAs? | No |
| Does your enviroment have any unsupported operating systems or software? | No |
| Do you conduct quarterly vulnerability scanning on your app and the infastructure that supports it? | No |
| Do you have a firewall installed on your external network boundary? | Yes |
| Do you have an established change management process used to review and approve change requests before they are deployed to production? | Yes |
| Is an additional person reviewing and approving all code change requests submitted to production by the original developer? | No |
| Do secure coding practices take into account common vulnerability classes such as OWASP Top 10? | Yes |
| Multifactor Authentication (MFA) enabled for: | CodeRepositories, DNSManagement |
| Do you have an established process for provisioning, modification, and deletion of employee accounts? | No |
| Do you have Intrusion Detection and Prevention (IDPS) software deployed at the perimeter of the network boundary supporting your app? | Yes |
| Do you have event logging set up on all system components supporting your app? | Yes |
| Are all logs reviewed on a regular cadence by human or automated tooling to detect potential security events? | Yes |
| When a security event is detected are alerts automatically sent to an employee for triage? | Yes |
| Do you have a formal information security risk management process established? | No |
| Do you have a formal security incident response process documented and established? | No |
Questions
Questions or updates to any of the information you see here? Contact us!
This information has been provided by SYNCDATE regarding the compliance standards their app requires and has the certifications they have accomplished.
| Information | Response |
|---|---|
| Does the app comply with the Health Insurance Portability and Accounting Act (HIPAA)? | N/A |
| Does the app comply with Health Information Trust Alliance, Common Security Framework (HITRUST CSF)? | N/A |
| Has the organization achieved a Service Organization Controls (SOC 1) Certification? | N/A |
| Has the organization achieved a Service Organization Controls (SOC 2) Certification? | No |
| Has the organization achieved a Service Organization Controls (SOC 3) Certification? | No |
| Do you carry out annual PCI DSS assessments against the app and its supporting environment? | N/A |
| Is the app International Organization for Standardization (ISO 27001) certified? | No |
| Does the app comply with International Organization for Standardization (ISO 27018)? | N/A |
| Does the app comply with International Organization for Standardization (ISO 27017)? | N/A |
| Does the app comply with International Organization for Standardization (ISO 27002)? | N/A |
| Is the app Federal Risk and Authorization Management Program (FedRAMP) compliant? | No |
| Does the app comply with Family Educational Rights and Privacy Act (FERPA)? | N/A |
| Does the app comply with Children's Online Privacy Protection Act (COPPA)? | N/A |
| Does the app comply with Sarbanes-Oxley Act (SOX)? | N/A |
| Does the app comply with NIST 800-171? | N/A |
| Has the app been Cloud Security Alliance (CSA Star) certified? | No |
Questions
Questions or updates to any of the information you see here? Contact us!
| Information | Response |
|---|---|
| Do you have GDPR or other privacy or data protection requirements or obligations (such as CCPA)? | Yes |
| Does the app have an external-facing privacy notice that describes how it collects, uses, shares, and stores customer data? | Yes |
| Privacy Policy URL | https://syncdate.app/privacy |
| Does the app perform automated decision making, including profiling that could have a legal effect or similar impact? | No |
| Does the app process customer data for a secondary purpose not described in the privacy notice (i.e. marketing, analytics)? | No |
| Do you process special categories of sensitive data (i.e. racial or ethnic origin, political opinion, religious or philosophical beliefs, genetic or biometric data, health data) or categories of data subject to breach notification laws? | No |
| Does the app collect or process data from minors (i.e., individuals under the age of 16)? | No |
| Does the app have capabilities to delete an individual's personal data upon request? | Yes |
| Does the app have capabilities to restrict or limit the processing of an individual's personal data upon request? | Yes |
| Does the app provide individuals the ability to correct or update their personal data? | Yes |
| Are regular data security and privacy reviews performed (for example, Data Protection Impact Assessments or privacy risk assessments) to identify risks related to the processing of personal data for the app? | No |
Questions
Questions or updates to any of the information you see here? Contact us!
| Information | Response |
|---|---|
| Does your application integrate with Microsoft identity platform (Microsoft Entra ID) for single-sign on, API access, etc.? | Yes |
| Have you reviewed and complied with all applicable best practices outlined in the Microsoft identity platform integration checklist? | Yes |
| Does your app use the latest version of MSAL (Microsoft Authentication Library) or Microsoft Identity Web for authentication? | No |
| Does your app support Conditional Access policies? | No |
| If your app does not use one of the above libraries, what authentication library or libraries does it use? | NextAuth.js (Auth.js) v4.24.13 with its built-in Azure AD provider, which uses openid-client v5.7.1 for OpenID Connect discovery and the OAuth 2.0 authorization code flow. Session tokens are signed and verified with jose v5.10.0. Connecting an additional calendar account uses a direct authorization code exchange against login.microsoftonline.com/common/oauth2/v2.0. Neither MSAL Node nor Microsoft.Identity.Web is used; the app relies on standard, provider-agnostic OIDC and OAuth 2.0 libraries. |
| Does your app support Continuous Access Evaluation (CAE) | No |
| Does your app store any credentials in code? | No |
| Apps and add-ins for Microsoft 365 might use additional Microsoft APIs outside of Microsoft Graph. Does your app or add-in use additional Microsoft APIs? | No |
Data access using Microsoft Graph
Graph Permission Permission Type Justification Microsoft Entra App ID Calendars.Read delegated SYNCDATE reads events from the calendars the user selects as a source and creates, updates and deletes its own copies on the calendars they select as targets. Read-only access cannot create or remove a copy, so ReadWrite is the minimum that supports the product's core function. Access is delegated and limited to the signed-in user's own calendars. The app never requests Calendars.ReadWrite.All or any application permission, and never reads a calendar the user has not explicitly chosen. 4e28e278-b86c-4ae2-90b8-90c57cce5200 Calendars.ReadWrite delegated Reads the signed-in user's display name and email address so the connected account can be labelled in the interface and matched to the correct SYNCDATE account. No directory data and no data about any other user is read. 4e28e278-b86c-4ae2-90b8-90c57cce5200 offline_access delegated Refreshes the access token so calendar sync can continue in the background between sign-ins. Without it, sync would only run while the user is actively signed in, which defeats the purpose of a background sync service. 4e28e278-b86c-4ae2-90b8-90c57cce5200
This application does not have Additional APIs.
Questions
Questions or updates to any of the information you see here? Contact us!