Privacy Notice · Effective 28 August 2026
Website information
When you visit pausesure.com, the systems that deliver and protect the website may process standard request information such as IP address, browser and device details, requested pages, timestamps, and security diagnostics. Edge abuse controls may use the request address transiently to limit automated traffic; it is not written to the checker's aggregate analytics table. The hosting security layer may set an essential bot-management cookie to distinguish legitimate traffic and protect the service. PauseSure does not add third-party advertising pixels or use that cookie for behavioral advertising.
When you contact us
If you email PauseSure, we receive the address, message, and attachments you choose to send. Use the published product, privacy, legal, or security address for the relevant request. Do not email passwords, verification codes, payment details, government identifiers, or unredacted scam evidence.
Optional content-free analytics
The public checker offers an optional, off-by-default control to share aggregate product events. If you enable it, PauseSure stores counts such as the type of check completed, broad result category, and next-action category. These counts measure feature use and flow reliability; they cannot identify false negatives, provide labeled examples, calibrate detection accuracy, or train a classifier. The analytics event does not contain the entry you checked, URLs, phone numbers, images, contact information, account or session identifiers, device identifiers, IP addresses, or free-form text. Daily aggregate rows are retained for up to 180 days. You can turn this choice off from the checker at any time.
URL threat intelligence
For URL threat checks, PauseSure sends each bounded web address to the PauseSure reputation gateway without the surrounding message or image. Credentials embedded in the address and fragments are removed; the remaining path and query are kept because changing them could check a different destination. The gateway keeps the Google credential on the server and does not write the submitted address to application data or request logs. Google receives the resulting address to compare it with Web Risk threat lists. PauseSure does not open the submitted site, so the lookup does not determine whether it currently responds, has been deactivated, or later returns. Threat matches and short failure backoff may be cached under a SHA-256 key; Lookup no-match responses are not cached. A no-known-match response is point-in-time evidence, not proof that the destination is safe.
Screenshot text recognition
When you choose an image check, the website first validates the selected JPEG, PNG, WebP, or AVIF file and creates a size-bounded JPEG or PNG copy without the original file metadata. The normalized screenshot is uploaded only when you run the check. PauseSure sends it to Google Cloud Vision for text recognition, analyzes the returned text through the canonical fraud engine, and may send bounded valid web addresses found in that text through Google Web Risk. PauseSure does not retain the screenshot or extracted text in application data or request logs after the request. If image recognition is not suitable, you can explicitly choose the pasted-text fallback instead.
Our core commitments
- Collect only what is needed for a feature you deliberately use.
- Use the narrowest practical processing route for each feature.
- Do not sell personal data or use it for behavioral advertising.
- Ask before sharing content with another person or service.
- Show retention and deletion controls in plain language.
Product processing
In the iPhone app, selected evidence is processed only for a check you deliberately request. The content you submit is sent to PauseSure’s analysis service and follows the documented processing route for that input. Other features you deliberately connect may use PauseSure services for account sessions, notification delivery, encrypted Trusted Circle routing, encrypted backup, content-free analytics, and configured reputation lookups. These paths may process submitted check content, account identifiers, hashed session records, encrypted notification tokens, ciphertext, routing metadata, and narrowly scoped security events. A connected feature is not permission to collect unrelated device content.
Connected-content boundaries
Trusted Circle request content and cloud backup content are encrypted before upload. The service still needs limited routing metadata, such as account identifiers, sender and recipient relationships, request status, timestamps, expiry, and encrypted payload size. A provider outage, missing feed, or failed lookup produces Couldn’t verify—not a reassuring result.
What we do not do
PauseSure does not sell personal information, build behavioral advertising profiles from checks, silently turn private evidence into marketing data, or treat a failed reputation lookup as proof of safety.
Retention and deletion
Website and contact information is kept only as long as needed to deliver the site, answer the request, protect the service, and meet applicable obligations. In-app and connected-service controls identify the records a person can delete, leave, replace, or export. Account deletion guidance is available on the Account deletion page.
Your choices
You may choose not to contact us, keep optional analytics off, decline optional app permissions, change iOS permission choices, and use in-app controls for connected relationships, records, export, sign-out, and deletion. Some protection states remain manual because iOS does not expose whether every extension is enabled or pinned.
Service providers and external links
PauseSure uses service providers for website hosting, security, email delivery, screenshot text recognition, and URL threat intelligence. Google Cloud processes submitted screenshots for Vision text recognition and bounded link indicators for Web Risk lookups under its applicable terms and safeguards. Links to banks, government agencies, reporting services, and other websites are governed by those organizations' notices.
Updates to this notice
Material changes are reflected by the effective date on this page. Product disclosures, App Store privacy answers, service-provider use, and actual network behavior are reviewed together.
Contact
Start from the PauseSure Support page for the current verified help routes. Do not send passwords, codes, payment details, identity tokens, or sensitive scam evidence through an unverified route.