Your files are yours.We built RuruSpace around that idea.

RuruSpace is built around a simple idea: your files are yours, not ours.

We built RuruSpace so that you can use file and productivity tools without creating an account, building a permanent profile, or handing us a personal library of your documents.

Whenever a tool can run directly in your browser, we prefer that approach. Your file can be processed on your own device without being uploaded to our servers.

Some tools require server-side software or resources. For those tools, your file may temporarily travel to our server so that the requested operation can be performed. Those files are treated as temporary processing data rather than permanent user storage.

This is the most important part of this policy.

Files processed in your browser

Many RuruSpace tools are designed to run locally in your browser. When you use one of these tools, the file can remain on your device while JavaScript performs the requested operation.

In that situation, RuruSpace does not need to receive the contents of your file at all.

Files processed on our server

Some operations depend on server-side programs such as media, document, PDF, or conversion software. When one of these tools requires server processing, the selected file is temporarily sent to the processing environment.

The server stores the temporary processing data only for the time required to perform the operation. The current server-side implementation places a hard maximum lifetime of approximately 60 seconds on a processing job, including when a request fails or is interrupted.

Temporary processing directories are recursively removed when the job is destroyed. This is designed to prevent processed files from becoming permanent application storage.

What we do not do with your files

• We do not sell your uploaded files.
• We do not use uploaded files for advertising.
• We do not build a user profile from your documents.
• We do not intentionally store uploaded files in the application database.
• We do not intentionally keep processed output as a permanent download library.
• We do not create an account containing your file history.

Even when a server-assisted tool is required, the purpose of receiving the file is to perform the operation you requested — not to create a permanent copy of your content.

Privacy does not mean pretending that a website processes absolutely no information. RuruSpace needs a small amount of operational data to keep the service reliable and maintain the application.

We separate this operational information from the contents of your files.

Operational usage information

When database-backed analytics are enabled, RuruSpace can maintain aggregate counters such as how many times a particular tool was used on a particular day, how many of those runs failed, and aggregate processing time.

These counters are intended to answer questions such as: "Which tools are being used?" and "Is a particular tool failing?" They are not designed to identify individual users.

Error information

RuruSpace can also record limited technical error information so that broken tools can be diagnosed and fixed.

Before an error message is persisted, the application attempts to remove recognizable filenames, file paths, and other information that could unnecessarily expose file-related details.

Error messages are also limited in length. The goal is to keep enough information to understand a software failure without turning the error system into a repository of user content.

What is not stored as usage analytics

• Your uploaded document contents.
• Your processed file contents.
• A permanent list of files you have processed.
• A personal account history.
• A profile containing your tool activity.

RuruSpace does not require you to create an account to use its normal tools.

There is no mandatory sign-up process, no user profile that needs to be completed, and no requirement to upload personal information before using the service.

Because normal tool usage does not depend on a user account, we do not need to maintain a personal file history tied to an account.

This is intentional. We would rather remove an unnecessary data collection step than ask for information simply because other websites traditionally do so.

RuruSpace is designed to work without requiring advertising or tracking cookies.

Some browser functionality may use temporary browser mechanisms such as memory buffers, Blob URLs, or other client-side objects required to process a file or provide a download.

These mechanisms are different from permanent cloud file storage. For example, a browser-created object URL can point to a file that exists locally in your browser session. RuruSpace can revoke those URLs when the corresponding output is no longer needed.

You should nevertheless understand that your browser itself is controlled by your browser vendor and operating system. RuruSpace cannot control information independently collected by the browser, extensions, DNS provider, operating system, or other software installed on your device.

We do not want RuruSpace to become a surveillance product.

The application is designed around minimal, privacy-conscious operational analytics rather than individual behavioral tracking.

Where database-backed usage analytics are enabled, the application records aggregate tool statistics rather than maintaining a detailed browsing history for individual visitors.

We do not need to know which PDF you opened, what the document contained, or which personal information appeared inside a file in order to know that a PDF conversion tool is being used.

Rate limiting

Server-assisted tools may also use rate limiting to protect the service from abuse and excessive automated requests.

The current implementation derives a short-lived salted hash from the caller's network address for rate-limiting purposes rather than keeping the raw IP address as the rate-limit key.

This mechanism exists for service protection, not for building a marketing profile about you.

Some RuruSpace features may rely on third-party libraries, infrastructure, content-delivery services, or external processing resources.

A third-party dependency may process technical network information as part of delivering a web page or resource. RuruSpace does not control the privacy practices of an independent third party once information is processed by that third party.

We aim to keep third-party dependencies limited and to avoid sending your uploaded content to an external service unless the specific tool requires it.

If a future RuruSpace feature sends data to a third-party service for processing, we intend to identify that behavior clearly in the relevant tool or documentation rather than quietly treating it as ordinary browser processing.

Privacy and security are closely connected. Minimizing the amount of information we keep reduces the amount of information that could be exposed later.

RuruSpace uses multiple technical controls intended to reduce unnecessary exposure of user data.

• Temporary server-side processing instead of permanent file storage.
• Automatic expiration of server-side processing jobs.
• Deletion of temporary processing directories.
• No requirement for user accounts for ordinary tools.
• Validation of uploaded files before server-side processing.
• Rate limiting for server-assisted endpoints.
• Security headers and content-security controls.
• No caching of processed uploads through the processing endpoint.
• Scrubbing of recognizable filenames and paths from persisted errors.

No internet service can honestly promise perfect security. We continuously work to reduce the amount of sensitive information that exists in the first place and to protect the systems that do need to process it.

Different kinds of information have different lifetimes.

We do not use a single "everything forever" retention model. The objective is to keep temporary user content for as little time as technically necessary while retaining limited operational information where it is genuinely useful for running the service.

RuruSpace is a general-purpose utility service. It is not designed specifically for children and should not be used to process information that a child should not be sharing online.

Parents and guardians should help younger users understand what information they are uploading to any online service, including RuruSpace.

You should have meaningful control over your information.

Because RuruSpace does not require an ordinary user account and does not maintain a personal file library, there is generally no account dashboard containing your uploaded files that you need to manage.

If you believe RuruSpace has retained personal information about you or you have a privacy question, you can contact the service operator using the contact details published on the website.

Depending on where you live, you may have additional legal rights concerning personal information, including rights relating to access, correction, deletion, restriction, objection, or data portability. The availability of a particular right depends on applicable law and your circumstances.

RuruSpace may change this Privacy Policy when the service, infrastructure, features, or applicable legal requirements change.

When we make a significant change to the way we handle personal information, we will update this page and revise the effective date shown at the top.

We encourage you to review this page occasionally, especially before using a new feature that handles sensitive information.

Privacy should not require you to guess what a service is doing.

If something about RuruSpace's data handling is unclear, we would rather explain it than hide it behind complicated legal language.

For privacy questions, concerns, or requests, please use the contact method provided on the RuruSpace website.