Data Retention Questions to Ask Any Stock Tool

How long a stock tool keeps your files, whether it must delete them, and what its terms allow. Six questions, answered from four vendors' own policies.

Retention policies in stock tooling come in three shapes. Desktop tools keep files and agency credentials on your own machine, so there is nothing for a vendor to retain. Cloud upload services hold files briefly and publish a ceiling: Xpiks Cloud states seven days. Managed pipelines keep content for as long as the account exists, and at least one reserves the right not to delete it at all.

That difference only becomes visible when you want out, which is the worst moment to read a policy for the first time. Everything below is quoted or paraphrased from each vendor's own published privacy policy or terms, checked in November 2026. Where a policy is silent, this guide says so rather than assuming the generous reading.

The six questions worth asking

Retention is not one question but six, and a policy can answer some well while staying silent on the others. How long are uploaded files kept. Can you force deletion, and how fast. Where do the files physically sit. Are agency credentials stored on the vendor's side or only on yours. Does the licence you grant allow the content to be used for model training. And what survives after you close the account.

The last two are the ones that cause real damage, because they are the two a privacy policy usually does not cover. They live in the terms of use instead, and the terms are where a licence grant can outlive the account that created it.

Retention audit for a stock tool

Six retention questions plus the places each answer is usually found: file retention period, forced deletion and response time, storage location, where agency credentials live, whether the licence covers model training, and what survives account closure.

What four vendors actually publish

Xpiks: the most specific policy of the four

Xpiks is a desktop application, and its privacy policy reflects that: it works without an account, keeps microstock credentials only on your computer in encrypted form with an optional master password, and describes no transmission of image files or metadata at all. What leaves the machine is an anonymous health report you can switch off, and diagnostic logs only if you attach them to a support request.

The optional Xpiks Cloud upload is where retention becomes a real question, and it is the only one of the four with a published ceiling: files are kept for up to seven days. The documentation goes further than most, stating that the upload server has no persistent storage of its own and no direct public internet access, that these servers are rotated frequently, that the desktop app holds only temporary write-only access to a file during its first upload, and that FTP credentials are not stored on Xpiks servers but encrypted with a key shared between the app and the upload server.

The limitation is scope rather than policy. Cloud upload is unavailable during the trial, the total upload has to exceed 300 MB or Xpiks falls back to a direct upload, a batch caps at 250 files, and allowance is metered: a Pro+ subscription includes 4 GB a month, with extra bought in tiers. The pricing model is a one-time or yearly licence rather than a share of your earnings.

StockSubmitter: a named region, no named period

StockSubmitter's privacy policy, published under the Microstock.Plus name, is the only one of the four to name a storage region: personal information is stored in the EEA and processing uses databases located there. It is explicit that files and content are stored in its systems, and that it holds data used to authenticate on microstock agency websites on your behalf. Both content and that authentication data remain stored for as long as you have an account.

On the deletion side it is better than average: stored content and metadata can be deleted at any time, through the interface or technical support, and the policy states a right to request erasure. What it does not give is a retention period for files or credentials beyond the life of the account, a deletion timeline, or anything about encryption and backup retention. For a contributor the practical reading is that credentials sit server-side by design, because that is how submission on your behalf works, and the compensating control is the named region and the self-service deletion.

Wirestock: the licence outlives the account

Wirestock's privacy policy reads like most of its peers: information is retained for as long as the account is active, with no specific period for uploaded content, and deletion runs either through Account Settings or by emailing support, with a commitment to respond within 30 days. Personal information is described as residing on secure servers, with no region named and subprocessors mentioned but not located.

The consequential clauses are in the terms of use, and contributors should read them before uploading rather than before leaving. Submitting content grants Wirestock a worldwide, non-exclusive, transferable, sublicensable licence, and the permitted uses explicitly include developing, building, training, testing, validating and improving AI and other technology. Copyright itself stays with the creator, which the terms state plainly.

Termination is where the three questions a privacy policy skips get answered. Wirestock has 90 days to remove content from the marketplaces it placed it on, and that window stretches beyond 100 items. Licences granted before termination survive it, and any licences already issued to end users remain in force. And the terms state that Wirestock and its partners are not required to delete content from their systems, and may keep using it to support or retrain products that depend on it. That is not a hidden clause; it is published, and it is the honest answer to whether closing an account undoes an upload.

What Wirestock offers in exchange is a managed pipeline: it handles distribution and the commercial relationship with agencies, and its published split pays contributors 85% of the royalty on standard downloads, keeping 15%, with prints at 70% of what it receives and dataset deals priced separately. For a contributor who does not want to run submissions, that trade is reasonable. It is a different product from a tool, and retention is one of the ways the difference shows.

BlackBox: check the date on the policy

BlackBox's privacy policy retains information for as long as the account is active or as needed to provide services, gives no period for uploaded footage, and routes deletion through profile settings or an email to the company, with a 30-day response commitment and a stated right to access, correct or delete personal information at any time. It does not name a storage location, saying only that personal information sits on a secure server reachable by selected personnel and contractors, and it does not mention AI training in either direction.

The detail worth noticing is the footer: the policy states it was last modified in May 2016. That is not evidence of bad practice, and the company may well handle footage carefully. It does mean the document cannot tell you how a 2026 pipeline treats content, so the answer has to come from support in writing rather than from the page. A policy's date is part of its content, and it is the first thing to check on any vendor page.

The pattern across all four

Three of the four answer retention with a version of the same sentence: as long as your account is active. Only Xpiks publishes a number, and it does so for a narrowly scoped feature rather than for the product as a whole. Two of the four commit to a 30-day response on deletion requests, which is a GDPR-shaped commitment rather than a deletion deadline, and the distinction matters: responding is not deleting.

Only one names a storage region. Only one spells out what happens to the licence after you leave, and the answer there is that the licence continues. None of the four is doing anything unusual for software of this kind. The useful conclusion is that the privacy policy is the wrong document to judge a stock tool on, because the clauses that bind you sit in the terms of use.

When to use which model

A fully local desktop tool is the right answer when the content itself is the sensitivity: commissioned work under embargo, unreleased material, anything where a third party holding a copy is the problem regardless of policy. The cost is that you run every submission yourself and the machine has to be on.

A cloud upload service with a published ceiling suits high-volume delivery where you want the transfer off your connection but not a permanent copy anywhere. The thing to verify is the ceiling itself and whether credentials are held server-side, which is the same question as where your files go during processing.

A managed pipeline makes sense when you want someone else to own distribution and you accept a royalty share and a durable licence as the price. It is a poor fit if you expect to migrate later, since the licence and the retained copies do not travel with you. If that trade is the deciding factor, the revenue share question is worth settling first.

Which retention model fits your work?

Three questions route you to a local desktop tool, a cloud upload service with a published retention ceiling, or a managed pipeline, based on whether a third-party copy is acceptable, whether credentials may be held server-side, and whether you expect to migrate later.

Where Rastock.ai sits, and where it does not

Rastock.ai is a tool rather than a pipeline. It generates metadata and delivers over FTP or SFTP to 10+ agencies, with per-agency status, and the commercial relationship with each agency stays yours. There is no revenue share, no claim of ownership over your files, and IPTC, CSV and XML export stay open so the metadata is portable out as well as in.

The honest limits: it is a hosted service, so files are processed on the server side rather than on your machine, which rules it out for work where no third-party copy is acceptable at all. And it does not sell your content for you, so a contributor who wants distribution and the agency relationship handled end to end is describing a managed pipeline, not this. If portability is the thing you care about, the export-and-leave test is the one worth running before you commit, and the security page is where our own answers to the six questions live.

Whichever model you land on, ask the six questions in writing before the first batch rather than after, and keep the reply. The 14-day trial needs no card, which makes it cheap to run the export test on a handful of files before anything large moves.

Frequently asked questions

How long do stock metadata tools keep your uploaded files?

Most do not publish a period. Xpiks states that files in its cloud upload are kept for up to seven days. StockSubmitter, Wirestock and BlackBox all use a version of the same formula instead: information is retained for as long as the account is active. That means the real answer for three of the four is indefinite, bounded only by when you close the account and request deletion.

Can I force a stock tool to delete my files?

You can request it, and GDPR gives that request legal weight in the EEA. Wirestock and BlackBox both commit to responding to a deletion request within 30 days, which is a response deadline rather than a deletion deadline. StockSubmitter lets you delete stored content and metadata yourself at any time through its interface. Read the terms as well, because a surviving licence can outlast a deleted file.

Does closing my account undo the upload?

Not necessarily. Wirestock's terms state that licences granted before termination survive it, that licences already issued to end users remain in force, and that Wirestock and its partners are not required to delete content from their systems. It also has 90 days to pull content from the marketplaces it placed it on. Closing the account stops new licensing; it does not reverse what already happened.

Can a stock tool use my photos to train AI models?

It depends on the licence you granted, not on the privacy policy. Wirestock's terms of use explicitly list developing, building, training, testing, validating and improving AI among the permitted uses of submitted content, while confirming that copyright stays with the creator. Xpiks, StockSubmitter and BlackBox do not mention model training either way, which is silence rather than a prohibition.

Is it safer to use a desktop tool than a cloud one?

For retention specifically, yes, because there is nothing held remotely to retain. Xpiks keeps agency credentials only on your computer, encrypted, with an optional master password, and describes no transmission of image files. The trade-off is operational: you run every submission yourself, the machine has to be on, and backups of that machine become your responsibility rather than a vendor's.

What should I check before uploading to any stock tool?

Six things: the stated retention period, the deletion route and its committed response time, whether a storage region is named, whether agency credentials sit server-side, whether the licence covers model training, and what survives account closure. The first four live in the privacy policy, the last two in the terms of use. Check the date on both pages, since an old policy cannot describe current practice.