Security & Data Handling

How we safeguard one-time shares

We designed OnlinClipboard to keep data footprints small. This page explains the storage systems we use, what the Worker does with your data, and the expectations you should have before relying on the service.

Infrastructure Overview

  • D1 (Cloudflare’s managed SQLite) stores share metadata and text content.
  • R2 (Cloudflare object storage) keeps uploaded files until they are deleted.
  • KV cache stores review statistics to avoid repeated database scans.
  • A Cloudflare Worker orchestrates uploads, retrievals, and scheduled cleanup jobs.

Retention Windows

Every share is created with a 24-hour expiration timestamp. A successful retrieval marks the share as accessed. Text records can be removed as part of retrieval, while uploaded-file cleanup completes through the protected download endpoint or the scheduled cleanup flow.

An hourly scheduled job runs cleanupExpiredShares to delete any remaining records whose expiration time has passed. This job also removes lingering files from R2 so the storage does not accumulate unused data.

What We Do Not Keep

  • No user-facing version history or recovery function for deleted shares.
  • Direct ?s= share links do not initialize Google Analytics or AdSense; Cloudflare can still process request and security logs.
  • The core clipboard needs only a passcode or slug link. Optional accounts and payments use separate persistent records.

Your Responsibilities

  • Do not use OnlinClipboard to store medical, financial, or other highly sensitive personal data.
  • Treat the generated link or passcode like any other secret—anyone with it can retrieve the content exactly once.
  • Remember that recipients can still save or forward the content outside the platform after retrieval. Automatic deletion does not prevent manual copying.
  • Contact us promptly at support@onlinclipboard.com if you detect abuse or need a share removed before its expiry—we will attempt to assist when technically possible.