ictNetworks

Privacy policy

ictNetworks Signature Platform · 2 October 2026

This privacy policy is for the ictNetworks Signature Platform at https://sign.ictnetworks.co.za/, operated by ictNetworks in South Africa. It describes the information this application accesses, uses, stores, and shares. It is the policy for this application. It is not a sample, and it is not a stand-in for a different product.

If we change how the application uses Google user data, we will update this page before that change. This URL stays linked from the application homepage and from the sign-in page.

Google user data this application accesses

Google user data is read only when an operator chooses Continue with Google on the sign-in page. The application requests the OpenID Connect scopes openid, email, and profile. From Google’s userinfo endpoint, and from the ID token only if userinfo omits a field, we read:

We do not request Gmail, Google Drive, Calendar, Contacts, Admin SDK Directory, or any other Google Workspace API. We do not read, send, or delete mailbox contents through Google. We do not receive the operator’s Google password.

Sign-in is refused when no operator account already exists for that verified email, when Google says the email is not verified, or when the Google subject does not match the subject already linked to that operator. An unknown Google account cannot create an operator.

How this application uses Google user data

We use that Google user data only to provide operator sign-in for the ictNetworks Signature Platform:

The Google subject is not printed in email signatures. Given and family names appear in the admin only as the operator’s display name. They are not copied into a sender signature unless someone separately types them on a sender address.

We do not use Google user data for targeted, personalized, retargeted, or interest-based advertising. We do not sell it to data brokers or information resellers. We do not use it to determine credit-worthiness or for lending. We do not use it to build an advertising audience. We do not use Google user data, and we do not use Google Workspace APIs, to develop, improve, or train non-personalized or generalized AI or machine-learning models. We do not transfer Google user data to third parties for any of those purposes.

Information the platform collects

The rest of this policy covers information the gateway and the admin store for the companies (tenants) using the platform. Operators enter most of it. Some of it is recorded from mail the gateway stamps.

Sender addresses

For each sending mailbox the company manages, we store the email address and the signature fields an operator fills in: first name, surname, job title, department, work phone, mobile phone, website, up to three labelled HTTPS links, and a street or office address. We also store which group the mailbox belongs to, whether it is active, and whether the operator has blocked it. A mailbox that sends through the gateway before anyone files it is recorded as an unallocated sender address so an operator can complete it. Those fields are what the published signature prints.

Signature content

Each group has signature versions: HTML template, plain-text template, status (draft, published, or retired), and whether the satisfaction survey sits above or below the signature. Operators can upload PNG or JPEG images used in a signature. Those images are stored and served from this application so mail clients can load them. We do not keep a copy of the messages those signatures were stamped onto.

Company lists

Each company can keep shared lists of department names, work phone numbers, websites, and street or office addresses. Operators pick from those lists when they edit a sender address. The list value is stored on the company, and the chosen value is stored again on the sender address that uses it.

Audience and domain tags

When outbound mail has an external recipient, the gateway records the recipient’s domain name for that sending company. It does not store the mailbox local-part in that domain list. Operators tag a domain with an audience name the company defines, such as a customer or supplier tag, and can attach service tags. Untagged domains stay untagged until an operator tags them. A banner or survey aimed at one audience tag is chosen only when every external recipient on the message resolves to that same tag.

Static destinations

An operator can file a specific recipient email address as a static destination, with one audience tag and any service tags. That full email address is stored. For mail to that mailbox, the static destination overrides the domain tag. Domain tags apply only when no static destination matches.

Service tags

Service tags are names a company creates for services a destination has with ictNetworks. They are labels on a destination domain or a static destination. They are not a separate copy of message content.

Survey ratings and comments

A published survey adds a star prompt to stamped mail. The person who receives the mail can submit a rating from 1 to 5 and an optional comment without creating an account. We store the rating, the comment (empty if they skip it), the sending mailbox that carried the survey, the external recipient mailbox that was on the survey link, the survey, the group, and the time. If the company filled in notification addresses, a rating of 1 or 2 can email the low-score list, and a rating of 5 can email the high-score list. Ratings of 3 and 4 do not use those lists.

Operator accounts

Operators are the people who sign in to the admin. We store email address, a bcrypt hash of the password (or an unusable hash when the account is Google sign-in only), first name, last name, role (Super Admin, Reseller, or Domain Admin), whether the account is active, whether a password change is still required, the Google subject when Google sign-in has been used, the last sign-in time, and the domains or companies that operator may manage. A Reseller login is tied to one reseller. Sessions store a random session id, a CSRF token, how the operator signed in, the active company for a Domain Admin, and an expiry. A session lasts 12 hours unless the server is configured with a different lifetime. Failed sign-in attempts are written to the service log with the connecting host. They are not added to the operator profile.

Mail the gateway stamps

The gateway reads each message in transit so it can add the signature, banner, survey, and disclaimer, then sends the message on. It does not store the message body, the subject, or a mailbox copy. For each message it stores a short hash of the raw message, a reason code (for example transformed, stamping disabled, unallocated sender, incomplete profile, or sender blocked), whether the message was transformed, how long stamping took, and links to the company, sender address, signature version, and campaign when those apply. Envelope recipient addresses are stored only when a blocked sender’s message is dropped, so an operator can see who that dropped message was addressed to. They are not stored for ordinary stamped mail.

Campaign click rows store the time, the banner’s destination URL, the campaign, and the sending mailbox that carried the banner. They do not store the recipient address, the subject, or the body. The click then redirects the person to the destination URL the operator configured.

The admin audit trail stores which operator did what, to which object, with the company and domain name when that action has one, and the time. DKIM signing stores a selector, the public DNS text, and the path of the private key on the gateway host. The private key is used to sign transformed mail. It is not a copy of anyone’s mailbox.

How that information is used

We use it to run the ictNetworks Signature Platform for the company that owns the sending domain:

We do not sell this information. We do not use it for advertising. We do not use it to train generalized AI or machine-learning models.

Sharing, transfer, and disclosure

We do not sell, rent, or trade personal information. We do not transfer or disclose Google user data to third parties except as part of the Google sign-in the operator started, or where the law requires it. We do not transfer Google user data, or other personal information from this application, to advertisers, data brokers, or information resellers.

How we protect information

The admin and this public site are served over HTTPS. Operator passwords are stored only as bcrypt hashes. Session cookies are HttpOnly, Secure, and SameSite, and admin changes require the session’s CSRF token. Google sign-in uses a short-lived state and a code challenge, and it never stores a Google password. Domain Admins are limited to granted companies. Private DKIM keys stay on the gateway host. Message bodies are handled in memory for stamping and are not written into the application database. Security procedures are in place to protect the confidentiality of this information, including encryption in transit with HTTPS and access limited by operator role.

Retention and deletion

We keep personal information for as long as the company uses the ictNetworks Signature Platform and for as long as we need it to provide the service, to secure it, to audit changes, and to meet a legal duty. When that period ends for a given record, we delete it or detach it from the person it identifies.

How to ask for access or deletion

Email support@ictnetworks.co.za and ask for access to, or deletion of, personal information held by the ictNetworks Signature Platform. You can also call ictNetworks on (+27) 021 201 2000 or 0861 368 638. Say which mailbox, operator email, or survey response the request is about, and whether you want a copy, a correction, or deletion.

We will confirm that the requester is the person the information is about, or the company that controls the tenant, before we act. An operator who can sign in can correct their own first and last name and their password on the profile page. A company administrator can correct or delete the sender addresses and related records they manage. We may refuse a request where the law allows us to keep the information, for example an audit record we are required to retain, and we will say so.

Someone who only received a stamped message can use the same contact details to ask about a survey rating, a comment, or a click recorded against their mailbox.

Contact

ictNetworks operates the ictNetworks Signature Platform. Privacy requests for this application go to support@ictnetworks.co.za, (+27) 021 201 2000, or 0861 368 638. This policy is published at https://sign.ictnetworks.co.za/privacy-policy.