Privacy Policy

1. Our Roles in Data Processing

Because Strelve serves both trade businesses and their customers, we operate in two distinct capacities:

• As a Data Controller: When we collect and process the personal and business information of our direct clients (trade businesses using Strelve).
• As a Data Processor: When we process and store the information of homeowners/leads who submit enquiries on behalf of our clients.

2. Information We Collect

We collect only what Strelve needs to run your lead pipeline, send notifications, and support you. Nothing more.

• Name, email, role, and profile avatar.
• Business details: industry, website, contact email, contact phone, service country and city, and branding colours (logo, primary, secondary, accent).
• Estimate form questions and answer choices configured in your account. We may use generalised versions of these to create and improve reusable estimate form templates, as described in our Terms of Service. We exclude your actual prices and pricing rules, and do not use individual leads' submitted answers for this purpose.

• First and last name, email, phone, address, city.
• If someone enters their name and phone number on an estimate form but leaves before submitting it, we may save those details and the answers they have entered so the trade business can review the incomplete estimate.
• If an estimate form uses address autocomplete, the typed search text and selected place details are sent to Google Maps Platform (Places API) to return matching address information.
• Enquiry answers and job timeline.
• Priority score, pricing estimates, and activity log.
• Email reply body text and HTML are stored for up to 12 months after receipt and then automatically purged.

• Stripe customer ID and subscription ID.
• We never store full card details. Card data is handled directly by Stripe.

• Admin command text and chat identifiers are retained for up to 12 months for security, support, and audit purposes.
• The admin bot accepts commands and confirmation actions from allowlisted administrator chats. It does not process customer Telegram messages.

• Images and other allowed files you or your leads upload are checked for file type and size, processed locally where needed, and stored in Supabase Storage.
• We do not currently send file attachments to OpenAI Vision or store AI image scan results.
• Raw files are access-controlled to your client workspace.

• Vercel Analytics collects page views, Core Web Vitals, browser/device information, and country/city.
• PostHog records public website page views, campaign source tags, and defined enquiry events. Estimate form submissions use generated lead IDs and business context such as category and source. We do not send lead names, emails, phone numbers, or answers to PostHog. Operator accounts are identified by user ID and role for usage analytics. Public website session recordings are disabled.
• No personally identifiable information is transmitted to Vercel Analytics.
• Estimate form funnel events are stored in our database with a visitor ID, form event and step details, campaign and referrer information, and a generated lead ID when an enquiry is submitted. A scheduled cleanup deletes event records older than 720 days.
• Signup setup events are stored in our database with a random attempt ID, the plan selected, signup step timestamps, and completion status for required Professional business profile questions. We do not store the answers, typed form text, email address, or password in these events. Events for attempts that do not reach account creation are deleted after 180 days; events linked to an account are retained with that account's records.

• Sentry captures error reports with stack traces and breadcrumbs so we can fix bugs.
• User email and IP address are explicitly stripped from every Sentry event before transmission.

• Captured ephemerally by Upstash Redis for rate limiting — held only for the rate-limit window, then discarded.
• Captured permanently in admin audit logs as part of the audit trail for regulated actions (billing changes, data purges, access grants).

• If an approved third-party integration is enabled for your account, OAuth access and refresh tokens are encrypted at rest.
• Tokens are used only for the approved lead handoff or sync you have connected on your behalf.

• Customer first/last name, email, phone, address, lead category, and value — retained so Strelve can send service reminders and process maintenance-contract invoicing on your behalf.

3. How We Use the Information

• To provide, maintain, and improve the Strelve Service.
• To create and improve reusable estimate form templates from generalised form questions and answer choices. We do not use your actual prices, pricing rules, margins, or pricing calculations, or individual leads' submitted answers, for this purpose.
• To process subscription payments and send billing-related emails.
• To send service updates and (where you have not opted out) product announcements.

• We process lead data strictly to provide the Service to you.
• We do not sell, rent, or mine lead data for our own marketing, and we do not share it with your competitors.
• You remain the Data Controller for your leads' information.

4. How We Secure Information

We apply industry-standard security controls, including Row-Level Security (RLS) policies within our database so that one client cannot read another client's data. Secrets and OAuth tokens are encrypted at rest. Card payments are handled directly by Stripe — we never see or store full card numbers. No internet-based service can guarantee 100% security, and we cannot guarantee absolute immunity from unauthorised access.

5. Third-Party Processors

We share data only with trusted service providers required to run the Service. Each processor handles only the data they need to deliver their slice of the Service:

• Stripe — payment processing and subscription billing; receives customer name, email, and billing address.
• Sentry — error monitoring; user PII (email, IP) is stripped before transmission. We maintain a Data Processing Agreement with Sentry — see their DPA.
• Vercel — application hosting and Vercel Analytics (aggregate traffic data only, no PII).
• PostHog — product analytics for aggregate funnel and usage measurement. Lead submission events use generated lead IDs, not lead contact details. Operator accounts are identified by user ID and role.
• Supabase — primary database, authentication, and file storage (raw attachments).
• Upstash — ephemeral Redis used for rate limiting.
• Telegram — delivery of admin alerts and commands from allowlisted administrator chats.
• Resend — outbound email delivery for all lead and operator emails. Resend receives the recipient name, email address, and message content needed to deliver each email.
• Google Ads — conversion tracking for paid acquisition campaigns. Receives anonymised conversion events (page views and form submissions) via the Google Ads tag. No lead PII is transmitted to Google.
• Google Maps Platform (Places API) — receives address search text and selected place information when someone uses address autocomplete in an estimate form, and returns matching address details.

We do not sell your data to any party, and we do not use lead data to train public AI models.

6. Data Retention & Deletion

• Lead and client data: We do not deactivate accounts or automatically delete their records solely because of inactivity. Subscription cancellation does not automatically delete client records, leads, soft-deleted leads, uploaded lead files, completed jobs, maintenance contracts, CRM tokens, API keys, or webhooks. There is no automatic deletion date after cancellation. We retain this data so the account remains available. Account owners can request deletion using the contact details under Your Rights.
• Demo lead data: Deleted within 30 minutes of submission. Demo submissions never persist beyond the live sandbox session.
• Incomplete estimates: Contact details and saved answers are deleted 30 days after they are first saved. Later answer updates do not restart that period. If a trade business has more than 100 active incomplete estimates, we delete the oldest entries and keep the 100 newest across all its forms.
• Admin Telegram messages: Command text and chat identifiers are retained for up to 12 months for security, support, and audit purposes.
• Email reply bodies: Purged 12 months after receipt.
• IP addresses in audit logs: Retained permanently as part of the regulated audit trail.
• Analytics data: Governed by Vercel and PostHog retention settings. Lead submission analytics use generated lead IDs, not lead contact details.
• Soft-deleted leads: Kept while the account is available so accidental deletions can be recovered. Subscription cancellation does not automatically remove the account data.

7. Your Rights

Under the New Zealand Privacy Act 2020 and the Australian Privacy Act 1988, you have the right to:

• Access the personal information we hold about you.
• Correct any inaccurate or out-of-date information.
• Request deletion (erasure) of your personal information.

If you are a trade business client, email us to request access to the personal information we hold about you: support@strelve.co.nz. We aim to respond to access requests within 20 working days in New Zealand or 30 calendar days in Australia.

If you are a homeowner/lead, please contact the trade business that collected your information (the Data Controller). We will assist them in fulfilling your request.

8. Changes to this Policy

We may update this Privacy Policy from time to time. We will notify you of any significant changes by posting the new policy on this page or via email.

9. Contact Us

For any privacy-related queries, email support@strelve.co.nz or .