Trust and Safety

Files are checked by several content-safety providers (OpenAI, Google Cloud Vision, Google Web Risk, a phishing text classifier, and a file-hash lookup against VirusTotal) when they are uploaded, and again later in scheduled re-scans. Images and sampled video frames are checked for unlawful and adult content; PDFs and HTML pages are checked for phishing; links inside files are checked against Google's list of unsafe sites.

When something is flagged, the link is held and not shown to anyone until a person reviews it. Scanning is a safety net, not a guarantee; see our acceptable use policy for what is not allowed and how review works.

Every shared page has a Report button. Reports go to a review queue; confirmed abuse is taken down and repeat or serious offenders are banned. You can also use the abuse page, file a copyright notice, or read how we handle child safety.

Files you share open on lisview.com, not on linkinseconds.com, where your account, sign-in and billing live. Keeping people's uploads on a separate domain means one bad upload elsewhere on the service can't affect your account pages, and shared pages can't read your sign-in cookies. Links shared before the move still work: they redirect to lisview.com.

Links are public by default: anyone with the link can open it. On every plan, Free included, you can add a password, set an expiry date or a view limit, ask viewers for their email first, make a link view-only, or turn it off at any moment. You can export your data and delete your account from the dashboard.

• Everything moves over HTTPS (TLS), and files are encrypted at rest by our storage providers.
• Files sit in a private bucket and are served only through our own checks or short-lived signed links; there are no public raw storage addresses.
• Stored files are not end-to-end encrypted: we and the safety providers above can technically read them. Do not upload sensitive information to a public link.

The details are in our privacy policy.

We do not use uploads to train, fine-tune or improve any AI model, and we tell AI crawlers not to train on shared files either (our robots.txt carries an ai-train=no signal).

Please tell us. Our security page explains what is in scope and what we promise researchers, or email support@linkinseconds.com.