multimedia-soft.com is a Video Processor AI service operated by FABTECH SOFTWARE INC. We wrote this page in plain language because our customers include editors and archivists who do not spend their day reading privacy notices. The goal is for you to finish this document knowing exactly which pieces of information we hold about you, how long we hold them, and what recourse you have if something feels off.
The policy applies to every surface of the product: the marketing pages of multimedia-soft.com, the rendering console, the API, and the support channels. It covers any personal data you hand to us directly and any technical data we observe while the service is doing its job. If you access our tools through a partner integration, that partner's own notice may also apply — we will never use a partner relationship as a reason to collect more than what is described below.
1. What we actually collect
When you create an account or submit a render job, we record a compact set of identifiers. Nothing here is sold, rented, or handed to a data broker.
• Account basics — the email address you signed up with, the display name you chose, and a salted hash of your password (the plain password never touches our database).
• Payment metadata — the last four digits of the card, the issuing brand, and the billing country. Full card numbers are handled by our PCI-certified payment processor and never land on our servers.
• Uploaded media — the video or image files you send to Video Processor AI for compression, format conversion, or enhancement, plus any per-job parameters you picked in the UI.
• Support conversations — the content of tickets, chat transcripts, and any screenshots or sample files you voluntarily attach to help us reproduce an issue.
• Product telemetry — feature clicks, queue wait times, render durations, device class, browser family, and approximate city-level geo (derived from IP, not persisted as a precise coordinate). This data lets us find the next bottleneck in the pipeline.
• Crash diagnostics — when a job fails, we store the error stack, the job configuration, and a non-sensitive fingerprint of the affected file so that engineering can reproduce the failure without needing the original asset.
2. How we use what we collected
Every piece of data above is put to work for a narrow, declared purpose. If a new use case comes up that is not covered here, we update this page before the change goes live.
• Delivering the service — authenticating you, charging the correct plan, routing your job to the right GPU pool, and returning the rendered output.
• Keeping the lights on — meeting our contractual obligations, chasing chargebacks, investigating abuse, and cooperating with valid subpoenas from U.S. courts.
• Improving the product — aggregate, de-identified metrics feed our roadmap decisions. Your individual files are not used to retrain the compression, conversion, or enhancement models.
• Talking to you — sending receipts, security notices, and, only if you opted in, release notes or tutorial emails. You can turn marketing emails off at any time through the unsubscribe footer without losing transactional notifications.
3. What happens to your footage
Files uploaded for processing are stored on encrypted object storage and automatically purged 24 hours after the job finishes, or 72 hours if you explicitly opt into extended retention for batch work. Thumbnails we generate for the preview panel follow the same clock. We do not mine your footage for training, we do not show it to advertisers, and we do not use it as seed data for any generative model.
4. Sharing, security, and your rights
We do not sell personal data. The only third parties that touch it are the infrastructure vendors we rely on to run the service — object storage, payment processing, email delivery, and fraud prevention — and each of them is under a written data-processing agreement that limits them to the task we hired them for. Depending on where you live, you may have the right to access your data, correct it, export it, or ask us to delete it; to exercise any of those rights, email [email protected] from the address on the account and we will answer within 30 days.
We will update this policy as the service evolves. When we make a change that meaningfully affects how your data is handled, we raise the revision date at the top of this page and notify active accounts by email at least seven days before the new version takes effect.