Everything RightsValet does, in detail.
From the first upload to the certificate, and everything that guards your archive in between.
First steps
- Set up your organization
- Approve a Copyright Profile
- Upload your first photos
- Sign your first Batch
Three ways in
Photos reach a Batch the way your studio already works. Every way in ends in the same Batch.
Upload in the browser
Drag finished photos into an open Batch. This is how every new Batch starts, and it needs no subscription and no payment method.
Send from Lightroom Classic
Install the plug-in once, on Windows or Mac, and send finished photos from Lightroom Classic into an open Batch. Lightroom uploads are part of the subscription.
Collect nightly from a delivery platform
Once a delivery platform is connected, RightsValet collects newly delivered photos every night at 1:00 a.m. Pacific. Nightly collection needs a verified saved payment method. Platform connections are coming soon.
One Batch, up to 750 photographs
A Batch groups published photographs from as many shoots as it takes, for one photographer, into one registration with one submit-by date.
Nightly ingestion
Collection is a scheduled discipline, not a stream of surprises. One run a night, fully accounted for.
1:00 a.m. Pacific, every night
A single scheduled collection run discovers newly delivered images across every active connection. No webhooks to babysit, no missed events to reconcile.
Rolling 48-hour scans
Each normal run covers the trailing 48 hours of account activity, so a late delivery or a provider hiccup is picked up on the next pass.
Durable catch-up watermarks
If runs are missed while you are entitled, a durable coverage watermark widens the next scan until every missed interval is covered. Nothing silently falls through.
Guided connection wizard
Connect a platform with provider-specific instructions, secrets held in an encrypted credential backend, and a harmless validation check before the first night runs.
Eligibility rules with safe defaults
Delivered, final still images are collected by default. Organizations can tune provider-specific eligibility without risking runaway scope.
Explicit cancellation boundaries
Connector coverage follows the applicable payment and admission rules. Subscription cancellation alone does not stop manual use. Reactivation after a historical cancellation starts a new epoch without implicitly backfilling the gap.
Image records
Every accepted image becomes exactly one archive copy. No sprawl of derivatives, no surprise storage bill.
One copy, prepared without upscaling
New Records use one private progressive JPEG, oriented before sizing, with proportions preserved and no upscaling. Oriented height is at most 1080 pixels; proportional width may exceed 1080 pixels. Output uses sRGB pixels and output ICC.
Wide input coverage
JPEG, PNG, HEIC/HEIF, single-page TIFF, static WebP, DNG, CR2/CR3, NEF, and ARW sources are all accepted.
Organization-scoped identity
Content identity is the SHA-256 of the source, scoped to your organization. Byte-identical revisions reuse one record, and your images are never deduplicated against another tenant.
Output policy, enforced
Quality 100. Final JPEG including metadata: at most 20 MiB (20,971,520 bytes), inclusive. No lower-quality or smaller-dimension fallback. An oversized or malformed JPEG is quarantined instead of published, with the reason reported separately.
Verified before it counts
A record exists only after checksum verification, committed database state, and an independent metadata read-back all succeed.
Copyright metadata
Your rights ride inside the archive copy, written from rules you approve. The archive copy is prepared for the archive: no upscaling, sRGB, oriented, re-encoded, and GPS stripped.
Rights-focused IPTC and XMP
Creator, copyright notice, credit line, source, and rights usage terms are written into every record with a resolved photographer mapping.
Versioned Copyright Profiles
Profiles and photographer mappings are immutable versions. Every record snapshot names the exact versions that produced it.
Location data stripped
GPS coordinates and sensitive location fields are removed from every record.
No visible watermark
Nothing is stamped on the image itself. The record stays presentation-clean.
Honest when incomplete
If no photographer rule resolves, the record publishes without authored copyright fields and is visibly flagged and filterable, never silently guessed.
Registration readiness
The archive is built so a US Copyright Office group registration is a habit, not a project.
Every delivered frame
Nightly enumeration collects every eligible delivered image, not a hand-picked selection. If an infringer grabs the second frame of a burst, that frame is in your archive too.
Built with 750-photo applications in mind
The Copyright Office group fee is $55 per 750 published photographs, as retrieved Tuesday, September 1, 2026; the Office has proposed $85 and fees can change. When the private beta ends, the RightsValet fee is $64.95 per registration, or $55.95 with a subscription, plus the Office fee and any tax. A Copyright Office deposit is its own package, not the Batch ZIP you download from the archive.
A rhythm that keeps the window in reach
Statutory damages and attorney-fee recovery require registration before the infringement or within 3 calendar months of first publication. That statutory window is counted in calendar months, not as a fixed 90 days, and it is separate from how often your archive Batches close. A complete, current archive is what makes the window practical to hit.
Certificates correlate later
The Copyright Office takes about 4 months on average to issue a certificate, and longer with examiner correspondence (Copyright Office processing times retrieved Tuesday, September 1, 2026). Records carry stable content identity and timestamps, so a certificate maps back to exact files whenever it arrives.
Ready for late discovery
Under the discovery rule most US courts apply, the 3-year clock on a claim generally runs from when you knew or reasonably should have known about the infringement. That rule comes from court decisions, not from the Copyright Office, and it is not a guarantee. Indefinite retention, including after cancellation, keeps the record retained when that day comes. Viewing and downloading follow the applicable subscription terms.
Information, not legal advice
RightsValet is an archive, not a law firm, and does not promise outcomes. Registration filing is AI assisted and human processed. Statutory figures come from 17 U.S.C. 412, 504, and 505 and Copyright Office rules.
Organizations and security
Each organization's data is kept apart from every other organization's, and one set of roles decides who can do what.
A permanent identity under the name
Your organization's name and web address can change. The identity your data is filed under does not.
Every organization has a permanent UUID before any business data exists. Slugs are just renameable labels.
Roles that match your team
Owner, administrator, operations manager, billing manager, member, and viewer roles keep credentials, billing, and deletion authority separate.
Exactly one owner
Every organization has one owner at all times. Handing ownership to someone else means signing in again, and the handover either completes or does not happen.
Ownership transfer is a locked, reauthenticated transaction. There is never zero, and never two.
Strong sign-in
Sign in with a passkey or an authenticator-app code, see every session that is signed in, and sign any of them out.
Email verification, TOTP two-factor authentication, passkeys, and per-session listing and revocation.
Platform credentials kept locked away
The keys that connect a delivery platform are stored encrypted, shown only in masked form, and can be replaced or revoked.
Provider secrets live in an encrypted credential backend with masked display, rotation, and revocation. They never appear in queues, logs, or exports.
Verified deletion and legal hold
Deleting an account or an organization is a deliberate, checked process, not a single click, and it waits while a legal hold applies.
Organization and account deletion are durable, verified workflows, subject to legal hold, with no immediate destructive shortcuts.
Archive and exports
Your Records stay private and retained if you cancel. Pending Batches stay viewable. Access to submitted Records follows the applicable subscription terms.
Indefinite retention
Records and their metadata remain private and retained after subscription cancellation until verified deletion or the existing lawful retention rules apply.
Viewing and downloading
When paid Record-access rules are in effect and your organization has accepted the applicable Terms, viewing or downloading submitted Records requires an eligible subscription, qualifying trial, or past-due grace. Records also held by a Pending Batch remain accessible under the existing Pending Batch rules. A lock does not delete a Record; restoring eligible standing restores access. Subscription cancellation alone does not stop manual use or delete Records. Eligible access includes downloads without a total byte quota, subject to fair pacing.
Download links that expire in minutes
Downloading a whole Batch creates a link to that one file that stops working within 5 minutes. Until then, anyone who has the link can use it.
A whole-Batch download is a signed URL scoped to one exact object and valid for at most 5 minutes. It is a bearer link once issued, so it is not restricted to a particular recipient after that. Individual Records stream through the app instead. Storage stays private; fair-use pacing protects everyone.
Batch ZIP downloads
Each Batch is one ZIP of 1 to 750 Records. Download the whole Batch, or any single Record.
Disaster-ready copies
An encrypted second copy in isolated storage, a 24-hour recovery point objective, and quarterly restore tests.
API and billing
An API key works for one organization only, and billing keeps a permanent record of what was charged and why.
One API key, one organization
An API key reads the Records of the one organization it was issued for, and nothing else.
Each API token is bound to exactly one organization when it is issued. Browser state can never retarget it. The public read API is a subscription benefit. Manual or free use alone does not grant API access. Eligible subscription standing includes qualifying trial or grace.
Every request names its organization
Each API address includes the organization it belongs to, so a request cannot land on another customer's data by mistake.
Every public API route is scoped by organization UUID, so cross-tenant confusion is structurally impossible.
One subscription, billed through Stripe
Your organization has one subscription, and Stripe handles the payment.
Organization-level subscriptions with Stripe as the payment authority and the platform as the usage authority. When the private beta ends the subscription is $11.95 a month or $120 a year, and new organizations start with a 30-day free trial that needs a saved payment method up front.
A usage record that is never rewritten
What you used is recorded once and not edited afterward. A correction is added as a new entry, so the history stays intact.
Usage is attributed to a UTC period at availability time, permanently. Corrections are compensating entries, never edits.
Billing that holds up under a retry
If sending usage to Stripe is interrupted and tried again, the retry is matched to the same billable event.
A durable outbox drives Stripe export, and reconciliation converges retries on the same billable event.
Operational safety
Built to run unattended overnight: it recovers from crashes, shares capacity fairly, and reports what actually happened.
Interrupted work is finished, not repeated
If a server fails in the middle of a task, the task is picked up again and ends in the same Record, without a duplicate.
PostgreSQL is the durable work ledger. Redis loss, worker crashes, and retries cannot lose work or duplicate a record.
Nothing is deleted until its Record is proven
RightsValet works on its own staged copy of each photo, not your original, and keeps that copy until the finished Record has been checked.
A staged source is deleted only after the retained record, its checksum, database state, and deletion intent are verified.
95% by 6:00 a.m.
The service objective: 95% of the night's valid, retrievable images are ready by 6:00 a.m. Pacific, and all non-quarantined work finishes before the next run.
Fair pacing everywhere
One organization's heavy night does not slow another's.
Independent limits at every stage keep one tenant from starving another: collection, downloads, processing, signing, and exports.
Guarded downloads
Files fetched from a delivery platform pass security checks and input limits before they are processed, and a file left waiting for 24 hours raises an alert.
SSRF protections, input security limits, and staging-age alerts at 24 hours.