Legal information
Privacy Policy
In force from .
Operator
Moderanto is built and operated by AI Executive Kft.
- Registered office
- 1045 Budapest, Ősz utca 126/A, Hungary
- Company registration number
- 01-09-455987
- Court of registration
- Court of Registration of the Budapest-Capital Regional Court
- Tax number
- 33042127-2-41
- EU VAT number
- HU33042127
- Phone
- +36 70 629 2222
- [email protected]
Scope and responsibilities
This notice covers the Moderanto public website and application, including connected Google services. Account registration happens in the Moderanto application atapp.moderanto.ai. The public website does not collect account details through a signup or application form.
PLACEHOLDER — confirm when AI Executive Kft. acts as a data controller and when it processes customer workspace data on the customer's instructions; add the applicable data processing agreement and responsibilities.
Application data and purposes
Moderanto processes account and organization information, workspace records and content, attachment references, connection settings, and authentication/session data to provide the application. Security and audit records support access control and investigation of issues. The data involved depends on the modules and connections you use.
PLACEHOLDER — confirm the complete data categories, support and billing data, legal basis for each purpose, required versus optional information, and any product measurement or marketing processing. Confirm Google sign-in availability and the profile fields it accesses.
Google Drive: access, use, and storage
When an authorized workspace user connects Google Drive as storage, Moderanto requests thedrive.file permission. It can work with files created through the application and files you explicitly select or authorize for it, rather than unrestricted access to every file in your Drive.
Moderanto uses this access for file storage and attachment workflows, including listing accessible files, reading metadata, uploading, copying, downloading, previewing, and retrieving thumbnails. File removal operations may trash or delete accessible files, depending on the operation. The connection creates or finds an application folder in Drive.
Connection settings include the connected Google account email, the connecting user and time, and folder identifiers. Moderanto stores access and refresh tokens in its secret store and retains attachment references such as file identifiers, names, types, and sizes in application records. File bytes pass through Moderanto servers when needed for these workflows; the files themselves are held in your connected Drive.
PLACEHOLDER — confirm any temporary copies, caching, scanning, operational logs, retention, and processing locations for Google file content and metadata, including downstream publishing or AI workflows.
Google Calendar: planned import and synchronization
Google Calendar integration is planned in two stages: read-only import first, followed by write access and two-way synchronization. These stages are not described here as currently available. Read-only import will not authorize changes to your Google events; the later write stage will require additional permission for event changes.
PLACEHOLDER — after implementation, specify the exact permissions, calendar and event fields accessed, imported data stored, purpose and visibility, two-way create/update/delete behavior, conflict handling, token storage, retention, and disconnect/deletion behavior. Update this notice and the consent flow before enabling additional access.
Sharing, service providers, and AI clients
Connected storage and publishing workflows exchange data with the service you configure. Workspace access and authorized AI connections are governed by application permissions. Third-party services have their own privacy terms.
PLACEHOLDER — list hosting, email, payment, monitoring, storage, and other processors; identify processing countries and any international-transfer safeguards. Confirm which Google-connected data can reach workspace users, publishing destinations, or a user's chosen AI provider, and the consent and controls for each transfer.
PLACEHOLDER — confirm and document Google API Services User Data Policy compliance, including Limited Use, permitted transfers and human access, no advertising/data-sale use of Google data, and restrictions on AI model training. This placeholder is not a claim that those practices have been verified.
Retention, disconnection, and deletion
Disconnecting Drive clears its connection configuration and attempts to revoke the Google authorization and delete stored tokens. If revocation fails, access may also need to be removed in your Google Account. Disconnecting does not delete your Drive files or automatically erase attachment records. Removing Google access does not erase data already stored in Moderanto.
The current operator tenant-deletion action marks the tenant as deleted and retains its data. It is not a complete erasure process.
PLACEHOLDER — specify retention periods or criteria for accounts, workspace records, Google data and tokens, audit/security logs, support records, and historical applications. Add the verified erasure request process, processing time, backup expiry, and statutory retention exceptions. Do not treat account closure or disconnection as complete deletion.
Your privacy rights
PLACEHOLDER — add applicable access, correction, erasure, restriction, portability, objection, and consent-withdrawal rights; explain how to contact the responsible controller, how requests are handled, and how to complain to the competent supervisory authority.
Website measurement and cookies
These website pages do not load advertising or analytics scripts, and do not store marketing cookies. Hosting and network providers may process technical request data to deliver the website. This website statement does not describe application session cookies.
PLACEHOLDER — confirm hosting request-log retention and the application's essential session cookies and any other cookie or analytics processing.
Changes to this notice
PLACEHOLDER — confirm the effective date, notice and consent process for changes, and the final privacy contact before this draft becomes the published policy.
See also the Terms of Service draft.