CutPlan
YOUR DATA, YOUR CHOICES

Privacy policy

How the website, app and API use data to plan your cuts and maintain your account.

1. Controller and contact

CutPlannerMDF is responsible for processing data for CutPlan. For privacy questions and requests, contact hello@cutplannermdf.com. This policy covers the website, app and API. Stores, payment providers, advertising services and external websites also have their own policies.

2. Data and purposes

You can calculate without an account; calculation happens on your device. Cloud storage, API imports and PDF generation send the necessary data to the server.

  • Account: email, internal identifier, acceptance of terms, dates, protected login codes and sessions, for authentication and security.
  • Projects: names, dimensions, quantities, materials, grain, margins, kerf, costs, currency and results, associated with your account when saved to the cloud.
  • Files: CSV import data and plans sent for PDF validation, access checks and quota control. Avoid adding other people’s personal data.
  • Subscriptions: account ID, product, purchase source, status, validity and transaction events, for Pro access, restoration and quotas. We do not receive full card numbers or security codes.
  • Local data: drafts, assemblies, language, units, preferences and consent choices. Not everything is synchronized.
  • Operation: connections include IP and HTTP information. The API uses protected IP/email summaries for rate limits; application error logs record request IDs and error classes. Hosting may keep its own technical logs.
  • Support: your email and message, to respond to your request.

The planner does not need camera, microphone, contacts or precise location. File selection and sharing depend on your actions and system permissions.

3. Grounds and limits

Necessary data supports the service and contract, including login, saved projects and subscriptions. Security and abuse prevention may rely on legitimate interests, subject to necessity, proportionality and your rights. Legal records and valid authority requests rely on legal obligations or the exercise of rights as applicable.

Personalized advertising and optional analytics require separate consent. Accepting terms does not replace these choices. Withdrawal applies to future processing without invalidating earlier lawful processing.

4. Cookies, analytics and advertising

Web login uses an HttpOnly session cookie lasting up to 30 days and revocable earlier. Native tokens use secure system storage. Drafts and preferences use local storage; deleting it may remove drafts or end your session.

With optional app analytics enabled and accepted, the API records daily aggregated event counts with platform, language, plan, categorized source and version, without account ID, email or project content. Manage the choice in Account where enabled; network transport still involves security connection data.

Website Google Analytics 4: if configured and you allow analytics, Google may store cookies and receive browsing, device and connection data. We measure page views and store clicks; a click does not prove installation. Our events exclude email, project content, dimensions, URL parameters and referrer. Advertising features are disabled. No Google tag loads before permission.

Use Analytics preferences in the footer to change your choice. Declining keeps the site working, stops future collection and removes accessible first-party _ga cookies on this domain; it does not delete data already received by Google. Language and consent choices use local storage. This privacy page does not load the analytics tag, even after earlier consent.

Free iOS/Android versions may use Google AdMob and UMP when advertising is enabled. Personalized ads require your choice, applicable regional permissions and iOS ATT authorization. Pro shows no ads or sponsorships. Google services may process IP (including approximate location), permitted device/account/advertising identifiers, ad interactions and diagnostics for delivery, measurement and fraud prevention. Planner code does not directly read or store advertising IDs; the SDK may process them with permission.

In Account, use ad privacy controls to decline tracking or review consent; iOS tracking can also be changed in system settings. Declining keeps the app usable and uses available own sponsorships without cross-app/site tracking, pixels or identifiers in links. Sponsor websites have their own policies. Advertising and analytics consent are separate.

5. Sharing and transfers

Hosting, database and email providers operate infrastructure and deliver login codes. Depending on platform and billing setup, RevenueCat, Apple, Google Play and Stripe process purchases, verify subscriptions, restore access and prevent fraud. RevenueCat receives the internal account ID, not project content for selling or restoring Pro. Google Analytics receives authorized website analytics; AdMob and consent-listed partners process advertising as described above.

You choose recipients when sharing exported files. Information may be disclosed for valid legal requirements or protection of rights within applicable limits. We do not sell project content. Providers may process data outside Brazil, subject to applicable legal safeguards and transfer mechanisms; countries and retention depend on contracted services.

Provider policies: RevenueCat, Apple, Google, Stripe.

6. Storage and security

Controls include account/project access checks, server authorization and quotas, protected tokens and codes, and rate limits. Published services must use HTTPS. Application logs exclude tokens, login codes, request bodies and project content.

This policy page loads no trackers, external fonts or analytics tools. Local scripts handle language and navigation. Hosting still processes the request. No safeguard eliminates all risk: protect your device and exports. Relevant incidents are handled and communicated when required by law.

7. Retention and deletion

Accounts and saved projects are kept as necessary to provide your account and contracted features until applicable deletion. Login codes expire in 10 minutes; sessions in up to 30 days. Physical removal of expired records may happen later. Technical records, backups and providers follow operational cycles and legal duties; contact us for effective retention periods.

In Account → Delete my account, authenticate again and enter DELETE. Deletion removes the account, projects, sessions, access and linked counters in the active database. Billing events kept for processing and deduplication may retain the former internal ID; aggregated usage counts cannot be individually removed.

Deletion does not automatically remove local copies, exports, backups or provider records. Remove local app/site data in system/browser settings after keeping any needed copies. Records required by law or legal defense may be retained for those purposes with restricted access.

Deleting an account does not cancel subscription renewal. Cancel through Apple, Google Play or web billing, depending on purchase source. If you cannot sign in, contact hello@cutplannermdf.com; proportionate identity verification may be needed.

8. Your rights and choices

Under applicable law, including Brazil’s LGPD, you may request confirmation and access, correction, sharing information, anonymization, blocking or deletion of unnecessary or unlawfully processed data, portability where applicable, objection, withdrawal of consent, information about refusing consent and review of exclusively automated decisions affecting your interests where they exist.

Account data export downloads your profile and projects as JSON. It does not replace your right to request access to other personal data. You can delete individual projects and end sessions. Send other requests to hello@cutplannermdf.com. We may verify identity, reply within applicable legal deadlines and explain limitations. Complaints may be filed with Brazil’s ANPD.

9. Children and teenagers

CutPlan is designed for woodworking planning and is not directed at children. We do not intentionally request children’s data for advertising. Guardians who identify inappropriate use or data submission should contact us for assessment and appropriate action, respecting best interests and applicable legal requirements.

10. Policy updates

We may update this policy for changes in features, providers or legal obligations. The version and date appear above. Material changes are communicated through appropriate channels; new consent is requested before new processing when required. Privacy contact: hello@cutplannermdf.com.

Public document. No account required.