Minimal data, bounded purpose.

Who is responsible

Board Blueprint Sync is provided by Taha Fırat, an Independent Developer acting as an individual. “Independent Developer” is a public descriptor, not a registered company name. This notice covers the app and https://boardblueprintsync.com.

What the app processes

The monday-hosted product reads board structure needed to compare classic boards: board identity, hierarchy, access level, groups, column descriptions/settings and revisions, and group metadata. It does not query board items or updates.

• boards:read reads board structure and metadata for Reference/target comparisons and structural drift detection, including permission/schema preflight and post-write verification.
• boards:write is used only after explicit review and confirmation to create safely missing Text or Status columns on one target board. No automatic deletion, destructive schema overwrite, existing-column modification, or group/item write is supported.

A short-lived monday session token is sent over HTTPS to a stateless entitlement endpoint. The endpoint verifies the signature with a server-only client secret and returns only trial, paid, expired, or verification-error state plus the verified account identifier where required. It does not persist tokens, account identifiers, subscription payloads, board data, plans, or results.

Access checks transiently process the monday account ID, user ID and signed app subscription fields: plan ID, trial status, billing period, remaining days, renewal date and, when supplied, pricing version and maximum units. The browser also reads account context, monetization support and current app subscription information before Apply. These checks determine whether access is allowed; they do not collect payment card details. An unsupported state originates in the client-side monetization-support check, not the entitlement endpoint response.

Storage and tracking

Scan, selection, preview, entitlement, and result state remain in browser memory for the active session. The app has no customer-board database, analytics, telemetry, advertising tracker, or application cookie. The public-site package is static and adds no analytics or advertising scripts. This does not describe monday's or Cloudflare's separate platform processing or imply that their systems keep no logs.

Approved board changes

Explicitly confirmed additions are sent directly from the app to monday and become monday board data. They do not pass through the entitlement service. Closing or uninstalling the app does not undo those additions.

There is no durable application dataset or stored board OAuth token for an uninstall/deauthorization deletion job. Closing the app discards its in-memory session; subsequent requests require current valid access. Uninstall/deauthorization does not trigger a product deletion job for monday board data, provider logs or support correspondence. We do not promise instantaneous revocation of an already-loaded monday session.

Service providers and collection

monday.com supplies the hosted app surface, board APIs, seamless authentication and native subscription services. Cloudflare hosts the public site and stateless entitlement function and routes support email. HTTPS requests necessarily reach these providers. Infrastructure and email handling are distinct from the app's memory-only board state; provider processing may occur outside your country. No specific hosting region, transfer safeguard or provider retention period is asserted here.

Relevant services are monday.com and its HTTPS subdomains for platform APIs, context and subscriptions; auth.monday.com for installation; and https://ve3366badb743358d3d3e7894d6ada728.cdn2.monday.app for the current frontend. Cloudflare serves boardblueprintsync.com and its pages.dev deployment hostname. The stateless endpoint https://boardblueprintsync.com/api/entitlement verifies signed session access; no board schema or proposed operation is sent to it.

The app obtains structure and session information electronically through monday when you use it. You may separately provide your email address and message when requesting support. Access verification and requested workflows are processed to provide the service; necessary security and support handling protects that service, and legally required processing may apply. No unrelated marketing consent is inferred from use.

Support, retention and your requests

The entitlement handler does not use an application console logger and returns fixed sanitized errors. The controlled monday SDK warning patch emits a fixed warning without remote warning payloads. Safe diagnostic codes, request identifiers and operation outcomes may appear in the session UI; they are not a durable server audit log. Separate monday, Cloudflare and browser diagnostics may still occur. Raw tokens and remote payloads are not intentionally logged by the application.

No marketing or advertising email is planned initially. Necessary customer-requested support, service, security, billing/subscription and legally required communications may be sent. Support correspondence is separate from the entitlement service; its content is not covered by a claim of zero email retention. No fixed mailbox or provider-log retention period is represented as verified.

Contact the address below to ask about processing or to request access, correction or deletion, subject to applicable law and necessary identity verification. Where applicable, your rights include information about recipients, objection to qualifying automated decisions and redress. No automated identity or marketing profiling is part of this product. Requests concerning monday board data may also require your account administrator or monday. Never send tokens, credentials, private board contents or raw API payloads to support.

This notice will be revised when the described processing changes. Applicable notice requirements remain unaffected. No certification or qualified legal-counsel review is claimed.

Contact

Taha Fırat — privacy contact: support@boardblueprintsync.com. Cloudflare Email Routing is owner-configured; independent delivery verification is not recorded.