This Privacy Policy explains what MediaToURL processes when you visit the service, create an account, upload or share a file, use an integration, contact support, or submit an abuse or copyright report. It is written to describe the real operating purposes of the platform; it is not a promise that every security or privacy risk can be eliminated.
The current independent build provides public pages and local browser previews. Its dedicated hosting, account authentication, and billing services are not provisioned, so cloud uploads, stored accounts, subscriptions, and the integrations described in older product materials are not enabled here. This policy distinguishes current visitor and support interactions from data processing that may apply only if a feature is later made available. Rights available under the law that applies to you are not limited by this policy.
1. Who Operates MediaToURL
MediaToURL is operated by Sagar Kumar Sahu, sole proprietor trading as Sagarvo Labs, with a business address at Infocity Road, Bhubaneswar, Odisha 751021, India. Where applicable privacy law uses the concept of a controller or a similar responsible business, Sagar Kumar Sahu, sole proprietor trading as Sagarvo Labs is responsible for the personal information that MediaToURL processes for its own product operations.
For privacy questions or requests, contact [email protected]. Account related requests should normally be sent from the email address connected to the account because this helps us verify that information is not disclosed or deleted for the wrong person.
2. Information We Process
Account and workspace data: The current build does not enable account sign-in or workspace persistence. If those features are made available, the data needed to operate them may include an account email, authentication state, workspace membership and roles, plan entitlements, and support communications. No payment processor or subscription checkout is currently connected to this independent service.
Files and asset metadata: Local previews process a file in the browser when you select it; this does not send it to MediaToURL storage. Cloud file processing, storage records, link settings, and hosted delivery will apply only after dedicated services are provisioned and the relevant features are enabled. Browser-side editing may create temporary local object URLs or downloaded exports.
Security and abuse signals: Requests may produce IP address or IP-derived rate-limit values, user agent, request time, route, status, bandwidth and quota events, authentication events, upload validation results, abuse reports, moderation actions, and integration or API activity. We use the minimum information reasonably needed for security, fraud prevention, troubleshooting, and enforcement. We do not need to retain a readable copy of a password to verify password-protected links.
3. Why We Use This Information
Service delivery: Public pages provide product information and local tools. Account, asset, link, workspace, and usage data would be used to provide hosted features only if and when the independent services needed for them are enabled.
Security and abuse prevention: We use validation results, rate limits, account and workspace signals, delivery events, reports, and other security data to detect spam, automated abuse, malware or phishing indicators, privacy violations, copyright complaints, evasion, and attacks against the platform. This may involve automated checks followed by human review.
Legal and operational purposes: We process information to comply with lawful requests, protect users and the service, investigate incidents, maintain records, resolve disputes, prevent fraud, improve reliability, and enforce the Terms of Service and Acceptable Use Policy. We do not sell uploaded files or use the contents of uploaded files for behavioral advertising.
4. Public Links Are Not Confidential Storage
The current build does not create hosted MediaToURL file links. If public or unlisted delivery is enabled in the future, anyone who obtains such a URL may be able to open, forward, embed, or copy it. Unlisted means less discoverable, not private or confidential.
Private and password-protected links use additional access checks, but they cannot prevent a recipient from copying a URL, sharing a password, taking a screenshot, or redistributing a file after access. Do not upload passwords, recovery codes, private keys, regulated records, or other material that requires a dedicated confidential-storage system.
MediaToURL may use no-index controls on appropriate user-generated pages, but search-engine controls cannot guarantee that a URL will never be discovered or that a third party will not publish a copy elsewhere.
5. Abuse Reports, Review, and Strict Response
A report may include the exact hosted URL, category, explanation, reporter contact details, safe evidence, and technical information required to prevent repeated submissions. Do not download, attach, or email suspected illegal material or live malware merely to make a report.
Reports are triaged by urgency. Credible child-safety concerns, active malware or phishing, non-consensual intimate content, serious threats, and similar immediate risks may cause access to be restricted before the investigation is complete. Repeated independent reports may also trigger a temporary delivery block while an operator reviews the asset; a report count is a triage signal, not by itself a final finding.
When enforcement is required, MediaToURL may disable the file and its links across direct delivery, share pages, variants, transformations, downloads, and verified custom delivery domains; quarantine or remove versions and generated outputs; restrict uploads; suspend or terminate an account or workspace; revoke integration credentials; preserve limited evidence; and report conduct to authorities or rights holders when required or appropriate.
6. Service Providers and International Processing
The independent application is designed to use providers for hosting, authentication, database services, object storage, delivery, email, payments, and related operations. Dedicated production provider accounts for these functions have not yet been provisioned for MediaToURL; the current local preview does not use them to store user uploads or process subscriptions.
Supabase and Cloudflare R2 are planned components of the independent architecture, not a statement that those providers currently process MediaToURL user files. The provider directory will be updated with verified service roles before any such feature is enabled. No Merchant of Record or payment processor is currently connected.
If a payment or integration provider is added later, this policy and the provider directory will identify the relevant data flows before the feature is offered. Do not send payment-card data or third-party credentials to MediaToURL support.
Where applicable law requires safeguards for international transfers, MediaToURL will use a lawful transfer mechanism and appropriate contractual or organizational protections. Nothing in this paragraph promises a particular legal mechanism in every country.
7. Third-Party Integrations
This independent MediaToURL build does not currently offer a Google Workspace add-on or another third-party account integration. It does not connect to Google Drive or process files from another account. If an integration is introduced, its requested permissions, data use, sharing, retention, and revocation path will be described before it is made available.
The public website does not use third-party advertising or analytics integrations in this build. Any later change to that behavior will be reflected in the applicable privacy and cookie information.
8. Retention, Deletion, and Legal Holds
Files and asset metadata are retained while needed to provide the service, honor link settings, maintain versions, enforce quotas, investigate abuse, resolve disputes, or comply with law. Expired, deleted, or disabled content may become inaccessible immediately while technical deletion completes asynchronously.
A file restricted after an abuse report is not automatically deleted merely because it was reported. It may remain in a restricted state for operator review. After a confirmed violation, MediaToURL may permanently remove the asset, versions, variants, and storage objects, while retaining limited report, audit, or legal records when reasonably necessary.
Deletion may be delayed or limited by legal holds, fraud prevention, security investigations, billing records, dispute handling, backup cycles, or another legal obligation. Backups are for service recovery and are not a customer archive or a promise of selective restoration.
9. Privacy Rights and Requests
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a copy of certain personal information. Send requests to [email protected] from the account email when possible. We may verify identity, request clarification, and apply lawful exceptions before completing a request.
A request to delete information does not require MediaToURL to restore content, remove records that must be preserved, or erase information that has already been copied by another person. We may retain a limited record of the request and its outcome for accountability and legal compliance.
10. Security Boundaries and Incident Response
The public website and local previews do not accept cloud uploads in the current configuration. Production storage access controls, hosted delivery checks, and related safeguards must be configured and verified before cloud services are enabled. No online service, CDN, browser, or storage system can guarantee perfect security.
If we confirm a security incident, we will investigate, contain affected access, revoke or rotate credentials where appropriate, preserve relevant evidence, and provide notices required by applicable law. Report suspected account compromise, exposed credentials, harmful files, or platform vulnerabilities promptly.
11. Children, Policy Changes, and Contact
MediaToURL is not directed to children. A person using the service must meet the minimum age required by the law that applies to them and must have any authorization that the law requires.
If we learn that personal information was submitted by a person who could not lawfully provide it without the required authorization, we may restrict the account and remove the information where required by law. A parent, guardian, or other authorized person can contact [email protected] if they believe this situation has occurred.
We may update this policy when the service, providers, legal requirements, or abuse-response practices change. The effective date shown on this page identifies the current version. If a change materially affects how we use personal information, we will provide notice where required.
For privacy, security, abuse, copyright, or account questions, contact [email protected] or use the Contact page. Do not send passwords, secret keys, live malware, or unnecessary sensitive files in a support message.