Skip to content
SecTruck

Privacy

Last updated: 15 November 2026.

What we read, and what we share

To protect your company, SecTruck reads the email in every Gmail mailbox you connect, as a monitoring and reporting service for you and your staff. Each message is checked for phishing and fraud, and we use what we learn to improve our filters. We also read your Workspace's list of users (names and email addresses), so you can choose which mailboxes to connect, and, where a setting allows it, Google's sign-in and app-access records for them, to spot unusual sign-ins.

What we learn from one customer's mail protects every customer: we share warning signs between customers, such as bad sender domains, bad links and scam patterns, but never the text of your mail.

We don't sell Gmail data, we don't use it for advertising, and we don't use it to train an AI model, ours or a vendor's.

Scams are rarely aimed at one company; most are broad attacks. So a warning sign found in your mail also protects other customers, and theirs protects you. Examples we learn from that contain mail text stay within your company's account.

Who we are

SecTruck is run by Individual Entrepreneur Kenzhaliev Azret Azamatovich (ИП Кенжалиев Азрет Азаматович), 23/12 Aaly Tokombaev St., Block B, Apt. 37, Bishkek 720060, Kyrgyzstan (ул. Аалы Токомбаева 23/12, Блок Б, кв. 37, г. Бишкек, Кыргызстан, 720060). Privacy questions and requests: azret.kenzhaliev@gmail.com.

What we hold

About your company's account:

About your mail:

The mail we read includes mail from people outside your company, the senders.

What we keep from all customers together, with no company, mailbox or message in it:

Why we use it, and on what ground

We use your data to check your company's mail for phishing and fraud, to label and, where your settings allow it, move what looks dangerous, to tell your staff about it, to run the accounts, and to improve our filters.

Who receives it, and where it is processed

This is the full list today. Your data is processed in the United States: our database is in AWS US East (us-east-1), our keys are in Google Cloud KMS in us-east1, and the service runs on Vercel in iad1 (US East).

How long we keep it

When a company disconnects, the data we kept from its mail (flagged and reported messages, threads, markers, known correspondents, the automatic-reply setting's hash, sign-in baselines and events, and site-check jobs) is deleted once the mail we labelled has been restored, and at the latest after 30 days. What stays: daily counts, with no end date yet; your staff's answers, with the message's Gmail id and mailbox, for up to 180 days; alerts and the audit log, for up to 13 months; and the warning signs we keep for all customers, which hold no company or mailbox. Backups: our database keeps its history for 6 hours, and we keep backup copies of it for 7 to 14 days, so deleted data can persist in them until they expire.

Who can see it

Your company's members, by role, and SecTruck's founders. Founders' views of your company are recorded in the audit log.

Our engineers, and the AI coding and review assistants that help them, may read a specific message when a fix or a review is about that message, and the AI vendors above read what we send them. We don't read your mail otherwise.

Google user data

SecTruck's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

The Gmail permission we ask for, gmail.modify, is broad: Google's own description lets an app read, label, trash and send mail (not delete it for good). We use it only to read mail and to add and remove labels (a label is ours, or the inbox label, which is how mail is moved out and back), and the code that talks to Gmail has no call that sends, trashes or deletes. We also ask to see the people in your Google Workspace domain, to pick seats (read only), and, where a setting allows it, sign-in activity, to spot unusual sign-ins (read only).

We use this data only to give you the checks described here. We transfer it only to the parties above, to give you the feature, for security, or where the law asks.

The rules above apply to what we derive from Google user data as well as to the data itself.

How we use AI

Where your company has agreed to AI review, we may send mail to Anthropic, OpenAI and Google (the Gemini API), in these ways. Each is only for the mailboxes that consent covers, and each stops when we end it:

The models today are claude-opus-5-5, gpt-6.1-sol and gemini-4-carbon-lt for the review, and claude-haiku-5-5 for the screen; the checks and tests use other models of the same vendors, and we may change them. The AI is asked how risky a message is and answers in a fixed form. We send an attachment's name and type, not its contents. Each vendor is on its paid API terms that don't train on our data.

Where AI review is on for your company, the AI's answer can raise or lower the label on a message. It cannot delete or send mail. The AI can be wrong: it can miss a scam, or flag a good message. Where a company's setting allows it, a DANGER message may be moved out of the inbox until your staff restore it.

We don't sell Gmail data, we don't use it for advertising, and we don't use it to train an AI model, ours or a vendor's.

The vendors keep some logs of their own: OpenAI keeps abuse-monitoring logs for up to 30 days by default, and Google's paid Gemini API logs prompts for a limited period for abuse and legal needs only.

We tell the AI that the message is untrusted data and never to follow instructions inside it, and we accept only an answer in the fixed form. If the AI gives no answer, the label stays what our rules gave.

To ask for a review of a label: use "Not a threat" in Gmail, report a message to us, or write to azret.kenzhaliev@gmail.com.

Your choices

What stays after disconnecting is listed under "How long we keep it".

Keeping it safe

The service is reached over HTTPS only. The copies we seal (a reported message, and the AI test's) are encrypted under a key per company that Google Cloud KMS wraps, and the key for a reported message is destroyed when the company's disconnection finishes, and the key for the AI test's copies by a daily job once the company is disconnected. Where the AI reads mail, we tell it the mail is untrusted data, and the code that talks to Gmail has no call that sends, deletes or trashes mail, so a message cannot make it do so.

If we learn of a known or suspected unauthorized access to Google user data, we contain it, tell the customers affected, and notify Google at security@google.com.