1. Who we are and what this covers
Logligent is provided by AcesFive, based in the Philippines. This policy explains how we handle personal data when you visit logligent.com, create an account and use the Logligent service, wherever you are.
We follow the Philippine Data Privacy Act of 2012 (Republic Act No. 10173) and the rules of the National Privacy Commission (NPC). Where other privacy laws apply to you, such as the EU or UK GDPR or US state privacy laws, we follow them too. Wherever you live, you have at least the rights in section 10.
A "controller" decides why and how personal data is used; a "processor" uses it on a controller's behalf.
For your account details, we are the personal information controller (the "controller" under the GDPR). For personal data that may appear in the logs you send us, you are the controller and we process it on your behalf as your processor (see section 4).
2. What we collect
When you create an account
- Your name, email address, and, if you give it, your company name.
- Your password, which we store only as a one-way hash (Argon2id). We never see or keep the password itself.
- The plan you chose and when you accepted our Terms and this policy.
- If you sign in with Google: your name, email address and Google account ID, which Google shares with us when you choose it. We don't receive your Google password.
- For two-step verification: your passkeys' public keys, your authenticator app's secret (encrypted), and one-time email codes (stored only as hashes).
- If you invite team members: their name, email address and role.
- A one-time verification code to confirm your email, stored only as a hash and deleted once used.
When you pay for a plan
Payments are processed by payment providers (PayPal, Stripe, PayMongo or Authorize.net). We receive and keep the payment status, amount, receipt details and the provider's references (and, for saved cards, the provider's token for charging renewals). Your full card or bank details go directly to the payment provider and are not stored by Logligent.
When you use the website and service
- A session cookie that keeps you signed in (see section 6).
- Your IP address, used briefly to limit repeated sign-up and code attempts. We store only a scrambled (hashed) form of it, for up to an hour.
- Standard server records of requests (such as IP address, time and page) kept for security and troubleshooting.
- When you visit our public pages: the page, the site that linked to it, your device type (computer, phone or tablet) and your IP address, to understand and protect our website's traffic. We don't use cookies for this.
- When you use our free tools: which tools you open and use, how long each one is on your screen, and your IP address and device type. Never what you type into them.
- The devices you connect and what their Collector reports: device name, hostname, operating system, IP addresses, health (processor, memory, disk), installed software and running services, and your Collector settings.
- Your messages to support.
3. How and why we use it
- To provide the service (our contract with you): create and secure your account, confirm your email, run monitoring for your plan, and send service emails such as codes, alerts and notices.
- To send the Cyber Digest, if your plan includes it (our contract with you): we use your name and email address to email it, and, on plans that tailor it, the names of software found on your devices to point out news that may affect them. This matching happens on our servers. You can unsubscribe at any time with the link in each digest or on its page in your account; your security alerts are not affected.
- To bill you (contract and legal obligation): process payments and renewals through the payment provider of your plan, and keep the records Philippine tax rules require.
- To protect all our customers: the community blocklist (legitimate interest in network and information security). When the same internet address attacks the devices of several customers, we add it to a shared blocklist that other customers' devices can block. Only the address, the kind of attack and when it was seen are used; never the rest of the logs, and never who the customers are. An address leaves the list a week after it was last seen. Customers can stop contributing to it on their Blocked IPs page. If your address is on it by mistake, email [email protected] and we will remove it.
- To keep Logligent secure (legitimate interest): prevent abuse, fraud and attacks, for example by limiting repeated attempts.
- To improve the service (legitimate interest): understand which features are used, using aggregated information wherever possible.
- To meet legal obligations: respond to lawful requests from authorities and keep records the law requires.
The words in brackets are our legal bases under the GDPR and the Data Privacy Act. We do not make decisions about you that have legal or similarly significant effects by automated means alone. We do not sell or "share" your personal data (as California law uses those words), and we do not use it for advertising. If we ever want to send you marketing emails, we will ask for your consent first, and you can withdraw it at any time.
4. Data in the logs you send
The Logligent Collector sends the server and application activity you choose, such as web server and application logs and security events. These can contain personal data about people who use your systems, for example IP addresses, usernames or browser details.
- You decide what is sent, and you are the personal information controller for it.
- We process it only to provide the service to you: storing it, analysing it for threats and showing you the results. The one exception is the addresses of attackers, which also go toward the community blocklist (section 3) unless you turn that off.
- Logligent is designed to redact sensitive values, such as passwords and card numbers, that it recognises before they are stored. Please still avoid sending data you don't need for monitoring.
- We keep it only for your plan's retention period, keep it separate from other customers' data, and do not use it for any other purpose.
Our processing terms
For this data we are your processor (a "personal information processor" under the Data Privacy Act; a "processor" under Article 28 of the GDPR). These commitments, together with our Terms, form our data processing agreement with you:
- We process it only on your documented instructions: our Terms and the way you set up the Service.
- Everyone at Logligent who can access it is bound to confidentiality.
- We protect it with the measures in section 8.
- We use only the sub-processors listed in section 5, under written terms at least as protective as these, and we will tell you of new ones before they start, so you can object or close your account.
- We help you answer requests from the people concerned and meet your own security, breach and impact-assessment duties, where we can.
- We tell you without undue delay after we become aware of a personal data breach affecting it.
- When your account is closed, we delete it as section 7 says, unless the law requires us to keep it.
- We give you the information you need to show these terms are met, and answer reasonable questions about them at [email protected].
5. Who we share it with
We share personal data only as needed to run Logligent, with:
- service providers (sub-processors) that work for us under contracts requiring them to protect the data and use it only for us:
- Amazon Web Services (United States): hosts our servers and databases, including all account data and the logs you send;
- Zoho: sends our emails (codes, alerts, reports and the Cyber Digest), so it receives your name, email address and the email's contents;
- PayPal, Stripe, PayMongo and Authorize.net: process payments for the plan you choose (only the provider of your plan receives your data);
- Google: sign-in with Google, if you choose it, and our website's fonts (Google Fonts receives your IP address and browser details when you visit);
- an AI provider (OpenRouter and the model provider it routes to), for two things:
- the Cyber Digest's summaries, for which we send only public news headlines and excerpts and public vulnerability data, never anything about you;
- the AI assistant ("Ask Logligent"), only when you use it: we send your question and the records it needs to answer, read from your account (for example your devices, threats, errors, blocked addresses and matching log lines, which can contain IP addresses and usernames). Email addresses and keys are hidden before anything is sent. We ask OpenRouter to use only model providers that don't keep this data or train their models on it;
- authorities, when the law requires it or to protect the rights and safety of our customers, our users or the public;
- a buyer or successor, if Logligent or AcesFive is sold or merged, who must continue to protect it as this policy describes.
Each provider also has its own privacy policy for what it does as a controller, for example a payment provider's own records.
6. Cookies
We use one essential cookie, logligent_session. It keeps you signed in and protects forms against forgery. It is sent only over secure connections, can't be read by scripts, and is deleted when you close your browser. We do not use advertising or tracking cookies.
7. How long we keep it
- Account details: while your account is open, and up to 30 days after it is closed.
- Unverified sign-ups: deleted automatically after 7 days if the email is never confirmed.
- Logs and events you send: for your plan's retention period, shown on our pricing, then deleted.
- AI assistant conversations: 30 days after your last message in each, then deleted; you can delete one sooner.
- Billing records: for as long as Philippine tax and accounting laws require.
- Security records: hashed attempt records for up to an hour; server request records for a short period needed for security.
- Website visits: the IP address of a visit for 30 days; the rest of the visit record, without the IP address, for up to 400 days, used only in aggregate.
- Free tools use: 30 days, then deleted.
8. How we protect it
We use organizational, physical and technical measures, including: encryption of data in transit (HTTPS); one-way hashing of passwords and codes; encryption of payment provider keys at rest; separation between customers' data; access limited to people who need it; and limits on repeated attempts. If a personal data breach is likely to put you at real risk, we will tell you and the authorities as the law requires (for the Philippines and under the GDPR, within 72 hours of becoming aware of it).
9. Where it is stored
Logligent's servers and databases are in the United States (Amazon Web Services). Our other providers may process data in other countries. So, unless you are in the United States, your data is transferred outside your country. We protect it there through our providers' data processing terms, which for data from the EU, the UK and Switzerland include the Standard Contractual Clauses approved by the European Commission. You can ask us about these safeguards at [email protected].
Some countries require personal data to be stored only inside the country. Because our data is in the United States, we can't meet such a requirement.
10. Your rights
Wherever you live, you have the right to:
- be informed about how your personal data is processed;
- access your personal data, and get a copy of it;
- correct inaccurate or out-of-date data;
- object to processing based on our legitimate interests, and withdraw consent where we rely on it (this doesn't affect what we did before);
- restrict processing while a correction or objection is being looked at;
- erasure or blocking of data that is no longer needed or was processed unlawfully;
- data portability, getting your data in a common electronic format;
- damages if you suffer harm from inaccurate, unlawfully obtained or misused personal data;
- file a complaint with the National Privacy Commission (privacy.gov.ph) or with the privacy authority where you live.
If the law where you live gives you more rights, such as California residents' rights to know, delete and correct their data, you have them too. We don't sell or share personal data, and we won't treat you differently for using your rights.
To use these rights, email our Data Protection Officer at [email protected]. We will reply within 15 working days, or sooner if your law requires, and may ask you to confirm your identity first. Using these rights is free. If your request is about data in a customer's logs, we will pass it to that customer, who controls that data.
11. Children
Logligent is a business service for people aged 18 and over. We do not knowingly collect personal data from children. If you believe a child has given us their data, please contact us and we will delete it.
12. Changes to this policy
We may update this policy as Logligent or the law changes. The date at the top shows when it last changed. If a change materially affects how we use your personal data, we will tell you by email or in the service before it takes effect.
13. Contact us
AcesFive
Data Protection Officer: [email protected]
Other questions: [email protected]