Records of processing

This record lists why SiyaBid handles personal information.

  • Account and company profile

    Provide the workspace the company asked for.

    People: Users, directors, and company contacts

    Information: Name, email, phone, address, registration and VAT numbers, and declared procurement details

    Product rule: collected because the person created the account or company.

  • Document vault

    Keep the evidence the company uploads for its own tender preparation.

    People: The company and the people named on those documents

    Information: Files, checksums, expiry dates, and verification level chosen by the user

    Product rule: stored because the company uploaded the file.

  • Tender analysis

    Quote requirements from a tender file the user uploaded.

    People: People mentioned in the tender file

    Information: Tender text, which can contain personal information, a limited company summary, and citations. Guided search can send the words typed when the site does not match them itself. Keyword search does not.

    Product rule: an analysis is sent because the user started it. Guided search can send the words without a separate analysis.

  • Billing

    Record a subscription, a tax invoice, or a credit note.

    People: The company and the billing contact

    Information: Plan and amount. A live card payment and an Android purchase are not available. If a payment form is opened, the billing email, amount, and plan can be sent. Card numbers are not stored.

    A confirmed payment is recorded. Opening a payment form can send the billing details before a charge.

  • Marketing email

    Send product news only where a consent record says the person opted in.

    People: Users who submitted the marketing consent control

    Information: Email address, the choice, the time, and the source

    Product rule: a separate opt-in, not acceptance of the terms.

  • Sign-in and security

    Keep the session, limit repeated failed sign-ins, and record security events.

    People: The person signing in

    Information: Email, password hash, session, IP address, and security events

    Product rule: required to operate the account the person created.

  • Suppliers

    Store a supplier the company adds, or a supplier profile that company publishes.

    People: Supplier contacts named by the company

    Information: Supplier name, contact details, and categories the company enters

    Product rule: stored because the company entered it.

  • Electronic signature

    Store a name typed for an in-app signature. A demonstration signature is not a live signature service.

    People: The signer named on that session

    Information: The typed name stays with the company document. A demonstration signature can also send the document, signer name, and signer email.

    Product rule: an in-app signature is stored because the signer typed it. A demonstration signature is sent only when that signature is started.

  • Contact enquiries

    Keep a message sent from the public contact form.

    People: The person who sent the message

    Information: Name, email, optional organisation, and the message. The form does not send email and does not opt the person into marketing.

    Product rule: stored so the enquiry can be read.

  • Android application

    Open the same website inside the Android Trusted Web Activity.

    People: The person using that app

    Information: The same website data. The app asks for internet and network-state access and does not add its own account store.

    Product rule: the app is the website.