Privacy policy

1. Who this policy covers

x1 technologies is responsible for the Svelo website and app service and acts as the data controller. Full business details and the postal address appear at the end of this document. For privacy, data-access or support requests, contact contact@svelo.cloud.

This website provides information. It does not sell subscriptions, take payments or collect mailing-list registrations. App descriptions concern features available in the version made available to you; a description does not mean the app is already publicly available in a store.

Svelo is intended for people aged 16 or over. We do not direct the service or advertising at children under 16. If you become aware that a person under 16 has provided us with data, contact us so we can investigate and take appropriate action.

2. Visiting the website

Your browser sends infrastructure providers information needed to deliver the page and secure the connection, including your IP address, request time, requested resource and basic browser and device information. Sites/OpenAI and Cloudflare provide website infrastructure. Hostinger provides infrastructure for the app API.

We do not add behavioural advertising or visitor-tracking analytics. We do not sell data or build advertising profiles of visitors. Necessary technical delivery and security are separate purposes.

The informational website does not set its own analytics or advertising cookies. The separate secure account-deletion process uses necessary session cookies on the API domain. They do not track activity across other websites. Store links and other external links open services operated under their own privacy policies.

3. Information stored on your device

Before you begin, the app asks you to declare locally whether you are at least 16. The age category stays in secure device storage; we do not collect your birth date or send this declaration to the server. This is a user declaration, not document, identity or parental-consent verification. Until the minimum age is confirmed, documents and support remain available and other app functions stay blocked.

Svelo can store tasks, plans, notes, drafts, focus-session history, energy and work feedback, settings and recovery information on your device. The local app database is encrypted and its key is protected by the operating system’s secure storage.

Saving a task or note locally does not itself send its contents to our server. Operating-system backups, files you export and subsequent sharing depend on the settings and services you choose.

We do not need diagnoses, medical records or other particularly sensitive information. However, content you enter may contain such information. Before sending anything to the cloud, remove unnecessary sensitive information and other people’s data you are not entitled to disclose.

4. Accounts and technical identifiers

You can link an account using Apple or Google sign-in. We receive identity confirmation and a provider account identifier and, depending on the sign-in method, basic information the provider shares. We do not receive your Apple or Google password. The main server-side account binding uses a provider identifier rather than a password.

Online features use installation and session identifiers, token hashes and a pseudonymous purchase identifier. These help route responses to the correct device, renew sessions securely, prevent repeated operations and enforce limits. Some are also created when you use a cloud feature without creating an account.

Signing in does not authorise uploading your entire local history. The app presents available options before associating local data with an account, and content synchronisation requires a separate opt-in.

5. Optional synchronisation

When you enable synchronisation and Pro access is verified, selected planning information, tasks, notes, completed sessions, outcomes and related settings and history can be sent to the server to restore them on another device. Active sessions, unsent drafts, passwords, provider tokens and the local calendar cache are outside content synchronisation.

Turning synchronisation off stops further content uploads. It is not a request to delete history already stored on the server. Losing Pro does not delete existing history either; downloading and reviewing existing history remains available through the app’s supported functions.

Separately from paid content synchronisation, the app may exchange limited operational records such as Pro-suggestion preferences and records of a prompt already shown or dismissed. This stream contains no task text or private notes. Among other things, it prevents repeated dismissed prompts.

Local database encryption and HTTPS do not amount to end-to-end cloud encryption. We do not describe Svelo synchronisation as a service where the provider is technically unable to process the content you send.

6. AI planning and transcription

You start AI functions after confirming the transfer. The selected request and context needed to fulfil it, such as selected tasks, availability and planning preferences, are sent to our API and then to OpenAI. The result is a proposal for you to review and approve before changing your plan.

Transcription requires selecting a recording or recording your voice after microphone permission. Only audio selected for transcription is uploaded; each recording is limited to 180 seconds and 20 MiB. We do not continuously listen. Server temporary files are removed after handling, including error paths; abandoned temporary files are scavenged after one hour.

We use the OpenAI API rather than a public chat. API data is not used to train OpenAI models by default. Planning requests use store:false. This does not mean zero provider retention: standard abuse-monitoring logs for text requests may be kept for up to 30 days, subject to legal and security exceptions. Current transcription-endpoint documentation specifies no application-state or abuse-monitoring retention for submitted audio.

Do not send AI content you do not wish to entrust to an external provider. Declining a transfer does not disable manual planning. Results may be incomplete or incorrect; we do not use them to make decisions producing legal or similarly significant effects on you.

7. Calendar, notifications and device permissions

Microphone, calendar and notification access depend on operating-system permission, which you can change in device settings. A system permission is not, by itself, consent to every further processing purpose.

Calendar integration reads selected calendars to display busy periods during planning. It does not write events to your calendar. Local access does not automatically upload your entire calendar to the server.

Your operating system handles local notifications. If you enable server notifications, we store an APNs or FCM token, platform, language, preferences and the link between the device and the current session. Apple and Google deliver the messages. Svelo remote notifications use general content; showing private titles in local reminders is a separate setting.

Marketing messages require a separate opt-in. You can disable them without losing the core service. Widgets and Live Activities, where supported, display selected session information on your device.

8. Purchases and payment information

Subscriptions are purchased through the App Store or Google Play. The store handles payment and billing information. RevenueCat helps verify purchases and Pro access, processing purchase identifiers, transaction, product and subscription-status information and technical information needed by its SDK. Svelo does not receive your full payment-card number.

Svelo’s server stores an entitlement-verification result and the minimum information needed to provide features. Deleting a Svelo account does not cancel store renewal. Manage renewal in your Apple or Google subscription settings.

9. Purposes and legal bases

• Contract performance and steps you request — GDPR Article 6(1)(b): accounts, requested online features, enabled synchronisation, AI requests and Pro entitlement handling.
• Our legitimate interests — GDPR Article 6(1)(f): secure website and app delivery, abuse and duplicate-operation prevention, service continuity, correspondence and establishing or defending claims. We limit data to the relevant purpose; you can object on grounds relating to your particular situation.
• Consent — GDPR Article 6(1)(a): separate optional purposes, particularly marketing you enable. You can withdraw consent for the future without affecting the lawfulness of earlier processing.
• Legal obligations — GDPR Article 6(1)(c): data-subject rights, consumer obligations and legally required records, to the extent those obligations apply to us.
• Data for an optional feature is not required for manual planning. Without information essential for a particular request, we cannot fulfil that request.

10. Providers and international transfers

Authorised Svelo personnel and providers necessary for your selected function may process data: Sites/OpenAI and Cloudflare for the website, Hostinger for API infrastructure, Apple or Google for sign-in and distribution, RevenueCat for purchase verification, APNs/FCM for push delivery and OpenAI for AI functions you choose. Titan, our email provider, handles messages you send us. Each provider does not receive every category of data.

Some providers operate outside the European Economic Area or use subprocessors in other countries. Entrusted processing requires appropriate agreements and, where data is transferred, a basis under GDPR Chapter V, such as an applicable adequacy decision or standard contractual clauses. Contact contact@svelo.cloud for information about safeguards relevant to your data. We do not claim that all data remains exclusively in the EU.

Stores, identity providers and other organisations may also act as independent controllers for their own obligations and security. Erasing information from Svelo does not replace exercising your rights with those organisations.

11. How long information is kept

Local information remains on your device until you delete it in the app, remove its profile or remove app data through the operating system. Exports and device backups may remain wherever they were saved.

Account information, synchronised history and minimal records needed for consistency, consent and duplicate-operation prevention are kept while the account is maintained or until an effective erasure request, subject to necessary legal exceptions. Deletion markers prevent deleted data from reappearing during later synchronisation.

AI-planning and transcription results remain available on the server for up to 24 hours, after which server maintenance removes their content. AI-request content is removed when handling completes or fails. Browser account-deletion verification records are deleted one day after their expiry. An expired access token or push binding stops authorising operations; expiry does not itself erase all operation metadata.

Minimal identifiers, request hashes and technical records may remain after a result expires to handle retries, establish operation status and prevent account confusion or duplicate charges. Account-associated records are removed through account deletion, except for a limited deletion confirmation and necessary legal records. The pre-release version does not yet have a single automatic erasure period for all technical history; we do not equate its retention with token validity or 24-hour result availability.

Backups are isolated from ordinary use and support recovery after failure. Deleting a record from the active database does not immediately delete every backup; completed erasure requests must be respected before restoring data to service. The pre-release version does not yet have uniform automatic rotation for all older backups. Infrastructure, store and AI providers also have their own retention rules. Contact us about a particular copy or restriction of its use.

Correspondence is kept until the matter is resolved. If a specific record is needed afterwards for a legal obligation or an actual dispute, we restrict retention to the required information and the applicable statutory period or resolution of the matter. We will explain a relevant restriction or exception when responding to a data request.

12. Deletion, export and your rights

The app provides export, synchronisation controls and account deletion after fresh identity confirmation. The account-deletion website supports existing Google-linked accounts. Browser deletion for Apple-linked accounts is currently unavailable; use the app or contact us. Additional private narrative is not required for us to consider a request.

Deletion covers the specified account, its data on our server and the local profile handled by that process in the app. It does not remotely erase independent local copies on another phone, previously exported files or provider records they must retain. The deletion receipt shows the operation status; managing a store subscription is a separate action.

You have rights of access and a copy, correction, erasure, restriction, portability where applicable, objection to legitimate-interest processing and withdrawal of consent. We may need proportionate identity confirmation before fulfilling a request. Do not send your Apple or Google password.

We normally respond within one month. For complex or numerous requests, the law permits an extension of up to two further months; we will explain the reason within the first month. You can complain to Poland’s President of the Personal Data Protection Office at uodo.gov.pl or the competent authority where you live or work.

13. Security and policy changes

We use encrypted connections, access controls, separation of accounts and devices, secure local-key storage and controls against duplicate operations and abuse. No service can guarantee complete absence of risk. Protect your device lock, updates and store account.

The current policy is available here with its update date. We will give appropriate notice of material changes in how your data is used. A new purpose requiring consent will not be enabled merely by changing this document.