Judicial-Portal Access Policy

Last updated: 12 August 2026 · Version: 1.0Ελληνική έκδοσηDownload PDF (EL/EN)

This page describes CourtSync's operational policy for accessing supported judicial portals. It addresses the scope of queries, request-frequency controls, authenticated-session handling, and communication with portal operators.

For technical controls protecting credentials and data, see Security Architecture and Judicial-Portal Integration. For contractual and data-processing terms, see the Terms of Service, Privacy Policy, and Data Processing Agreement.

This page is informational, does not form part of the Terms of Service, and does not state or imply that CourtSync has been approved, certified, or endorsed by any judicial-system operator.

The Greek and English versions are intended to have the same meaning. If they differ, the English version prevails.

1. Scope of access

CourtSync sends requests only for cases and identifiers selected or enabled by an authorised user. It is not used for general crawling, bulk collection, or indexing of judicial-portal content.

Access uses credentials supplied by the customer and only within the feature enabled by the customer. For each monitored matter, the user confirms that they are authorised to access and process the relevant information.

2. Request and session controls

CourtSync applies technical controls at account, case, and request-frequency levels. Where technically appropriate, it reuses an existing authenticated session to avoid unnecessary repeat logins.

Out-of-schedule checks occur only following an explicit user action. Exact schedules, limits, and thresholds are not published because they are adjustable operational and anti-abuse controls.

3. Access restrictions and portal stability

CourtSync evaluates the technical results of requests and may reduce frequency, defer checks, or temporarily suspend an integration when a portal returns access restrictions, elevated error rates, or indications of instability.

CourtSync does not use circumvention techniques, identity or network-address rotation, or origin obfuscation to continue access that has been restricted or blocked.

4. Service identification and operator contact

Where supported by the technical environment, automated requests carry a CourtSync service identifier and an operator contact route.

Reports concerning load, compatibility, access patterns, or technical impact are reviewed by Hartwell and may result in immediate restriction or temporary suspension of the relevant integration. Operators may contact support@courtsync.gr.

5. Official interfaces and technical coordination

Hartwell prefers official, documented interfaces supported by the operator of the relevant system. Where an official API, approved system-to-system integration, or interoperability programme covers the relevant functionality, it will be evaluated and, where appropriate, adopted as the preferred integration method.

Judicial-system operators and institutional stakeholders may contact support@courtsync.gr regarding technical coordination, exchange of technical information, interoperability testing, or migration to an official interface.