This Privacy Policy explains how Theodoros Pitsikos (independent developer, trading as Ariavel) ("we", "us", "Ariavel") processes information when a monday.com account ("Customer") installs and uses Ariavel Seal (the "App"), a monday.com app that lets a Customer choose protected fields on a board, lets a permitted person confirm the exact values of those fields on an approved item ("Confirm & Seal"), and then shows whether the current values still match that confirmed state.
The App is not an electronic signature, a legal attestation or a compliance certification, and it does not lock items or prevent edits in monday.com. Ariavel Seal is an independent app, not developed or endorsed by monday.com. This policy applies to every installation of the App.
1. Roles under data protection law
- The Customer is the controller of the board data the App reads and of the protected values its users confirm. The Customer decides which boards, fields and approvers to use.
- Ariavel is a processor acting for the Customer for that data. We process it only to provide the App, following the Customer's instructions and our Terms of Service.
- For the limited technical data needed to run, secure and bill the App (for example the monday.com account and user IDs used for sign-in, and installation lifecycle records), Ariavel is an independent controller.
People whose personal data appears in a protected field who want to exercise their rights should contact the Customer (the controller) first. We will help the Customer respond.
2. What data the App stores
Customer data is separated by monday.com account (tenant). Seal also keeps application and connection records to control access to stored data. These records do not establish a new native installation after reinstall or completed deletion after uninstall. The current Seal backend and Document DB run in monday code's EU region; this is not a statement that all monday.com services process data only in the EU. Accounts outside the EU are served by the same EU backend.
| Category | Examples | Where stored |
|---|---|---|
| monday.com identifiers | monday account ID, the user ID of the person who performs an action, and board, item and column IDs. They come from monday.com session tokens and the monday.com API. | monday code Document DB |
| Seal policies | The approval prerequisite (status column and value), the protected field IDs and the permitted approvers' user IDs. Each saved change creates a new policy version; earlier versions are kept as history. | monday code Document DB |
| Seal records and history | Seal status (for example NOT SEALED, VERIFICATION REQUIRED or SEAL BROKEN), who confirmed and when, confirmation receipts, checks and the link to a successor seal. | monday code Document DB |
| Fingerprints | A SHA-256 checksum computed from the confirmed protected values in a fixed, deterministic format. It is used to compare states. | monday code Document DB |
| Confirmed protected values and differences | The exact values of the protected fields at confirmation, and the field-by-field difference recorded when a seal breaks, so the App can show what changed. | monday Secure Storage (encrypted by monday.com). Details are readable for up to 30 days; expiry does not establish physical deletion (see section 7). They are not stored in Document DB. |
| Application, connection and lifecycle records | Account and user IDs, Seal application and connection identifiers, received lifecycle notifications (such as install and uninstall) and processing times, and the progress of uninstall deletion. | monday code Document DB |
| Ariavel support records | Records Ariavel staff create about your account: extra capacity given as a service and its history, an internal label, internal notes, an internal complimentary flag, any suspension and its reason, any in-app announcement for your account, any feature setting for your account, and a log of what staff did and when. They contain no board content or protected values. | monday code Document DB |
| OAuth credentials | Access and refresh credentials from the account admin who authorized the App for the account, and from any earlier per-user connection made during testing. | monday Secure Storage, bound to the account and connection. Raw credentials are not exposed in the browser or in diagnostic logs, and are not stored in Document DB. |
| Workflow records | Review requests, workflow subscription identifiers, related account, user, board and item IDs, and delivery state. Trigger callback URLs are needed to send Seal results to the configured monday.com workflow. | Workflow metadata in monday code Document DB; callback URLs in monday Secure Storage |
Protected values can contain personal data if the Customer chooses such fields (for example a name typed into a text field). We recommend protecting only the fields an approval actually depends on.
How the App reads monday.com data. An account admin installs the App and authorizes it once. The App then reads monday.com data with that admin's authorization; other users do not connect their own accounts. The identity of the person using the App always comes from the session token monday.com issues for that person, and the App checks that person's own board and item access before it shows anything, denying access it cannot determine. Protected values and differences are shown only to account admins and the approvers named in the board's policy. Other members, viewers and guests see the Seal status and the names of changed protected columns, not the values.
The authorization requests these monday.com permissions: me:read to identify the authorizing user; boards:read to read the boards and items used with Seal, protected values and relevant board activity logs; users:read, teams:read and workspaces:read to check whether the person using the App may see a board or item (user type, board, team and workspace membership). Checks read current values from monday.com when the App or a configured workflow performs a check; continuous background monitoring is not provided. The App does not request permission to write to boards, does not change item values and does not change the monday.com Approved status. The business values retained for comparisons and differences are the protected fields chosen in a policy; identifiers and operational records are listed above.
What Ariavel staff can see. Currently, only Ariavel's owner is authorized to sign in to the private support console. To support your account the owner can see your monday account ID, your subscription details from monday.com (plan, status, price, renewal), counts of boards, policies, items and Seals, board IDs, install and lifecycle events and the Ariavel support records above. The console does not show protected values, differences, fingerprints, policy contents, board or item names, or anything on your boards. The owner cannot use your authorization through the console. Each staff action is logged. Exports contain the same records and are used only to support your account or answer a data request.
The App uses no analytics, advertising or tracking SDKs and sets no tracking cookies. The current Seal connection flow does not set a Seal authorization cookie. monday.com's own sign-in and authorization pages are separate services governed by monday.com's policies.
3. What a seal records
A seal is a record that a permitted person confirmed specific protected values on a specific item. The App compares the current values with that confirmed state by an exact, deterministic comparison. monday.com does not document complete change-history coverage, so a confirmed Seal normally shows Verification Required rather than a positive result; the App never shows a positive result based on elapsed time. It also shows Verification Required when monday.com data is unavailable or incomplete.
A detected later change to a protected value breaks the Seal. Restoring the previous value does not restore a recorded broken Seal; a permitted person must review and reconfirm it. Seal does not guarantee detection of every temporary change that is absent from the evidence monday.com returns.
AI
In versions that offer optional AI explanations, a permitted user can request a short explanation alongside Exact Diff for a broken Seal. The App checks the user’s access and uses the installing account’s ai:consume authorization and credits from that account’s monday AI balance. The request includes the selected changed fields’ identifiers, labels and types, their confirmed and detected values, the observation time and, where available, a unit or numeric change. Selected values may contain personal data.
monday.com processes the request through its AI gateway and may route it to its model providers. See monday.com’s AI gateway documentation for how it provides that service. Ariavel Seal displays the returned explanation and does not store the AI prompt or response or use either to train models. The App determines Seal integrity separately. Only a permitted person can confirm or reapprove a Seal.
4. Purposes and legal bases
- Providing the App's seal features to the Customer. Legal basis: our contract with the Customer. For personal data in protected fields, the Customer's legitimate interest in keeping a clear record of approved values.
- Authentication, tenant separation, security and abuse prevention. Legal basis: legitimate interests.
- Handling support requests you send us. Legal basis: legitimate interests or contract.
- Meeting legal obligations.
We do not sell personal data, use it for advertising, or use Customer data to train machine-learning models.
5. Hosting and sub-processors
| Sub-processor | Purpose | Location |
|---|---|---|
| monday.com Ltd. | Hosts the App's backend and interface, Document DB, Secure Storage and platform logs; provides monday.com authentication, processes user-requested explanations through its AI gateway when enabled, and provides Marketplace billing when activated | Current Seal backend and Document DB: EU region. Locations for the other monday.com services are not established by the backend's region. |
| Google Firebase infrastructure, via monday.com | Infrastructure underlying monday code Document DB, as described by monday.com | Current Seal Document DB: EU region. This does not establish the location of every service used by monday.com. |
Our public website, help and legal pages are hosted by OVHcloud. These static pages do not receive Customer board data or protected values from the App. Emails sent to support@ariavel.eu are handled by our email provider, OVHcloud. We will update this list before we add a new sub-processor.
6. Security
Board and item requests from the App's interface are authenticated with session tokens issued by monday.com and verified by the App, and the account and user come from that verified token, never from browser input. Board and item data access, policy changes and human confirmations are checked against the user's own monday.com access and Seal's role rules; access that cannot be determined is denied. Credentials and confirmed protected values are kept in monday Secure Storage. Data is encrypted in transit (HTTPS) and encrypted at rest by the hosting platform.
The current backend writes technical diagnostic logs, such as the route family, processing phase and outcome. Application diagnostics are designed not to contain protected values, board content, access tokens or session tokens. These logs are kept in monday code platform logging for the period the platform sets; we do not keep a separate copy.
7. Retention and deletion
- Seal policies, seal records, history and fingerprints are stored while the App is installed, to provide the App.
- Confirmed protected values and recorded differences are readable from monday Secure Storage for up to 30 days after they are recorded. After expiry, the App refuses reads and no longer shows those details. This read limit does not establish when the stored payload is physically deleted; it is deleted at the latest by the uninstall deletion below.
- Uninstall and deletion. When monday.com notifies us that the App was uninstalled from an account, the App deletes that account's Seal policies, seal records, history, fingerprints, confirmed protected values, differences, workflow records, connection records and stored monday.com credentials, and retires the account's authorization. We delete this end-user data and metadata within 10 days of uninstall, unless the Customer has given express written consent to keep it longer. This deletion process is implemented but has not yet been verified with a real uninstall on monday.com; we will update this policy when it has been. If you uninstall and want confirmation that your account's data was deleted, email support@ariavel.eu; we will check and complete the deletion within 10 days.
- Ariavel support records and the staff log entries about your account are deleted with the rest of your account's Seal records after uninstall. A reinstall starts without them.
- To process uninstall and reinstall in the right order, the App keeps a minimal record that an account was uninstalled and that deletion ran (account ID, times and counts of deleted records, with no board content or protected values).
- Data on the Customer's own monday.com boards stays under the Customer's control in monday.com. The App does not delete it.
8. Your rights
Depending on where you are (including under the GDPR and UK GDPR), you may have the right to access, correct or erase your personal data, to restrict or object to its processing, to data portability, and to complain to a supervisory authority. Because seal records are kept for the Customer, please contact your account administrator first. You can also email us at support@ariavel.eu; we will verify the account, help the Customer respond and tell you what we can verify. We respond within one month.
9. Children
The App is a business tool and is not intended for children under 16.
10. Changes
We may update this policy. We will announce material changes in the App or on this page and update the effective date.
11. Contact
Theodoros Pitsikos (independent developer, trading as Ariavel), Greece. Email: support@ariavel.eu. For data protection requests, use this email address. Customers who need a Data Processing Agreement can contact us at support@ariavel.eu to discuss one.