Privacy policy

Who is responsible

Seller: Raja Kumar. Business contact address: Whitefield, Bengaluru 560066, India. Website: https://gridynotch.dev. Support and privacy contact: [email protected].

This policy covers GridyNotch and its direct purchase website. For privacy requests, contact the seller using the contact page.

Window and project data stays local

Project names, window titles and assignments, layout settings and recovery information are stored locally on your Mac. GridyNotch does not send this window-management data to the licensing service. Trackpad gesture handling occurs in memory and is not uploaded or saved as an input history. Accessibility permission lets the app manage windows; it does not authorize uploading your window contents.

Purchase and licensing data

For a purchase, we process your email address, selected pack, accepted terms version, amount/currency, order and payment references, payment status, delivery status, and refund/support records. For activation, we process a hash of the submitted license key, a device-generated public key or installation credential, activation identifier, status and timestamps. These identify a licensed installation; they are not window titles, files or document contents.

The app stores its private installation credentials and signed activation receipt in macOS Keychain. Activation sends the entered license key over HTTPS so it can be checked; raw license keys must not be included in application logs. License lookup uses hashed keys. An encrypted fulfillment copy of the key pack is retained for purchase recovery, delivery retries and support-assisted replacement.

Payments and service providers

Razorpay processes payment details and may collect billing, contact, fraud-prevention and payment-instrument information under its own privacy policy. We do not receive or store your full card number or card security code. Supabase hosts the licensing database and API. Cloudflare hosts downloads and may provide website and security services. A transactional email provider delivers purchase messages; the launch configuration uses Resend.

These providers process the data needed for their role. Depending on provider regions and networks, processing may occur outside your country. They may record technical information such as IP addresses, request times and user-agent information for delivery, security and service operation.

Purpose and browser storage

We use purchase and activation information to fulfill your purchase, enforce one-Mac activation, deliver keys, prevent fraud and abuse, handle refunds and support, and meet applicable accounting or legal duties. We do not sell your personal data or use window data for advertising.

The website stores a theme preference in localStorage. During checkout, it may store private order access in sessionStorage for that browser tab. Keys are shown only on the protected order-status view and in delivery email; no analytics event should contain keys or order-access tokens. Razorpay may use its own storage when you open checkout. No payment code is loaded merely to explore the demo.

Retention and your choices

Purchase, payment and refund records are retained for applicable accounting, tax, fraud-prevention and dispute obligations. Activation records are retained while needed to support the license. The encrypted key-pack copy is retained while needed to deliver and support your license; it is not stored as plaintext. You may request deletion, subject to legal retention and purchase-verification needs. Technical logs are kept only as needed for security and operations. Backups can retain deleted records until their normal retention cycle ends.

You may request access, correction or deletion of your personal data and withdraw any optional consent through the contact page. We may need to verify ownership and retain records required by law or necessary to resolve an open payment dispute. Deleting local app settings does not automatically delete purchase records. You can revoke Accessibility access or uninstall the app at any time.

Security and changes

We use HTTPS, restricted backend access, hashed license lookup and signed activation receipts. No system can guarantee absolute security. Do not send card data or credentials to support. Material changes to this policy will be dated on this page; new purposes requiring consent will not be silently added.