This website
This site has no sign-in, contact form, advertising pixel, cookies, or browser-storage features. Images and styles are hosted with the site; loading a page does not fetch fonts or media from third-party services.
Page views. To see which pages are read, each page loads Microsoft's Azure Application Insights script from js.monitor.azure.com and sends an anonymous page view to our Azure monitoring: the page address and title, the referring page, the browser and operating system, and an approximate location that Microsoft derives from your IP address. The IP address itself is not stored. No cookies or browser storage are used, so visits cannot be linked to you or to each other.
The site is hosted on Microsoft Azure. The hosting service may receive standard technical request information, including an IP address and browser details. Automated availability checks monitor the homepage. A minimal health API uses Azure Application Insights for server-side request telemetry, such as request URLs, timestamps, response codes, and durations. Site pages do not call this API automatically, and the function does not echo or explicitly log request contents. Do not include personal information or credentials in API URLs.
As verified on September 21, 2026, API request records and availability-check results have a 90-day retention setting in our Azure monitoring tables; as verified on September 30, 2026, page-view records do too. This describes those monitoring records, not all information Microsoft may process to operate its services. See the Microsoft Privacy Statement for information about Microsoft's data handling.
Following external links takes you to sites with their own policies. This website does not accept photos, API keys, contributor credentials, or payments.
Alamy & Dreamstime publishing
Each FTP plug-in stores its credentials locally through Lightroom's encrypted password storage. They are separate from the other plug-ins. The JPEGs each plug-in sends, including embedded metadata such as GPS, go directly to the selected agency.
FTP is unencrypted. Account credentials and image data can be exposed in transit. Local encrypted storage does not protect the network connection. Use the agency's HTTPS uploader if encrypted transfer is required.
Local upload history retains filenames and transfer states for duplicate checks. Local diagnostic logs contain stage names, counts, and batch indexes, not credentials, filenames, source paths, or raw server responses. There is no automatic upload of logs and no Expolumi-operated backend or analytics.
Removing a plug-in or published collection does not remove remote submissions. Agency processing and retention follow the agency's own policies.
Expolumi Getty Publisher
The plug-in copies JPEGs rendered by Lightroom, including embedded metadata such as GPS, into a folder you choose on your computer, normally inside your Dropbox folder. It makes no network requests and does not connect to Getty Images or Dropbox; it stores no credentials. The Dropbox desktop app syncs the folder under Dropbox's own terms, and you upload the files in Getty ESP yourself.
A local delivery history keeps file names and batch folder names for duplicate checks. The diagnostic log contains stage names and counts, not paths or file names. See the Getty guide.
Expolumi Shutterstock Publisher
The plug-in uploads JPEGs rendered by Lightroom, including embedded metadata such as GPS, directly to your Shutterstock contributor account over SFTP, which encrypts the connection. Your Shutterstock email or username and password are sent to Shutterstock to sign in. They are stored locally through Lightroom's encrypted password storage, separately from the other plug-ins, and are never written to logs. Shutterstock documents FTPS rather than SFTP for contributors, so it may restrict or change SFTP access.
Local upload history retains filenames and transfer states for duplicate checks. The diagnostic log contains stage names, counts, and batch indexes, not credentials, filenames, source paths, or raw server responses. There is no automatic upload of logs and no Expolumi-operated backend or analytics. Removing a plug-in or published collection does not remove files from Shutterstock, which handles them under its own policies. See the Shutterstock guide.
Expolumi AI Photo Tagging
The plug-in sends a reduced JPEG preview to your configured Microsoft Foundry resource over HTTPS after consent. Embedded metadata is stripped, but identifying image content remains visible. Optional tip text and an enabled capture timestamp are also sent. Do not include information you are not authorized to share.
The resource endpoint and deployment name are local preferences. Your API key uses Lightroom's encrypted local storage. Expolumi does not operate a processing backend, receive the request, or keep a prompt/response archive through the plug-in.
Microsoft's data-processing terms and abuse-monitoring policies apply. A setting disabling stored completions is not a guarantee of zero retention. Processing location depends on the deployment type, not only the resource region.
Temporary preview files are normally deleted. A crash or deletion failure can leave Lightroom-AITagging* folders in the operating system's temporary directory. Close Lightroom before inspecting and removing only those plug-in temporary folders.
Expolumi OneDrive Album (Preview)
This free preview organizes existing personal OneDrive files through Microsoft HTTPS endpoints, not FTP. Requests contain cloud-relative paths, filename searches, file identifiers, album names, and album-membership changes. It does not send photo bytes, render edits, replace files, or delete source files. No telemetry or background account discovery is added.
The preconfigured public application uses device-code sign-in and delegated Files.ReadWrite and offline_access permissions. Files.ReadWrite is broader than access to one folder, although the preview exposes no upload, file-replacement, or file-delete operation. Review Microsoft's consent request and manually verify your local personal OneDrive root before authorizing album work.
Tokens and remembered identity are stored through Lightroom's encrypted password storage, scoped by application and drive. Sign out clears local authorization, not Microsoft's consent. Remove the app's consent in your Microsoft account to revoke access there. Native Lightroom and live OneDrive Photos tests are pending; read the preview guide for scope, recovery, and first-use checks.
Expolumi Publishing Workflow
Channel, album, license type, status, and status date fields are custom metadata in your Lightroom catalog. The plug-in makes no network requests, has no account or telemetry, and never changes photo files. Its fields are not written to XMP sidecars or exported files. Sync only reads other plug-ins' publishing records in the same catalog. See the Workflow guide.
Your controls
- Read the destination and consent prompt before sending an image.
- Use Forget credentials or Forget key to clear locally stored access. This does not revoke credentials at the provider or erase backups.
- Rotate compromised passwords or keys with the relevant service.
- Review every AI suggestion and choose which fields to apply. Existing keywords are merged, not deleted.
- Check metadata actually embedded in JPEGs before publishing, including location fields.
- Review logs and screenshots for personal information before sharing them.
Encryption at rest cannot protect a compromised local account or malicious code in Lightroom. Credentials necessarily exist briefly in memory during use. The plug-ins do not guarantee secure memory or backup erasure.
Catalog changes may be written to disk independently by Lightroom's automatic metadata settings. Keep backups and check those settings before working with sensitive photos.