◎ siglumoStart a free test

Privacy Policy

Effective date: 24 October 2026

1. Who operates Siglumo

Siglumo is a product of HamCut.

Operated by: Lead Sourcing & Email Marketing

Business address: Sierra Cartel, No. 343, 9th Main, Sector 7, HSR Layout, next to Karnataka ATM, Bangalore, Karnataka 560102, India.

For privacy questions and requests, email info@siglumo.com.

2. What this policy covers

This policy explains how Siglumo handles information when you visit the website, send a test email, view a report or contact us. It also explains the difference between deleting a test and clearing information from your browser.

3. Information in your test email

When you send an email to a Siglumo test address, we receive the original message. This may include sender and recipient addresses, the subject, message headers, body and attachments. Headers may contain sending IP addresses, timestamps and other technical identifiers.

Use a non-sensitive sample that you are authorised to share. Remove passwords, credentials, financial details, confidential material and unnecessary information about other people. Do not send content simply because it is available in your mailbox; make sure you are entitled to submit it for testing.

4. Why we process test information

We process the email to receive and associate it with your test, inspect available sending and authentication evidence, request relevant history and content checks, generate a report, and compare the two messages in a test. We also process information needed to operate the service, handle support requests and prevent misuse.

The report may contain automated interpretations. It is not a guarantee of inbox placement or future delivery.

5. Website, session and operational information

Browser-held test information helps you return to your current or earlier unexpired tests. Retest notes are stored in your browser. Clearing browser data can remove this access or those notes; it does not itself delete information held by Siglumo.

The siglumo_pilot cookie supports a server-validated website session and expires after two hours. The siglumo_session cookie is used only for administrator sign-in and can remain for 30 days. These are separate from the private credentials used to open a test report.

Your browser stores the current test and earlier unexpired test references in siglumo.current-test.v1 and siglumo.previous-tests.v1. Retest notes use siglumo.retest-note.<test reference>. The current test record may also contain the waiting steps you selected. Browser-held records and notes can remain until you delete the test through the interface or clear browser storage. Server-side deletion does not remove copies you have exported or printed.

We record site openings, sessions, approximate distinct IP counts, tests created, emails received, report availability and views, two-email pairs, analysis calls, estimated analysis costs, failures, retries and limit events. Application analytics use a keyed hash of the visitor IP. IP counts are not people counts, and an email's From address does not establish who visited the site. Authorised administrators can inspect sender addresses, sender domains, authentication results and observed sending connections from retained reports.

Detailed usage and abuse events are kept for up to seven days. Admission metadata and message fingerprints are kept for up to 24 hours. Daily aggregate figures are kept for 90 days; identifying daily quota keys are removed as their day buckets age out. Raw email bodies and private report access tokens are not copied into analytics. Standard web-server access logs can contain IP addresses, request paths, times and browser information; they rotate daily with 14 archived logs retained. AWS function logs have a 14-day retention setting. Application diagnostic logs are separate from test-content deletion and may remain in server-managed logs.

6. Services used to produce a report

Our current service disclosure identifies these processing activities:

Attachments and raw message headers are not submitted to the content-analysis or explanation services under this described flow. The original message can still contain both and is held in the storage infrastructure.

Siglumo also inspects message structure and local spam-filter rules on its server without retaining another original message copy. A limited link check may send a HEAD request to up to five public destinations. Query strings, tracking-style links and account-action links are skipped; redirects are not followed. Destination servers can observe the request and Siglumo server IP. Results expire with your test.

Provider-held data may be subject to separate retention arrangements. Deleting a Siglumo test must not be understood as an assurance that every provider-held record is instantly deleted.

Original email storage uses the existing AWS receiving bucket in the US West (Oregon) region. Processing by other services may take place elsewhere. This policy does not promise a specific retention period for provider-held copies or that every processor uses the same location.

7. Who can access information

Access is intended for authorised Siglumo personnel and authorised infrastructure administrators who need it to operate, support or secure the service. Someone who has access to your private test credentials or browser session may be able to view the report while it remains available. Keep private test access information confidential and review copied or printed findings before sharing them.

The administrator dashboard requires an administrator session. Test report access uses independent private credentials; the email address alone does not grant report access. Necessary information may also be disclosed where required by applicable law.

8. Test expiry and deletion

Each test displays its expiry time. The current service schedules original test emails and reports for deletion when the 24-hour test period ends. You can request earlier deletion using Delete test.

Access closes first. Background cleanup normally completes within five minutes and failed cleanup is retried. This is an expected cleanup window, not a guarantee that every deletion completes at exactly that time.

The deletion process is intended to cover the original messages, their attachments, reports and the encrypted body copies used for content retries. Technical deletion records may be retained without the message content.

The 24-hour period starts when the server creates your test address. Expiry applies to that test, not to the availability of free access generally. The cleanup process removes original AWS email objects, their normalised AWS report copies, the app reports, encrypted content-retry text, matching standalone report backups and the private ingestion copy. Derived caches are cleared as part of cleanup. Technical deletion markers prevent delayed writes from recreating removed reports. Operational and abuse logs follow the separate periods above. Support emails sent to info@siglumo.com are separate from test messages and may be retained to handle your request; deleting a test does not delete your support correspondence.

Clearing browser data is not a server-side deletion request. If you cannot access Delete test, contact info@siglumo.com.

9. Your requests and choices

Contact info@siglumo.com to ask about your information or request access, correction or deletion. Include your test reference and enough context to identify the issue, but do not include passwords, API keys or unnecessary message content. We may need proportionate information to verify the request.

Depending on applicable law, you may have rights concerning access, correction, deletion, restriction or objection, or withdrawal of consent where processing relies on it. Contact info@siglumo.com to make a request or raise a concern. We will assess the request under the law that applies and may ask for proportionate verification. You may also have a right to contact the relevant data-protection authority.

10. Security

No online service can promise absolute security. Use non-sensitive samples, protect access to your test and avoid sharing private report details unnecessarily.

The service uses private server-side credentials, independent private report access tokens, administrator sign-in, server-side usage limits and an embedding restriction. Credentials are not included in the public interface. These measures reduce risk but do not guarantee that unauthorised access or misuse is impossible.

11. Policy changes

The current version of this policy will be published here with its effective date. Material changes will be handled in accordance with applicable requirements.

12. Contact

Privacy requests: info@siglumo.com

Operator: Lead Sourcing & Email Marketing

Reporting database retention

The private reporting database keeps pseudonymous test lifecycle records and aggregate usage figures for 90 days. Declared sender addresses, authentication summaries and report identifiers are removed from reporting records at test expiry or deletion. Keyed IP hashes used to count approximate visitors are kept for 30 days; they identify observed networks, not people. The reporting database does not store email bodies, attachments or private test access tokens.

Customer accounts and account emails

If you register, we store your account email address, optional name, password hash, verification status, Terms acknowledgement and login sessions. We use AWS SES to send verification, password reset and security emails. We do not send test email bodies or attachments in these notifications.

Tests created while logged in are linked to that account. Earlier anonymous tests are not linked by matching sender addresses. Account access links are encrypted on the server and removed when the test expires or is deleted. The 24-hour deletion promise for original test emails and reports is unchanged.

Account details remain while your account is active. Contact info@siglumo.com from your verified account address to request account deletion. Account email delivery records are retained for up to seven days; encrypted email-link payloads are removed when their links expire, normally within 30 minutes. Minimal pseudonymous allowance records are retained for up to 90 days. Essential account emails cannot be disabled while using the account; marketing is not enabled.

Prepaid purchases and payment records

Razorpay processes payment details. Siglumo stores the account-linked purchase reference, pack, amount, currency, payment and payment-link identifiers, confirmation status, timestamps and credit usage. Siglumo does not store card numbers, banking credentials or payment authentication codes.

The purchase and credit ledger remains while your account is active so that balances, payment questions and refunds can be handled. It is separate from test content and is not removed by Delete test or the 24-hour email and report expiry. Contact info@siglumo.com to request account and purchase-record deletion; we will explain any records that must be retained before completing the request.