Privacy Policy

1. Data We Collect

Account Information

We store your account identifier, email address, profile information and plan. You can register with email and password or use Google sign-in. Supabase handles authentication and password verification. Google sign-in provides identity information such as your name, email address and provider identifier; it does not give us your Google password.

Application activity and access history

We record first-party operational activity for security, support and service administration. This includes access requests, IP addresses, approximate country when supplied by our hosting platform, browser and operating-system categories, application surface, timestamps, response status, extraction activity and database change metadata. Signed-in web, Chrome and Outlook clients also report page visits, session visibility and interface actions such as clicks, form submissions and field changes. We record the action and control identifier, not the value you type. These records can be linked to your account and viewed or exported only by authorized platform administrators. Administrative access is itself logged.

Automation indicators may identify a declared crawler or AI agent, or a browser automation signal. They can be absent or spoofed and do not establish a visitor's identity. IP addresses may be shared or represent a VPN or proxy. Activity searches cover 120 days; daily cleanup deletes expired activity rows, with delays possible if the cleanup service fails. Existing procurement, billing and security records have their separately described retention rules. Account deletion clears live account links in this activity log. Infrastructure logs and backups follow their providers' separate retention arrangements.

Activity records exclude passwords, access tokens, cookie contents, query strings, typed values, email bodies, uploaded file contents and screenshots of your session. Browser delivery can be interrupted. This operational collection is separate from optional third-party analytics and diagnostics, which continue to follow your privacy choices. Contact support to request access, correction or deletion.

Email Content

The Chrome Extension reads the content of Gmail emails you are currently viewing, but only when you choose Extract. Email content is read directly from the Gmail webpage (DOM access), without Gmail API permissions. The Outlook add-in reads the selected message through Office APIs. Selected content is transmitted to our servers and AI providers for extraction. Raw email content is processed to fulfil your request and is not stored in our database. Only the structured result is saved.

Uploaded Files

When you upload a file through the web dashboard (PDF, Excel, CSV, Word document, or an image such as PNG or JPG), the file is transmitted to our servers for text extraction and AI processing. Text and document images extracted from PDF files and images are processed in memory and not stored. Current Excel, CSV and Word extraction routes also save structured fields without retaining the uploaded source text. Older records may contain raw text. Manual retention controls let you preview eligible records, place holds and confirm a raw-source purge. This does not erase structured records, copies already sent to providers or backups.

Content safety checks and account restrictions

Required safety checks may send normalized images and PDF page images to AWS Rekognition and send text or independently screened images to OpenAI moderation before extraction. A blocked submission is not forwarded for ordinary AI extraction and does not consume extraction quota. Safety checks can make mistakes and do not guarantee that every harmful item will be detected.

Safety records contain account and incident identifiers, timestamps, hashes, file type, normalized classifier signals, account restrictions and review history. They do not contain blocked files, thumbnails, filenames or source text. Authorized administrators review this metadata. Safety emails contain references and guidance, without attachments. A stable pseudonymous account identifier accompanies OpenAI generation requests and helps associate provider enforcement notices with an account; it is not your email address. Account deletion removes account-owned incident records; provider case metadata can remain without an account link. Ordinary event cleanup is manually controlled, and critical or provider cases require separate review. Contact support for retention information or to contest a restriction, using only the incident reference.

File retry records and local recovery

Supported file retries retain account-linked attempt identifiers, an input hash, usage information, processing status, original processing metadata and a link to the saved result. These records do not retain a second copy of the source file or extracted content. A retry reads the current owned saved result. Deleting that result leaves an attempt record so the same key cannot recreate it; deleting the account removes its attempts. The client can hold the selected file and retry key in memory while recovery remains available. Reloading or closing it can lose those details. See our Cookie & browser storage policy.

Extracted Data

The structured data extracted by AI (vendor name, quote numbers, line items, amounts, etc.) is stored in our database and linked to your account. This is the core output of the Service. You can review, correct and export records through the dashboard. Project records you share may be accessible to authorised collaborators. Deletion and retention are explained below.

Projects, Comparisons & Evidence

We store project membership and roles, supplier records, RFQ drafts, approval history, evaluations and delivery or quality observations you record. Evaluations can include saved quote snapshots, costs, exchange-rate assumptions and decision reasons. Semantic comparisons send selected structured quote fields to an AI provider and save the result, source excerpts, source versions and processing details. Comparison jobs are private to the requesting user with current project access; shared evaluations and project history have separate access and retention rules.

Reviewed action proposals

When you prepare a supported project action proposal, we retain its proposed wording or parameters, selected source evidence, reasons, state and decision history. This can include internal requirements, quotation details, supplier identities and commercial or contact information you deliberately select. Project members with current access can inspect the shared evidence. A proposal does not itself contact a supplier or approve a purchase. Retained proposal facts can remain after a source or resulting draft is deleted; deleting the project removes its proposals. Account deletion clears live contributor references but does not erase shared project snapshots.

Organization Supplier Directory

Where the shared directory is available, organization owners can publish supplier identity details, business addresses, contacts, categories and internal notes for current organization members. Each publication records the reviewed fields, author and reason. An optional private supplier preview copies only the displayed identity fields after confirmation; private aliases, notes, quotes and performance evidence are not automatically shared or synchronized.

Where sourcing, award or issued-order attribution is available, an authorised project editor who is also a current organization member can explicitly associate an issued purchase order, saved RFQ recipient, captured quotation entry or approved award revision with a reviewed directory identity. This shares its display name, legal name, registration reference, country and website with project collaborators. The recorded identity and correction reasons remain in project history. The directory shows linked order values, current receipt quantities and explicitly associated sourcing revisions only to members with access to the project. RFQ recipient and quotation entry associations identify the exact saved revision; later revisions are not automatically linked. Where receipt performance is available, date-filtered quantities and completion comparisons use those accessible order records. Current access, attribution and receipt corrections determine the displayed figures; no separate report is retained. Where award and price history is available, accessible issued orders provide retained award reasons, commercial notes, quoted references and line values. Buyer-selected price comparisons recheck current supplier attribution and project access; no separate comparison record is retained. Explicit award associations can also expose saved selected-supplier costs, reasons, commercial notes and recorded approval evidence without an issued order. Each association identifies a saved evaluation revision and requires current project access to appear in the directory. Where recorded response timing is available, explicitly associated RFQ attempts and reviewed first quotation documents provide send-attempt and buyer-recorded arrival times. Current project access, associations and reviews determine the displayed samples and exclusions; no separate timing report is retained. Where shared quality inspections are available, the current organization owner can explicitly preview and share an owned inspection with current organization members. The shared copy contains the reviewed source supplier name, inspection reference, date, inspected and defective quantities, unit and evidence reference. Private notes are excluded. Source changes do not silently rewrite the copy; changed, voided or unavailable sources are excluded from current quality metrics. Supplier governance reviews, where available, store the organization owner's scoped approval and compliance assessments, review dates, shared notes and document references with issuer and expiry details. Current organization members can read published assessments and their correction or withdrawal history. Where supporting-file sharing is available, an owner can explicitly upload a reviewed PDF against an assessment reference. Current members can download retained files; contents are not sent to AI or independently verified. These reviews remain separate from project procurement approval and spending authority. Organization-only contacts, tax details and notes are not copied into project history.

Organization permissions

Where directory, organization structure, procurement policy, review-group or audit-read permissions are available, we store the member, named permission, grant identity, version, current state and granting owner. Current organization members can read permission labels. Owner grant and revocation reasons, before/after states and membership or ownership invalidations are recorded in organization history, accessible to the owner. Explicitly authorized audit readers can also view selected administrative summaries: recorded membership roles, permission changes, hierarchy changes, policy and review-group publications, including dates, actor and target identifiers, labels, versions and reasons. This read-only view excludes full before/after metadata, supplier responses, project activity and billing. Organization access reviews also let the current owner retain a membership and permission snapshot, review reason and next review date. Current audit readers can inspect these reviews. Snapshots retain owner/member identifiers, roles, join times and grant identifiers, versions and effective states; email labels are fetched live and are not copied into those snapshots. Reviews do not change access. Revocation ends subsequent reads; existing records keep their original retention. These permissions do not provide project approval or access to private supplier responses. Published review-group versions retain the actual publisher and the owner or specific grant authority used at publication. Revoked authority blocks dependent reviews while retaining the group history.

Organization structure

Where organization structure is available, owners and explicitly permitted members publish business units, departments and cost centres with codes, names, descriptions, parent relationships and archive states. Current organization members can read the structure and its version history, including reviewed parent labels, publication authors and reasons. Changes to current paths do not rewrite previously saved versions.

Project organization classification

Where classification is available, eligible project editors explicitly share an organization name and a reviewed business-unit, department and cost-centre path with everyone who can access the project. Saved classifications retain identifiers, hierarchy versions, labels, author references and reasons for the project or an exact shared request revision. Changes, removals and previously reviewed paths remain in project history. An organization procurement register can show these deliberately shared paths for projects and current shared request revisions that a member can already access. Its rows and counts recheck project access and current organization membership without creating another retained copy. Classification does not grant access or spending authority.

Supplier introductions

Where invitation-based onboarding is available, the organization owner can create a private expiring link and send it manually. We retain the intended recipient email, invitation dates, issuer and a hash of the access token. Anyone holding the link can submit business identity, address, registration or tax references, one primary contact, supporting document references, optional PDFs and authority, accuracy and sharing declarations. This does not verify email ownership or certification. Submitted responses are visible only to the current organization owner until an explicit review publishes the identity and contact fields as a new shared directory version. Declarations and supporting references stay in the owner review record. The public form does not run product analytics or session replay. It does not collect bank details. Submitted PDFs stay owner-only until the owner separately reviews and shares exact copies against governance references. Private downloads check current owner access. File removal deletes live private bytes while metadata, hashes and owner review reasons remain; shared copies have separate removal controls. These files are format-checked, not malware-scanned or independently verified. Expiry and revocation end link access; submitted responses remain for owner review, including rejected responses. Deleting the directory supplier or organization removes its invitations, responses and files. Issuer or reviewer account deletion clears live pointers. Administrative audit retains operation reasons, identifiers, response hashes and publication outcomes and reviewed file metadata under existing audit retention, without copying raw responses or access tokens. Reviewed directory versions follow the directory retention above.

Procurement Requests

Where guided intake is available, we store your buying narrative, structured drafts, revisions and review decisions. Optional AI suggestions send only the saved narrative to the configured AI provider after your confirmation. We retain the proposal, source excerpts and model/version details separately from your reviewed draft. Explicitly sharing a request with a project shares its complete saved history, including narratives and AI proposals, with authorised project collaborators.

RFQ Mail & Delivery-Failure Reports

Where RFQ mail features are available, we retain reviewed message content, recipient, approval and send records, and provider receipts or response associations. If you import a delivery-failure email (.eml), its full content and headers are stored encrypted as private evidence. The original sender needs current project access to read that source; collaborators can see permitted delivery-status metadata. Withdrawing evidence corrects its use on the send record but does not delete the original evidence file.

Customer & Quote Data

When you use the quote follow-up features, we store the quotes you track and the customer contact details you enter or that are extracted from those quotes (names, email addresses, phone numbers). When a customer replies, you can paste their reply text into the dashboard; it is stored with the quote and classified by AI (intent detection) to recommend a next step. Recognised opt-out requests stop pending follow-ups. This requires a logged reply; we do not automatically monitor all replies in your mailbox.

AI-Generated Follow-Up Drafts

The Service generates follow-up email drafts with AI, constrained to the facts in your quote and customer data. Automated checks help reject unsupported details, but do not guarantee that a draft is accurate or complete. Drafts are prepared for your review only; you send them yourself from your own mailbox.

Usage Data

We track how many extractions you perform each month to enforce plan limits. We also collect basic usage metrics (number of extractions, source type, confidence scores) to operate the Service. When you allow product analytics, pageviews and product usage events are collected via PostHog using browser or account identifiers. These identifiers are pseudonymous, not necessarily anonymous. Browser, device and interaction information may also be collected. Optional analytics requires a saved browser choice and provider configuration. Essential usage accounting and security records do not depend on this choice.

Optional emails and contact records

For optional ProcureMind emails, we hold the recipient address and any supplied name, country, opt-in date, consent wording and evidence reference, reviewed message, sending status and provider message identifier. An authorised administrator records the evidence; a public business address, purchased list or account registration alone is not an opt-in to our emails. Evidence may refer to a form, an event or another direct request you made to us. Contact us to ask about the source of your record.

You can object to direct marketing or withdraw email consent at any time, free of charge. Use the unsubscribe link in any optional email, reply with a stop request, or contact support. You do not need a ProcureMind account to unsubscribe. We retain a suppression record to prevent further optional messages. Essential account security, billing and requested service messages are separate and must not contain promotions.

Payment Information

Payments are processed by Stripe. We never store your credit card number, CVV, or full payment details. We store billing identifiers, subscription and payment-event information needed to manage your plan and credits.

Google Sheets Access

If you connect Google Sheets, we store OAuth access and refresh tokens server-side to write extracted data to your chosen spreadsheet using the drive.file permission. We store the selected destination and send history. These tokens are encrypted at rest and never exposed to the Chrome Extension. You can revoke access at any time from your Google Account settings or from our Settings page.

Microsoft 365 Access

If you connect a Microsoft 365 account (Outlook or Excel Online), we store OAuth access and refresh tokens server-side, encrypted at rest, with account and destination details. The granted permissions support the features you connect, such as Excel Online writes. RFQ mailbox sending and status checks, where available, use a separately authorised mailbox connection and mail permissions. Office add-in message extraction is a separate action. You can disconnect in Settings or revoke access in Microsoft account permissions.

2. How We Use Your Data

• To provide extraction, quote comparison, projects, approvals, supplier evidence, spreadsheet exports and customer quote follow-up tools
• To enforce plan limits and process subscription payments
• To improve extraction accuracy and product quality
• To classify pasted customer replies (AI intent detection) and recommend next steps
• To send transactional and notification emails (usage warnings, payment notifications, quote activity alerts such as follow-up ready, customer responded, or recovery won). No marketing without consent
• To analyse product usage via PostHog when you allow optional analytics
• To investigate browser errors when you allow optional diagnostics, and maintain essential server security and operational logs. Browser session replay is disabled
• To send optional product emails with explicit opt-in, record the permission relied on, and honour marketing objections and opt-outs

3. Third-Party Processors

We share data with the following third-party services, each under their own privacy policies:

If you export records, send them to a selected spreadsheet, configure an extraction webhook or share a project, the chosen recipient or collaborator receives the relevant data. Webhook deliveries can include structured extraction results. Copies held by those recipients are subject to their own access and retention practices.

AI processing and overseas recipients: Content needed for your selected feature is sent to the configured AI provider. Provider retention and processing are governed by the applicable API terms and account settings; our extraction source-handling rules do not mean that providers retain nothing. Processing can take place outside Australia, including the United States and, when DeepSeek is used, China. See OpenAI API data controls and the DeepSeek Privacy Policy. Hosting, support and other providers may also process information overseas. Contact us for information about the providers used for your workflow. We remain responsible for the privacy obligations that apply to our handling and disclosure of your information.

4. Data Retention

Retention depends on the purpose, an active account or shared project, unresolved disputes, legal obligations and applicable limitation periods. We review deletion requests against those purposes; keeping a backup or shared record is not a blanket exemption from your rights. Some cleanup is manual, so a retention rule does not guarantee immediate automated deletion.

• Optional email records: Reviewed messages, recipient states and consent evidence remain for sending history, permission review and complaint handling until an authorised retention review removes records no longer needed. They are not automatically erased with an account because contacts can exist without accounts. Minimal opt-out records are kept while needed to avoid contacting you again. Contact support to request access, correction or deletion; a suppression record may need to remain to honour an objection.
• Extraction input: Current extraction routes do not retain raw email bodies or uploaded files as extraction source. Structured fields can contain text from the source. Separately submitted replies, RFQ messages and failure-evidence files are retained as workflow records.
• Legacy raw source: Older records may contain source text. Manual retention preview and confirmation can purge eligible stored raw text; held records are excluded. Current upload routes do not retain that source text.
• Extracted data: Owned extraction records are retained while your account is active and removed on account deletion. Snapshots saved in another owner's shared project or evaluation may remain.
• Customer, quote, reply & follow-up data: Retained while your account is active; deleted on account deletion
• Organization structure: Archived units and their saved versions remain readable by current members. Ownership transfer preserves structure and history. Account deletion clears live author references; reviewed parent snapshots, descriptions and reasons remain with the organization. Organization deletion removes its units, versions and organization events.
• Shared organization classifications: Deliberately shared organization names and hierarchy paths remain with their project after organization or unit deletion, membership changes and hierarchy edits. Removing a classification retains its earlier path and reason in project history. Deleting a request removes its current classification records; its classification audit remains with the project. Account deletion clears live author references, while saved history can retain actor and owner identifiers. Project deletion removes these classifications and their project audit.
• Organization permissions: Revoked grants remain recorded until membership or organization deletion. Removing the member or granting owner membership clears their live grants. Ownership transfer clears organization grants. Change and invalidation history remains with the organization, including recorded member identifiers and reasons; account deletion clears live event actor references. Organization deletion removes grants and organization history, including access reviews. Access-review snapshots retain recorded member, owner and grant identifiers after account deletion; email addresses are not retained in these snapshots. Rejoining does not restore a removed grant.
• Organization suppliers: Explicitly published identity and contact versions remain with the organization after correction, archival or deletion of a private source. Author references clear on account deletion, while reviewed content and reasons remain visible to current members. Membership departure removes directory access. Deleting the organization removes its shared directory and revision history. Explicitly shared sourcing, award and order identity snapshots and attribution reasons remain in project audit history after directory, organization or source deletion; live source links and actor references clear as their associated records are deleted. Project deletion removes that project history. Extraction-source purge controls do not remove these shared records. Shared inspection copies remain after private-source or contributor deletion, with live publisher references cleared, and delete with their directory supplier or organization. Governance review rows follow the same directory/organization deletion rule; reviewer account deletion clears the live pointer and flags the assessment for review. Explicitly shared supporting PDFs remain after uploader account deletion and delete with the supplier or organization. Owner-confirmed file removal deletes stored application bytes while retaining the filename, hash, reference and audit history; downloaded copies and backups follow their separate retention. New assessment versions do not automatically inherit attachments. Sharing, governance and file-action reasons and before/after metadata remain under existing administrative audit retention, which retains recorded contributor identifiers and clears the organization pointer when an organization is deleted.
• Private comparisons: Results are available for 30 days while access and source checks pass. Older completed or failed jobs are removed when cleanup runs; expiry is not a guarantee of immediate physical erasure. They also delete with their requesting account or project.
• Procurement requests: Private drafts and their history delete with the requester account. Once explicitly shared, all saved narratives, revisions, AI proposals and decisions remain with the project after contributor deletion; actor references are cleared. Deleting the project removes this request history. Extraction-source retention controls do not purge request narratives.
• Procurement policy: Published organization policies retain versions, authors and change reasons. Policy definitions, matched rules, explicit request associations and quotation references used for request, RFQ, recipient-send and award decisions are copied into their existing histories and shared under project access. These decision snapshots remain with the project after the organization or contributor is deleted; deleting the project removes these shared decision histories.
• Staged approvals: Published project review routes, named reviewer identifiers, review reasons, decisions and frozen route/policy evidence are shared with project members. For requests explicitly shared with a project, this includes the human revision and submission identity tied to each review; private drafts and separate AI proposals are not copied into the approval ledger. Optional step delegation also retains the original reviewer, actual delegate, expiry and delegation/revocation reasons. Organization review-group definitions and history are visible to organization members and delete with the organization. Group versions and member identifiers explicitly selected for project routes remain in those shared project snapshots. Project approval evidence remains after an account is deleted, with live actor references cleared. Deleting the project removes its approval history.
• Purchase orders and reviews: Where order preparation and review are available, saved buyer/supplier contact details, addresses, commercial terms, line values and frozen award/approval evidence are shared with project members. Commercial revisions, review submissions, decisions, reopening and cancellation history remain with the project after contributor or source-evaluation deletion. Where manual PDF issuance is available, the finalized PDF, order number and issuance evidence are also retained with the project. Buyer-recorded supplier responses may include contact details, communication references, response dates and summaries, including superseded acknowledgement and cancellation-review evidence. Receipt records retain delivery references, dates, line quantities, damage/rejection counts, receiving-user references, evidence summaries, notes and void/closure history with the project. Live actor references are cleared; shared decision snapshots may retain actor identifiers and reviewed details. Deleting the project removes this order history and retained PDFs. Raw email bodies and uploaded files are not automatically copied into order evidence, and extraction-source purge controls do not remove these shared structured records or PDFs. Copies downloaded or sent through external email are outside ProcureMind retention controls.
• Shared comparison mappings: If you explicitly share a comparison to prepare evaluation mappings, its structured sources, citations and subsequent human reviews become project history. That shared copy and evaluation provenance remain with the project after private-job expiry or contributor account deletion; deleting the project removes its stored mapping history. Raw email bodies and uploaded files are not copied into this history.
• Delivery-failure evidence: Imported source files remain after evidence withdrawal and delete with the original sender account or the related dispatch/project. They are separate from the manual extraction-source purge.
• Shared history: RFQ, award and clarification records in another owner's project can survive deletion of an editor or approver account. Clarifications retain captured quotation, sourcing RFQ and requirement context, reviewed questions and buyer-recorded outcomes with the project; deleting a source record does not erase those snapshots. Actor references are cleared, but saved content and history may still contain information supplied by that person. Contact us about personal information in these records.
• Usage logs: Account-linked extraction counts are retained to support allowances and usage history and removed on account deletion; there is currently no automatic 13-month expiry.
• Connected-service tokens: Retained until you disconnect the relevant Google or Microsoft connection or delete the account.
• External copies: Account deletion or a source purge does not remove copies already exported, emailed or written to spreadsheets. Provider logs, billing records and any backups have separate retention; contact us with a deletion request concerning those records.

5. Your Rights

Depending on your location, you may have the following rights regarding your personal data:

• Access: Request a copy of data we hold about you
• Correction: Request correction of inaccurate data
• Deletion: Use Settings → "Delete my account" or contact us about specific information. The shared-history and external-copy limitations above apply.
• Portability: Export your extraction history as CSV or a branded Excel file from the dashboard
• Objection: Object to processing based on legitimate interests. Your right to object to direct marketing is unconditional
• Withdrawal of consent: Unsubscribe from optional email or change your Privacy choices. Withdrawal does not affect processing already lawfully carried out
• Restriction and complaints: Request restriction where applicable and complain to the relevant privacy regulator

To exercise any of these rights, email us at support@procuremind.io. For EU/UK requests, we respond without undue delay and normally within one calendar month. Where the law permits an extension, we explain the reason and timing within the initial period. We may request proportionate identity verification. Requests are normally free of charge.

6. Cookies & Tracking

Our Cookie & browser storage policy describes website and installed-client storage. Use the Privacy choices control to accept, reject or change optional analytics and browser diagnostics independently. Both are off by default.

Cookies and browser storage support authentication, session management and preferences. With your permission, PostHog measures product usage using memory-only browser identifiers and Sentry collects browser error reports. Browser session replay is disabled. Rejecting optional tracking does not prevent sign-in; blocking essential authentication storage can. We do not use third-party advertising cookies or sell your data.

7. Security

We use industry-standard security practices: TLS encryption in transit, encrypted storage at rest via Supabase, row-level security and permission checks for owned and explicitly shared data, and AES-256-GCM encryption for stored OAuth tokens. The Chrome Extension stores only your ProcureMind session in Chrome's extension storage. The access token is session-scoped and cleared when the browser closes; a refresh token persists in extension-isolated local storage to restore sign-in. Connected-service tokens are stored server-side. See our Security page for details.

8. Children's Privacy

The Service is not directed to individuals under 18. We do not knowingly collect personal data from children. If you believe we have collected data from a child, contact us immediately at support@procuremind.io.

9. Changes to This Policy

We may update this Privacy Policy periodically. We will notify you of material changes by email or by posting a notice on the Service. The "Last updated" date at the top indicates when this policy was last revised.

10. Australian Privacy Act & Your Rights

We handle privacy requests under the Australian laws that apply to our activities, including the Privacy Act 1988 (Cth) and Australian Privacy Principles where applicable. You can:

• Access personal information we hold about you (APP 12)
• Correct inaccurate or out-of-date information (APP 13)
• Request deletion or use Settings → "Delete my account", subject to the retention and shared-history details above
• Complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au if you believe we have breached the APPs

We will respond to privacy requests within 30 days. In the event of an eligible data breach we will notify affected individuals and the OAIC as required by the NDB scheme.

11. International Users & GDPR

Cyber Eccentric Pty Ltd is established in Australia. Where the EU GDPR or UK GDPR applies, we act as controller for account administration, our own communications, billing and service security. A business customer may act as controller for personal data in supplier documents and other content it submits, with us acting as processor when handling that content on its instructions. Those responsibilities depend on the actual processing and applicable agreement. Contact us about data-processing terms before submitting data on behalf of your organisation.

For our controller activities, the purposes and bases are: contract for providing the service requested by an individual account holder; legitimate interests in administering business accounts, preventing abuse, investigating faults and responding to enquiries; legal obligations for applicable accounting and regulatory duties; and consent for optional marketing and browser analytics/diagnostics. We assess legitimate interests against your rights. Granting an integration permission enables your requested feature; it does not give permission for marketing.

You can complain to the Irish Data Protection Commission, the UK Information Commissioner's Office, or the competent authority in your EEA country. You do not have to contact us first.

Account details necessary to provide a requested feature must be supplied for that feature to work. Optional marketing and analytics choices are not a condition of access. AI extraction and suggestions support human review. Safety classifiers can restrict processing; you may ask for a human review using an incident reference, without resending blocked material.

In addition to the rights in Section 5, you have the right to restrict or object to processing, the right to lodge a complaint with your local supervisory authority, and the right to withdraw consent at any time without affecting the lawfulness of processing before withdrawal. Section 3 describes overseas processing. Contact us for details of applicable transfer arrangements; this policy does not itself establish an international transfer safeguard or waive your statutory rights.

12. Contact Us

For privacy enquiries, data requests, or complaints:

Cyber Eccentric Pty Ltd
Sydney, New South Wales, Australia
Email: support@procuremind.io
Website: procuremind.io