Privacy Policy

This Policy applies to the Qryvios website/application, its guest and registered account flows, dataset upload and processing, backend SQL execution, query history, charting and export features.

It does not automatically apply to third-party sites or services you reach through external links, or to independent recipients with whom you share exported files.

The operator is responsible for personal information it collects for account administration, security, product operation, support and service improvement.

When users upload datasets containing personal information about other people, the operator may act as a processor/service provider on the user's behalf depending on applicable law and contractual context. The exact legal role should be confirmed for target jurisdictions and enterprise customers.

Users remain responsible for determining whether they are permitted to collect, upload, query, visualize and export personal information contained in their datasets.

• Provide and authenticate guest and registered sessions.
• Associate datasets, queries and results with the correct owner identity and prevent cross-user access.
• Upload, validate, normalize, store and make datasets queryable.
• Validate SQL, queue and execute read-only analytical queries, store results and provide user-specific query history.
• Create chart/result views and support client-side exports.
• Maintain security, detect misuse, enforce technical limits, troubleshoot failures and operate monitoring/alerts.
• Provide support and communicate service or policy changes.
• Improve performance, reliability and user experience using operational metrics that should avoid unnecessary raw dataset content.

Depending on applicable law, processing may rely on performance of a contract or steps requested by the user, legitimate interests in operating and securing the Service, consent where specifically requested, and compliance with legal obligations.

If the Service is offered in a jurisdiction that requires more specific legal-basis disclosures, the operator must tailor this section before publication.

Registered authentication is handled through Amazon Cognito.

Identity mappings, principal profiles, dataset metadata and query execution/history metadata are designed to be stored in DynamoDB.

Raw uploads, processed datasets, previews and full query-result artifacts are designed to be stored in Amazon S3.

SQS is used for asynchronous job delivery and should carry minimal identifiers/metadata rather than full dataset content.

CloudWatch and related AWS observability services may process logs, metrics and alarms.

The operator should document the AWS region(s) and production environment locations before publication.

Cloud infrastructure and service providers may process information on the operator's behalf as needed to provide the Service. The current architecture relies primarily on Amazon Web Services.

Information may be disclosed when required by law, legal process, government request or to protect rights, safety, security and the integrity of the Service.

Information may be transferred in connection with a merger, acquisition, financing or sale of business assets, subject to applicable law and appropriate notice where required.

The operator does not intend to sell uploaded datasets or query content for advertising. If the business model changes, this Policy must be updated before such use occurs.

Cloud services may process information outside the user's country. Before production publication, the operator should identify hosting regions and, where required, describe applicable cross-border transfer safeguards or contractual mechanisms.

The Service is designed to use owner-scoped authorization based on a backend-resolved principal identity, rather than trusting user-supplied ownership identifiers.

S3 should use block-public-access and encryption; uploads should use short-lived pre-signed URLs rather than exposing permanent AWS credentials.

DynamoDB and other managed stores use server-side encryption according to configured AWS settings.

SQL execution is restricted to an approved read-only analytical subset and should prevent arbitrary filesystem/network/extension access.

Least-privilege IAM, rate/concurrency limits, structured logging and alerting are used or planned as part of the production hardening baseline.

No security control eliminates all risk. Users should avoid uploading data that exceeds the Service's approved sensitivity/compliance scope.

Depending on your location and applicable law, you may have rights to request access, correction, deletion, restriction, objection, portability, withdrawal of consent, or information about processing.

Registered users should be able to request account and associated-data deletion through [ACCOUNT DELETION METHOD / SUPPORT PROCESS].

Users can export their own resolved query/chart data using supported export tools. Product exports are not necessarily a complete statutory privacy-data export and should not replace a formal privacy request process where required.

The operator may need to verify identity before fulfilling a privacy request and may retain limited information where required by law or necessary for security/fraud prevention.

Guest users do not necessarily have a verified email identity. The visible Guest ID alone is not sufficient proof that a requester owns the associated resources.

To access, recover or delete guest-owned information, the Service may require the active secure guest session, a valid Secure Guest Access credential/access code, or another verification method implemented by the operator.

If the guest identity has been linked to a registered account, privacy requests should generally be handled through the registered account while preserving any necessary Guest ID audit reference.

The Service may use an essential secure guest-session cookie, including a Secure HttpOnly cookie where deployment topology allows, to maintain guest ownership across requests.

Cognito authentication may use browser/session mechanisms required for login and token/session handling according to the selected integration.

Theme preference and chart/dashboard configuration may be stored in localStorage or similar browser storage in the current release.

This draft assumes no advertising or behavioral-targeting cookies. If analytics, advertising or optional tracking tools are added, the cookie disclosure and consent approach must be updated before deployment.

The Service is not intended for children below [MINIMUM AGE]. The operator should choose the correct age threshold and parental-consent approach for the markets in which the Service is offered.

The Service performs automated data processing and SQL execution but is not currently designed to make legally significant automated decisions about individuals. If that changes, this Policy must be updated.

The operator will investigate suspected security incidents and provide notifications to affected users or authorities where required by applicable law and based on the nature of the incident.

The operator may update this Policy to reflect product, provider, legal or business changes. Material changes should be communicated through the Service, email or another reasonable channel where required.

Privacy contact: [PRIVACY EMAIL]

Operator: [OPERATOR / COMPANY LEGAL NAME]

Address: [REGISTERED / BUSINESS ADDRESS]

Data protection officer / representative (if required): [DPO / REPRESENTATIVE DETAILS]

Users may also have the right to complain to their local privacy/data-protection authority where applicable.