Privacy policy

Who is responsible

Alper Sentürk is the independent developer responsible for SacredSpeak and the controller of personal data processed to operate it. Timete is the name of this website and app collection; it is not a company or a separate legal entity.

For questions or privacy requests, contact support@timete.lu. This notice covers the app and app support. Visits to timete.lu are covered by the website privacy policy.

SacredSpeak is currently being prepared for public release. This notice describes the app’s current data flow, including access provided through a test build.

What stays on your device

Local storage includes your language and tradition preferences, chat history, reading position, bookmarks, saved passages and personal notes, along with a cache of question usage and purchase status. These are used to let you return to your reading and conversations.

There is no email-and-password registration for SacredSpeak. The online service can create a pseudonymous session and app user identifier for authentication, quotas and purchases. These are linkable identifiers, not a guarantee of anonymity.

What happens when you ask

Before the first AI request, the app asks you to agree to external processing. For an online answer, it sends your question, relevant recent chat context, chosen tradition or figure, language and source information through our Supabase backend. Retrieval and answer generation use OpenRouter and selected AI model services. Some locally available answers may not need an AI request.

Supabase

Hosts the backend that authenticates requests, applies question limits and coordinates retrieval and answers. See Supabase privacy information.

OpenRouter

Routes questions and relevant context to AI processing endpoints, including services running OpenAI or Anthropic models. See OpenRouter’s privacy policy.

AI endpoints

Process the supplied question and context to find or generate relevant material. Requests are configured to use endpoints with no-training and zero-data-retention policies. See OpenRouter’s explanation of these routing controls.

These controls concern AI inference content. They do not mean that billing, authentication, quota or security records disappear immediately.

Questions can be personal

Questions and selected traditions may reveal religious or philosophical beliefs, which receive special protection under data-protection law. Keep questions general where possible and avoid including names, contact details or other sensitive information about yourself or other people.

AI processing is optional. You can decline the prompt and use reading features that do not require an AI request. To request withdrawal, email support@timete.lu. Do not send further online questions while your request is being handled. The current test build does not provide an in-app consent-reset control. Withdrawal does not undo a request that has already been processed.

Paid packages and purchases

No paid service is currently offered. Paid packages are planned for a future release. The information below describes the planned purchase flow and, where present, test-build purchase integration; it is not a current offer.

Apple handles App Store payments. In builds with purchase integration enabled, RevenueCat processes app identifiers and technical information and checks test or purchase entitlements. A free test build can still contact this service. This involves an app user identifier, transaction and product identifiers, purchase dates, subscription status and technical information needed by the purchase service. These identifiers can be personal data even when they do not contain your name.

We do not receive your full payment card details. Purchase verification does not require the content you create in the app. See Apple’s privacy policy and RevenueCat’s privacy policy.

The app’s purchase screen will explain the paid packages and applicable question allowances before you choose one. This policy does not promise a particular price or unlimited questions.

What is kept, and for how long

• Local content: conversations, saved items and notes stay until you remove them using the app’s controls. Delete exported or shared copies separately.
• Operational records: the service keeps pseudonymous request and usage information for quotas, reliability, cost control and abuse prevention. The configured retention targets are 30 days for request metadata, 35 days for daily usage records and 90 days for weekly usage records. Verification that scheduled deletion runs in the hosted test environment is still in progress; these are not yet a verified maximum retention period. These operational tables do not store question or answer text.
• Session and purchase identifiers: may remain separately from those usage records so the service can authenticate requests and restore paid access. Contact support for a deletion request.
• Provider records: hosting, security and purchase providers may retain technical or transaction records under their own policies and applicable legal requirements.
• Support email: kept while needed to resolve your request, handle related follow-up and satisfy legal obligations, then deleted when no longer needed.

Clearing content and contacting support

Use the chat settings to clear conversations. Remove bookmarks and saved notes through their respective screens. Local deletion does not automatically delete backend usage records or purchase history; email a privacy request for information held by us.

When you email support, we receive your email address, message and any files you choose to attach. We use them to answer your request and investigate the issue. Our email service processes this correspondence for delivery and storage.

Send only what is needed. Remove personal or confidential information and other people’s details from screenshots. Support does not need your password, payment card number or backup passphrase.

Legal bases and international processing

Where GDPR applies, optional AI processing requires consent. Processing that reveals religious or philosophical beliefs additionally requires an applicable Article 9 condition, such as explicit consent; merely accepting general terms is not a substitute. The current test-build permission prompt and withdrawal controls remain under review before public release. Future paid access would rely on contract necessity for the purchase service, not as a substitute for consent to optional AI processing. Security, service reliability and abuse prevention rely on legitimate interests; mandatory retention or disclosure relies on legal obligation.

The listed providers operate internationally and may process data outside the EEA, including in the United States. Their privacy information explains their processing and transfer safeguards. Contact us for details about the processing locations, providers and transfer arrangements relevant to your request.

We do not sell questions, use them for advertising or make decisions about your legal rights or eligibility based on your religious beliefs. AI output is provided for your own reading and reflection.

Your privacy rights

Depending on applicable law, you can request access, correction, erasure, restriction or portability of personal data we hold about you. You can object to processing based on legitimate interests and withdraw consent where processing relies on it. Withdrawal does not affect processing already carried out lawfully.

Clearing local content does not automatically delete purchase records or backend identifiers. For data we hold, email support@timete.lu; we may ask for limited information to verify the request. We normally respond within one month, and will explain any lawful extension.

You may complain to your local supervisory authority, including Luxembourg’s Commission nationale pour la protection des données (CNPD).

Younger users

SacredSpeak is not directed at children under 13. A higher local age for consenting to online data processing applies where required; parental authorisation may be necessary. If you believe a child has sent personal data to the service, contact support so we can investigate.

Changes to this policy

We update this notice when the app or its data practices change. The date above identifies this version. Material changes will be brought to your attention in the app or through another suitable notice; we will ask for consent where required.