Skip to main content
SnagMate
How it worksPricing

Launching soon

Sign up to hear when SnagMate launches.

Privacy notice

Sign in

SnagMate Privacy Notice

How SnagMate collects, uses, shares, retains and protects personal information.

Effective date: 12 November 2026
Version: 1.7

This notice explains how Odin Tech Solutions (Pty) Ltd (registration number 2024/677836/07), providing the SnagMate construction snagging service ("Odin", "we", "us" or "our"), processes personal information under the Protection of Personal Information Act, 2013 ("POPIA"). It applies when you visit the SnagMate website, use an account or workspace, upload site records, receive communications, contact support, or otherwise use SnagMate.

1. Responsible party, operator roles and contact

Odin is the responsible party for SnagMate's website, account administration, billing, service communications, security, support and its own business records. A customer organisation may be the responsible party for personal information in its project workspace where it decides why and how that information is used. In that situation, Odin processes the information on that customer's behalf. Tech Local (Pty) Ltd provides development, hosting administration and technical support as an operator/data processor under Odin's instructions and applicable data-processing terms.

  • Responsible party and service provider: Odin Tech Solutions (Pty) Ltd
  • Registration number: 2024/677836/07
  • Business address: Nicol on Main Office Park, Block C, 2 Bruton Rd, Bryanston, Johannesburg 2196, South Africa
  • Telephone: +27 10 300 0942
  • Privacy contact: SnagMate privacy team
  • Privacy and PAIA email: hello@snagmate.com

If your request concerns information controlled by your employer, client, contractor company or another SnagMate customer, we may refer the request to that organisation or help it respond.

2. Personal information we collect

Depending on your role and how your organisation uses SnagMate, we may process:

  • Account and identity information: name, email address, company, role, profile, membership, invitation, authentication and account-status records.
  • Organisation, contractor and project and site information: organisation and contractor-company details, project and client names, site addresses, buildings, floors, units, rooms, trades, team rosters and assignments.
  • Inspection and workflow records: report details, snag descriptions, categories, status, responsibility, comments, dates, review decisions, sign-offs, reminder settings and activity history.
  • Site media and files: photos, annotations, project drawings, voice notes, transcripts, completion proof, report branding and generated client-ready reports.
  • Communications: invitations, reminders, notifications, feedback, support enquiries and related delivery records.
  • Launch and marketing preferences: email address, combined launch and newsletter subscription, consent wording/version and date, signup and unsubscribe status, and related provider and delivery records.
  • Billing information: subscription, invoice, entitlement and limited payment-status information where paid service features are enabled. Payment providers process payment credentials; SnagMate does not need your online-banking password or card PIN.
  • Technical and security information: IP address, browser or device details, access times, session, authentication, audit, error, security and abuse-prevention logs, and necessary browser or device storage.

Site photos, drawings, voice notes or descriptions can incidentally include information about workers, residents, visitors or other people. Users should capture only what is relevant to the inspection and avoid unnecessary identity, health or other sensitive details.

3. Why we process personal information

We process personal information for specific, lawful purposes, including to:

  • create, secure and administer accounts, organisations, contractor companies and role-based access;
  • create projects and reports, capture and route snags, collect evidence, manage review and sign-off, and generate reports;
  • transcribe a user-requested voice note and create a short draft snag title or description for human review;
  • send invitations, operational reminders, security messages and service communications;
  • send SnagMate launch news, newsletters, product updates and offers after explicit signup consent;
  • provide support, investigate feedback and improve service reliability;
  • manage subscriptions, billing and contractual entitlements where applicable;
  • prevent misuse, enforce permissions, investigate incidents and protect users and the service;
  • meet legal, accounting, tax, PAIA, POPIA and other applicable obligations; and
  • establish, exercise or defend legal rights.

Depending on the purpose, processing is justified by consent, concluding or performing an agreement, complying with law, protecting a legitimate interest, or another ground permitted by section 11 of POPIA. Consent is requested where it is the appropriate legal basis and may be withdrawn without affecting processing already carried out lawfully.

4. Required information, sources and customer content

Account details and role information are required to secure access and apply project boundaries. Project, location and workflow details are required when your organisation uses the corresponding feature. Camera, photo-library or microphone access is optional at device level, but a chosen photo or voice feature cannot operate without the relevant permission and content.

We collect information directly from users, from the organisation or contractor company that invites or administers them, from authorised workspace participants, from systems used to deliver the service, and automatically through necessary technical events. Users and customers are responsible for having the authority, notices and permissions needed to submit information about other people, record voice, photograph a site, upload drawings and share project records.

5. Account messages and direct marketing

The signup form offers one SnagMate email list for launch news, newsletters, product updates and offers. The required consent checkbox starts unchecked. Submitting the form records your consent and adds eligible addresses directly to the SnagMate newsletter audience. No email confirmation step is required. We send a brief signup acknowledgement. Signing up does not create a product account and does not subscribe you to Tech Local marketing.

SnagMate's protected newsletter records on Tech Local's website backend include your email, consent text and version, signup date, subscription and delivery status, provider IDs and unsubscribe history. Resend receives your email and newsletter preference to manage SnagMate's own audience, deliver the signup acknowledgement and send enabled newsletters.

Where email engagement tracking is enabled, Resend records when a message's tracking image loads and when a tracked link is opened. Tech Local uses aggregate open and click counts to report newsletter performance. Email software can load images or follow links automatically, so these events do not prove that someone read a message or completed a signup. This email reporting is separate from optional website and app analytics.

The signup acknowledgement and newsletters identify SnagMate as the sender and include the same Resend-hosted unsubscribe and preference link, which works without creating or signing into an account. You can also contact our privacy team to withdraw your permission. Unsubscribing stops both launch news and newsletters. We retain consent and suppression records to honour your choice and do not automatically resubscribe you. Supported mailbox unsubscribe controls can also stop marketing. The brief signup acknowledgement is a service receipt; it does not contain a separate promotional subscription or confirmation request.

Operational messages—such as verification, invitation, assignment, reminder, security, billing and workflow notices—are part of providing and protecting SnagMate. Preference controls may limit optional channels, but necessary account and security messages may still be sent.

Electronic direct marketing is sent only where POPIA and other applicable law permit it. Where consent is required, it will be requested explicitly and will not be preselected. Marketing messages will identify the sender and provide a free, reasonably accessible way to object or unsubscribe. Opting out of marketing does not stop necessary service messages.

6. When we share information

We do not sell or rent personal information. We disclose only what is reasonably necessary to:

  • authorised users within the relevant organisation, contractor company, project, report or assignment, according to their role;
  • the customer that controls a workspace and its authorised representatives;
  • Supabase for authentication, database, Edge Functions and private file storage;
  • Vercel for website and application hosting;
  • Google Analytics for optional website visits and coarse app-screen statistics after you allow analytics on the relevant surface;
  • Cloudflare Turnstile for protecting newsletter and launch signup from automated abuse;
  • Tech Local for operating SnagMate's content and newsletter backend, storing launch and marketing preferences, and monitoring delivery under Odin's instructions;
  • Resend for transactional email, consented SnagMate launch news and marketing email where delivery is enabled;
  • Groq for voice-note transcription and limited text summarisation where the voice feature is enabled;
  • Slack for routing product feedback where that integration is configured;
  • PayFast for payment processing only where paid online checkout is enabled;
  • accounting or other messaging providers where a customer enables the corresponding feature;
  • professional advisers, insurers, regulators, courts or law-enforcement bodies where disclosure is lawful and necessary; and
  • a successor in a lawful reorganisation or business transfer, subject to appropriate safeguards.

Providers are limited to the information needed for their function. Operator and service-provider arrangements must include appropriate confidentiality, processing and security obligations.

7. Processing outside South Africa

Some providers may store or process information outside South Africa. Before a cross-border transfer, Odin or the relevant customer must use a basis permitted by section 72 of POPIA, such as adequate foreign protection, a binding agreement with substantially similar safeguards, consent, or a transfer necessary for a contract or the data subject's benefit. The applicable customer setup, provider region and transfer safeguard should be confirmed from the production configuration because they may change over time.

8. Cookies and browser or device storage

SnagMate currently uses necessary cookies or similar storage for authentication sessions, security, route continuity, app preferences and guided-onboarding state. On this public website, optional Google Analytics stays off until you choose Allow analytics. You can decline, or change and withdraw your choice using Privacy choices in the footer. This choice is separate from signing up for SnagMate launch news and newsletters.

When allowed, Google Analytics receives page visits, a browser-generated identifier and basic browser, device and approximate location information. Our page-view events use fixed public-page addresses without query strings or fragments, and referrers are reduced to their website domain. They do not contain names, email addresses, form answers, project records or private report links. Advertising personalisation and Google signals are disabled for this website tag. Optional analytics is not needed to browse this website, use its contact options or join the newsletter.

After analytics permission, registered campaign links can add a public campaign identifier and fixed source and channel labels to these statistics. We keep the last valid tagged campaign in this tab for up to 24 hours. Campaign fields never contain email addresses, recipient identifiers, advertising click identifiers or arbitrary URL text. A public app entry link may carry the campaign identifier; the app still asks for its own analytics choice. Campaign reports show visits and completed-account results associated with tagged links, rather than proving an advertising platform caused a signup.

The SnagMate web app offers its own optional analytics choice in its privacy controls. If allowed there, it reports fixed screen categories such as projects, reports or profile, rather than actual workspace addresses or page contents. App analytics does not send project, customer or user IDs, report links, form fields, snag content or authentication details. Allowing analytics on the public website does not enable it in the app, or the other way around.

With app analytics permission, a confirmed new account completion may also be counted as a signup event. Signing in, requesting an email code, accepting a newsletter request or adding an organisation to an existing account does not itself count as a new account. Account identifiers used privately to prevent duplicate counts are not sent to Google Analytics.

Separately, SnagMate records completed account registrations privately and sends pseudonymous receipts to Tech Local for aggregate reporting. This account count remains available when optional analytics is declined. Campaign attribution is included only with the app’s analytics permission; names and email addresses are not part of these receipts.

We save your analytics choice in this browser. Analytics cookies use the snagwebprefix on this website and smapp in the web app, scoped to each host and set for up to 60 days. Withdrawing analytics stops new collection and removes the relevant analytics cookies; it does not recall information already received by Google. If browser storage is unavailable, your choice works for the current page and may be requested again on another visit. The website does not use advertising pixels or session recordings.

9. How long we keep information

We keep information only for as long as the purpose, customer agreement, law, security need, dispute, audit requirement or legitimate operational need reasonably requires. Retention depends on the record and purpose:

RecordTypical retention approach
Account, organisation and billing metadataFor the active customer relationship and afterwards where required for contract, tax, audit, fraud prevention or disputes. The applicable period depends on the record and legal obligation.
Project, report, snag and evidence recordsFor the project or customer-agreed lifecycle and afterwards as configured or reasonably needed for handover, contractual records, disputes and legal obligations.
Voice notes, transcripts and generated draft fieldsAs part of the related project record until deleted under workspace controls, the customer agreement or the applicable retention schedule.
Invitations, notifications and reminder delivery recordsFor the active workflow and a limited period afterwards for delivery, security, audit and dispute handling.
Support and feedback communicationsFor handling the enquiry and afterwards where needed for support history, disputes or legal obligations.
Security, access and diagnostic logsFor operating and securing the service, with longer retention where needed for an incident, investigation or legal claim. Provider-specific periods depend on the service configuration.
Launch and newsletter preferencesSubscription, consent, delivery and unsubscribe records are stored in SnagMate's protected newsletter backend. Opt-out and suppression records are retained to prevent unwanted emails. No automatic newsletter-record deletion schedule is currently configured.

Authorised users may delete eligible snags, reports or an entire project through guarded controls; deleting a project queues its linked private media for cleanup. Issued or completed evidence can be retained as an immutable project record until the applicable retention rule permits deletion. Copies held by providers and backups may have separate retention arrangements. Report share links allow anyone holding the link to access the shared report while the link is valid; recipients can retain downloaded copies after link expiry or deletion of the original.

10. How we protect information and handle compromises

Safeguards include authenticated access, least-privilege roles, tenant and project boundaries, database row-level security, private storage buckets, controlled uploads and authenticated media downloads, encrypted connections, restricted service credentials, audit records, input validation, and idempotency controls. No online service is entirely risk-free.

If there are reasonable grounds to believe personal information was accessed or acquired by an unauthorised person, Odin or the relevant responsible party will notify the Information Regulator and identifiable affected data subjects as soon as reasonably possible, subject to any lawful delay. An operator must notify the responsible party immediately when it discovers a compromise.

11. Your POPIA rights

Subject to POPIA and other applicable laws, you may ask to:

  • confirm whether personal information about you is held and request access to it;
  • identify third parties or categories of third parties who had access where the law provides;
  • correct or update inaccurate, irrelevant, excessive, outdated, incomplete or misleading information;
  • delete or destroy information that is no longer authorised or required;
  • object to certain processing, restrict use where appropriate, or withdraw consent;
  • stop direct marketing; and
  • request safeguards or a representation regarding a solely automated decision that has a legal or similarly significant effect.

Email hello@snagmate.com. Requests and objections are free to submit and may also be made through another reasonably accessible channel we provide. We may verify identity and authority and will communicate the action taken as required by applicable law. A request cannot override information that must lawfully be retained; if access or deletion is limited, we will explain why.

12. Children and special personal information

SnagMate is a business service intended for authorised site-team users who are at least 18 years old. It is not intended for children. Do not create an account for a child or deliberately submit children's or special personal information unless the responsible party has confirmed a lawful, necessary use and the required safeguards. Site media should avoid identifiable people whenever that information is not needed for the snag record.

13. Questions and complaints

Contact the SnagMate privacy team at hello@snagmate.com so that Odin can investigate and respond. You may also complain directly to the Information Regulator (South Africa):

  • POPIA complaints: POPIAComplaints@inforegulator.org.za
  • Website: inforegulator.org.za
  • Telephone: 010 023 5200
  • Address: Woodmead North Office Park, 54 Maxwell Drive, Woodmead, Johannesburg, 2191

14. Changes to this notice

We may update this notice when SnagMate's features, providers, customer arrangements or legal duties change. The effective date and version identify the published notice. If a change materially affects existing information, we will give appropriate notice and request consent where required.

SnagMate

Site records the whole team can follow.

Quick-start guide
Contact supportPrivacyTerms of UseRefundsCancellationDigital delivery

© 2026 SnagMate. All rights reserved.

Created byTech Local