Privacy policy

1. Sign-in and your profile

Sign in with Google and add your name, company, and currency to create a business profile. Microsoft sign-in is being configured. Supabase provides authentication and stores the profile. We receive your provider account identifier, email address, and basic profile information, such as your name. Your provider handles its password and verification prompts; Yardwise-Lanscaping does not ask for your Google or Microsoft password.

Account sign-in does not authorize access to your inbox, contacts, calendar, or Google Drive. Apple sign-in is not currently enabled. Session information is stored in your browser for this tab so you can use the app; signing out clears the app session in that tab.

2. Saved workspace information

Supabase hosts your business profile, estimates, customer contact details, project descriptions, amounts, statuses, notes, follow-up dates, and saved email draft subjects and bodies. We use these records to provide the features you request. The app enforces account-level access so users cannot use the app to access each other's workspaces.

Netlify hosts the website and application files. Netlify and Supabase process technical information such as IP addresses, request information, and security logs to provide their services. See Netlify's privacy policy and Supabase's privacy policy. We have not added advertising trackers or third-party analytics.

The account owner operating Yardwise-Lanscaping has administrative access to its hosting and database systems for maintenance and support. Do not put passwords, payment card details, or unrelated sensitive personal information into estimate notes or drafts.

3. Email drafts and sending

The online workspace saves follow-up drafts. You may separately connect Gmail for sending directly from this website. Google asks for the send-only gmail.send permission and basic identity details to confirm the sending address. This permission does not read your inbox, contacts, calendar, or Google Drive. Gmail sending is currently limited to approved test accounts while Google review is pending.

Google's authorization library loads from Google when you choose to connect Gmail. A short-lived access token remains in this page's memory; it is not saved in browser storage or sent to Netlify or Supabase. Closing the page or signing out clears that token. You may need to reconnect when it expires. Disconnect clears this page's token; revoke Google's grant separately through your Google account connections.

Each website send requires your review and confirmation of Gmail, the exact sender, recipient, subject, and message. The page sends the email directly to Google's Gmail API using your token. Google processes the content and sends it from your account. Supabase stores a send reservation, the reviewed recipient/subject/body/sender, follow-up date, result, and provider message reference to keep your records and reduce duplicate-send risk. Provider acceptance is not a guarantee of delivery. If a connection fails with an uncertain outcome, the saved draft stays blocked from retry until the result is resolved; check Gmail's Sent folder and contact support.

You can still copy a draft or choose Open email app to pass its recipient, subject, and body to your device's default mail application. Your device chooses the app and account; review both there. Apple Mail may use Gmail, Outlook, iCloud, or another provider. For an email sent externally, Mark as sent records your confirmation and updates the follow-up date. No messages are sent automatically. Outlook website sending and inbox reply reading are not enabled.

4. Earlier local test versions

Earlier Windows test versions stored accounts and workspace records in a local SQLite database. Those existing records have not been automatically uploaded to this online service. Local provider tokens, if configured, were encrypted with Windows DPAPI. The local database's estimate and draft content was not encrypted by the app.

Those test versions could request Gmail's gmail.modify permission or Microsoft mail read/write and send permissions. Their mailbox features used selected drafts and linked conversations, with explicit confirmation before sending. Retrieved conversations were not saved in the local database. Existing provider grants can be revoked through your provider's app-permissions page.

5. Google API Limited Use

Yardwise-Lanscaping's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

We do not sell Google or Microsoft account or mailbox data, use it for advertising, or use it to train AI models. Information is used to provide the features you request.

6. Retention, export, and deletion

Workspace records remain until you delete them or request account deletion. You can delete unused estimates and drafts in the app and export your estimates as CSV. Records with pending, uncertain, or submitted website sends are protected from changes or deletion to preserve send history; contact support for verified account deletion. Deleting an estimate also deletes its saved drafts. Exports and copies you send through an email provider remain under your control or that provider's retention rules.

For deletion of your online profile and remaining workspace records, contact support from the email associated with your account. We may need to verify ownership before acting. Service logs and provider backups may remain for their applicable retention periods; deletion from the active workspace does not promise immediate removal from every backup.

To revoke provider permission, use Google account connections, Microsoft app permissions, or your organization's account settings. Revoking a sign-in grant does not itself delete workspace records. For earlier local versions, files and backups on your computer remain under your control.

7. Availability and changes

The app uses free hosting plans with usage limits. Availability is not guaranteed; keep CSV copies of important estimate records. No subscription or payment details are required from app users.

Google mailbox verification remains incomplete. This policy does not imply review or endorsement by Google, Microsoft, or Apple. If data practices or requested permissions change, we will update this policy and provide any required disclosure and consent.

8. Contact

For privacy questions, support, or account deletion, email fedorradzik@gmail.com. Support emails pass through the email services used by you and the support recipient. Share only what is needed; never send passwords or authorization codes.