Privacy Policy
Effective date: 19 November 2026This policy describes how Reconcile (the “Service”), an open-source data reconciliation workspace and Model Context Protocol (MCP) server maintained by Doğukan Demirci, handles information when you use the hosted website or MCP endpoint.
1. Information processed
The Service does not require an account and does not intentionally collect a user profile. To perform a comparison, the Service may temporarily process files and records you submit (including CSV/XLSX contents), selected field mappings, comparison options, REST URLs and response data, PostgreSQL connection details, and MCP request parameters. These inputs may contain personal or confidential information if you choose to include it.
Do not submit passwords, access tokens, payment-card data, health information, government identifiers, or other sensitive information unless you have independently assessed that doing so is lawful and appropriate. Use a read-only database account and only connect to sources you are authorized to access.
2. Purposes and processing
Submitted information is processed only to inspect supported sources, reconcile records, calculate differences and operation estimates, and return the requested result. The application code is designed not to write submitted source contents, credentials, or results to an application database, file store, or persistent cache. Processing takes place in browser memory and server request/process memory for the duration of the operation. This is not a guarantee of forensic memory erasure.
3. Recipients and service providers
Requests to the hosted Service are handled by Vercel infrastructure. Network providers and other infrastructure providers may process connection metadata as part of delivering and protecting their services. The public source repository and GitHub are not used by the running application to receive your comparison data. The Service does not intentionally send submitted data to advertising networks or external AI model providers.
Infrastructure providers may create security, operational, or request logs under their own policies and account settings. The Service operator does not control or independently verify all provider-side logging, access, location, or retention practices. See Vercel documentation and applicable provider terms for current details.
4. Retention and deletion
The application has no user account, history feature, or application-level persistent storage for submitted datasets. Temporary request data is used to complete the operation and is not intentionally retained by the application after processing. Browser state ends when the page is closed or reloaded. Provider-side operational logs may be retained separately according to the provider's current policies; the Service cannot delete or guarantee the retention period of those records.
If you believe personal information was included in a provider log, contact the relevant provider through its privacy process. For a security or privacy concern relating to this project, use the private vulnerability reporting option in the repository's GitHub Security tab. Do not post personal data or credentials in a public issue.
5. Security and limitations
The project applies input validation, request and file size limits, restricted network-source controls, and other safeguards described in its Security Policy. The hosted public MCP endpoint does not currently require user accounts. No internet service can promise absolute security. Avoid uploading data whose sensitivity or legal requirements you have not assessed.
6. Your choices and responsibilities
You choose what information to submit and may stop using the Service at any time. Do not submit data unless you have the rights and legal basis to do so. If you are using the Service for an organization, you are responsible for your organization's instructions, notices, permissions, and applicable privacy obligations.
7. Changes and contact
This policy may be updated when the Service, its infrastructure, or applicable requirements change. The effective date above will be revised when material changes are made. For support, use GitHub Issues. For sensitive security reports, use the private reporting route linked above.