File transfer & security terms.

The vocabulary of modern file sharing — encryption modes, infrastructure, compliance, and the rest. Bookmark this if you read security writeups or product roadmaps.

6-digit code

The short numeric identifier SendMe assigns to every transfer. Easier to read aloud than a URL, guaranteed unique within its expiry window.

AdSense

Google's advertising network. Sites are reviewed against Google's content quality policies before they're approved to monetize.

AES-256-GCM

Advanced Encryption Standard with a 256-bit key in Galois/Counter mode — the encryption algorithm used by most cloud storage providers, including SendMe's backend.

API (Application Programming Interface)

A programmatic way to interact with a service. SendMe's REST API is on the 2026 roadmap.

Bcrypt

A password-hashing function designed to be slow and resistant to brute-force attacks. SendMe stores all passwords as bcrypt hashes — even we can't read them.

Bandwidth throttling

When an internet service provider intentionally limits the speed of certain types of traffic. File-sharing services are occasionally throttled, which can be bypassed with a VPN.

Cookie consent

The banner asking visitors whether they accept cookies. Required by GDPR for any website serving EU users.

DLT (Distributed Ledger Technology) registration

In India, every transactional SMS sender must register their entity, header, and template on the DLT platform before bulk SMS can be sent through carriers.

DND (Do Not Disturb)

An Indian telecom feature that blocks promotional SMS. Properly registered transactional SMS (like SendMe's OTP) bypasses DND by default.

End-to-end encryption (E2EE)

Encryption where only the sender and receiver hold the decryption key — the service operator cannot read the content. SendMe's default mode is not E2EE; it's on the roadmap.

Expiry window

The amount of time a SendMe transfer remains accessible. Free plan: up to 24 hours. Pro plan: up to 7 days. After expiry, the file is purged.

FAQ schema

Structured data (JSON-LD) on a web page that tells search engines, 'this is a Frequently Asked Questions block'. Boosts visibility in Google's rich results.

GDPR (General Data Protection Regulation)

EU law governing how personal data is collected, stored, and processed. SendMe is GDPR-compliant by design — minimal data collection, automatic deletion on expiry, account deletion on request.

GSTIN

Goods and Services Tax Identification Number — the 15-character identifier issued to every GST-registered business in India. Required for claiming input tax credit on SendMe Pro.

Hash

A one-way mathematical transformation that turns input (like a password) into a fixed-length string. Even tiny changes to the input produce wildly different hashes, and the hash can't be reversed to recover the input.

HTTPS

Hypertext Transfer Protocol Secure — the encrypted version of HTTP. SendMe forces HTTPS for every page; HTTP requests are auto-redirected.

JSZip

A JavaScript library SendMe's web client uses to bundle multiple downloaded files into a single ZIP archive on the client side, before saving to disk.

Multi-part upload

Splitting a large file into smaller chunks and uploading each separately, allowing parallelism and resume on failure. SendMe Pro uploads >100 MB use this technique.

MSG91

An Indian SMS gateway. SendMe uses MSG91 to deliver mobile OTPs for team workspace verification.

Object storage

A storage architecture that treats data as objects with unique IDs, rather than files in a folder hierarchy. Scales to billions of objects. SendMe stores transfers on encrypted object storage.

OTP (One-Time Password)

A 6-digit numeric code valid for a short window (typically 5 minutes). Used by SendMe to verify mobile numbers on team creation/join.

Password protection

Optional feature that requires receivers to enter a password before the download starts. Layers defence on top of the 6-digit code.

QR code

A 2D matrix barcode that encodes a URL. Scan it with any modern phone camera to jump straight to the SendMe receive page.

Range request

An HTTP feature for downloading specific byte ranges of a file, enabling pause/resume. SendMe's current storage backend doesn't support range requests; this is a known limitation we're working on.

Rate limiting

Capping the number of requests a single user or IP can make in a time window. Used to prevent brute-force attacks on 6-digit codes and OTPs.

Razorpay

An Indian payment gateway. SendMe uses Razorpay to process Pro subscription payments (UPI, cards, netbanking, wallets).

Receive URL

The shareable link that opens a transfer's download page. Format: sendme.co.in/r/{code}

Robots.txt

A plain-text file at /robots.txt that tells search-engine crawlers which pages to index and which to skip. SendMe's robots.txt disallows API endpoints and authenticated pages.

Service worker

A browser background script that can intercept network requests for offline support. SendMe's PWA roadmap includes a service worker for Add-to-Home-Screen functionality.

Sitemap.xml

A machine-readable list of all public URLs on a site, submitted to search engines so they can discover content. SendMe's sitemap is at /sitemap.xml.

Soft delete

Marking a record as deleted without actually purging it from storage. SendMe avoids soft delete for transfer content — when something expires or is deleted, the file is removed.

Team workspace

A Drive-style shared folder for up to 10 members with 5 GB of shared storage, included in SendMe Pro and the Team plan.

TLS 1.3

The latest version of the Transport Layer Security protocol, used for encrypting HTTPS connections. Mandatory for all SendMe traffic.

Transfer code collision

When two different uploads would generate the same 6-digit code. SendMe avoids this by retrying code generation until a unique one is found.

UUID (Universally Unique Identifier)

A 128-bit identifier generated to be globally unique without coordination. SendMe uses UUIDs internally for file storage paths.

WebSocket

A protocol for bi-directional real-time communication between browser and server. SendMe doesn't currently use WebSockets — the upload model is straightforward HTTPS.