Privacy Policy
i-Will does not send your vault content to any server. Your notes, voice recordings, files, and access details stay on your device. Text content is encrypted by the app; voice, video and files are protected by iOS device data protection. The server layer carries only the operational control metadata strictly required to run the service: account identity, device ownership, protocol state, and notification delivery. This policy explains what is processed, where, why, and what rights you hold.
1.Data Controller
Under Article 13 of the EU General Data Protection Regulation (GDPR) and Article 10 of Turkey's Personal Data Protection Law No. 6698 (KVKK), the data controller for personal data processed in connection with i-Will is:
Nexalent
Website: nexalent.com.tr
Email: info@nexalent.com.tr
Subject line: GDPR Request or Privacy Request
Nexalent is considered to qualify for the small-scale enterprise exemption from mandatory registration with the Turkish Data Controllers Registry (VERBİS) under KVKK and related regulations. This exemption does not affect compliance with other obligations under KVKK.
2.Categories of Personal Data Processed
i-Will operates across two distinct data layers. The tables below clarify this separation.
A. Data Stored Locally on Your Device, Never Sent to Servers
| Data Category | Description | Storage Location |
|---|---|---|
| Vault notes | Text content added by the user | Device only (cryptographically encrypted) |
| Voice recordings | Audio messages recorded inside the app | Device only (protected by iOS device data protection; not additionally encrypted by the app) |
| Files and photos | Media files added to the vault | Device only (protected by iOS device data protection; not additionally encrypted by the app) |
| Access details | Passwords, account notes, structured credentials | Device only (cryptographically encrypted) |
| Recipient list | Names and email addresses of trusted contacts. The full recipient list remains on the device in encrypted form. | Device only (cryptographically encrypted). One exception applies to the recipient marked as Guardian; see section B. |
| Encrypted backup file | Portable backup exported by the user | Under user control (device or external storage) |
B. Metadata Processed on Servers for Service Operation
| Data | Purpose | Legal Basis (GDPR) |
|---|---|---|
| Account email address, delivery mailbox address and name | Account mapping and system emails. The account identifier is derived from a one-way HMAC digest of the email address. So that grace notices and pause confirmations can be sent even when the phone is off, the account email, delivery mailbox address and name are also stored on the server in plain text; they are closed to direct client access and deleted when the account is deleted. | Art. 6(1)(b): Contractual necessity |
| Installation ID | Enforcing the single active device rule and managing device conflict resolution | Art. 6(1)(b): Contractual necessity |
| Protocol status | Tracking Safe / Amber / Red / Grace / Suspended states | Art. 6(1)(b): Contractual necessity |
| Last check-in timestamp | Correct operation of the heartbeat tracking system | Art. 6(1)(b): Contractual necessity |
| Push notification token | Delivering critical alerts via APNs | Art. 6(1)(b): Contractual necessity |
| Email provider connection status | Monitoring Gmail / Outlook connection health | Art. 6(1)(b): Contractual necessity |
| Subscription plan | Controlling access to Premium features | Art. 6(1)(b): Contractual necessity |
| Language preference | Delivering system messages in the user's language (Turkish, English, German, Dutch or Japanese) | Art. 6(1)(b): Contractual necessity |
| Grace period metadata | Managing the 24-hour final control window flow | Art. 6(1)(b): Contractual necessity |
| Grace window link tokens | Validating the Trusted Contact's and the user's pause links. Tokens are generated randomly for each grace window, are valid only while that window is open and are deleted with the grace record 90 days after it closes. | Art. 6(1)(b): Contractual necessity |
| Guardian name and email address | So the final-window notice can reach the Guardian by email even if the user's phone never wakes up. Kept only while protection is on; the server record is deleted when protection is turned off, when the Guardian is removed or changed, and once delivery is complete. If the user turns on Asking After You, a gentle email goes to the Guardian when there has been no check-in for the chosen number of days; for this the server keeps only the feature's settings and timing: whether it is on, the threshold, the email language, the next check time, a counter, the times of the introduction email, the last email, a failed attempt (with its technical reason) and an opt-out, and a one-way hash of the opt-out link. The Guardian's address is not stored for this feature. The phone supplies the address for each email at the time of sending, so this email can be sent only when the phone can be reached. The record of each grace window (two email addresses and two names) is deleted 90 days after the window closes. | Art. 6(1)(b): Contractual necessity |
| Recipient-derived delivery metadata | Limited operational metadata such as recipient count, primary guardian identifier, and masked guardian email data, used only to operate delivery and guardian flows. Full recipient content is not stored on servers. | Art. 6(1)(b): Contractual necessity |
| Scheduled letter schedule | For letters scheduled for a future date: the letter and recipient identifiers, the scheduled date and time zone, the delivery status, the times of delivery attempts and, if an attempt fails, its technical reason. Used so that delivery can be completed and confirmed. The title of the vault item is not stored on the server; if an app version includes it when syncing the schedule, the server discards it. | Art. 6(1)(b): Contractual necessity |
| Vault item count (aggregate) | Growth signalling and capacity planning; contains no content information | Art. 6(1)(f): Legitimate interest |
| Optional Daily Companion personalisation context | When enabled by the user: first name, language, tone, scheduled local delivery time, abstract weather category, temperature band, and selected city/country; if the user also turned on Personal Ritual integration, the day's locally calculated rhythm summary (area scores, a few sky signals and the local ritual line, without birth date, time or place). Coordinates are used only to request a forecast from Apple WeatherKit and are not sent to the AI provider. Vault content, recipient data, email data, IP-derived location, and precise device location are not included. | Art. 6(1)(a): Consent |
| Optional Personal Ritual AI context | When enabled by the user: language, tone, narrow astrological placement/aspect/confidence signals calculated on device, ritual axis scores, local ritual copy, and message hashes used to reduce repetition. Birth date, birth time, birth city, coordinates, vault content, and recipient information are not sent to the AI provider. | Art. 6(1)(a): Consent |
| Optional Heart Circle connections | When the user adds someone to their Heart Circle: a random link identifier showing that two accounts are paired, the pairing date, the mute preference, daily sending counters, each side's last heart time (to limit repeated sending to once every 15 minutes) and the pair's shared heart streak and weekly heart count. Invitation codes are kept only as one-way hashes; link invitations are valid for 24 hours and QR invitations for 10 minutes, and they are deleted after they expire. The display name the user chooses is kept while the connection exists and is shown only to the person in that connection (including as the title of heart notifications). When someone is removed from the circle or reported, a block record is kept that only shows the two accounts cannot pair again; for reports, the reporting and reported account identifiers, the reason and the date are kept to prevent abuse. Nicknames given to people are kept only on the device. So the screen opens quickly, the latest copy of the circle list (link identifiers, display names and counters) and the heart history with each person (only intent, direction and time; never message text) are also kept only on this device and are deleted when the user signs out. Nicknames, Heart Circle settings and this history are included in the encrypted iWill backup the user creates; photos are not included. A photo the user chooses for a person in the circle is stored only on this device, encrypted, and is excluded from device backups; it is never uploaded to our servers and is not shown to anyone else. No email address, phone number, contacts, or location is used. When a Premium user sends a heart, only the chosen intent, the time of day, the recipient's language and, if the user enabled it, the day's sky sign are sent to the AI provider; no names are sent. | Art. 6(1)(b): Contract |
Vault content (notes, recordings, files, and the full recipient list) is never stored on Nexalent's servers and cannot be read by Nexalent. The server layer holds only the limited operational metadata listed above, including certain recipient-derived delivery metadata that is necessary to run guardian and delivery flows. The titles of vault items, including scheduled letters, are not stored on the server either.
3.Purposes of Processing
Personal data is processed solely for the following legitimate purposes, limited to what is strictly necessary and proportionate for each:
- Account creation, identity verification, and enforcement of the single active device rule
- Correct operation of the heartbeat protocol (timing, state transitions, notification orchestration)
- Enabling email delivery flows (system messages, guardian notifications, and user-configured outbound delivery messages)
- Delivering push notifications to the device
- Generating optional Daily Companion messages and adapting them to the selected tone, scheduled time, and weather context
- Enriching optional daily and weekly Personal Ritual copy with narrow ritual signals calculated on device
- Setting up optional Heart Circle pairings and delivering heart notifications to the people the user chooses
- Subscription and voucher validation
- Technical fault detection and service reliability
- Compliance with legal obligations
4.Legal Bases for Processing
All processing activities rely on one of the following legal bases under GDPR Article 6 (and the corresponding provisions of KVKK Article 5):
- Contractual necessity (GDPR Art. 6(1)(b) / KVKK Art. 5(2)(c)): Processing required to provide the core service: account management, protocol operation, notification delivery.
- Legitimate interest (GDPR Art. 6(1)(f) / KVKK Art. 5(2)(f)): Aggregate technical data used to improve service quality and reliability; limited to what does not override your fundamental rights and freedoms.
- Legal obligation (GDPR Art. 6(1)(c) / KVKK Art. 5(2)(ç)): Processing required to comply with applicable law or a lawful request from a competent authority.
- Consent (GDPR Art. 6(1)(a) / KVKK Art. 5(1)): Where none of the above bases apply, explicit consent may be sought. Such consent may be withdrawn at any time without affecting the lawfulness of prior processing.
5.Email Provider Connections and OAuth
When you connect a Google (Gmail) or Microsoft (Outlook) account, authorisation is handled via the OAuth 2.0 protocol. Within this connection:
- Your verified email address is retrieved for identity verification purposes.
- For Gmail, only email sending permission (gmail.send) is requested. For Outlook, sending (Mail.Send) and draft creation (Mail.ReadWrite) permissions are requested so that large attachments can be sent; i-Will uses this only for the delivery drafts it creates itself. Your inbox, contacts, calendar, mailbox history, and message contents are never read.
- Connected email providers are used only to send messages created by the user in advance, from the user's own connected account, to the recipients selected by the user, when a user-configured scheduled or protocol condition is met.
- OAuth access and refresh tokens are stored in the secure Keychain on your device. Nexalent's servers do not store your tokens.
- Nexalent does not and cannot read the content of your emails.
- Google or Microsoft user data obtained through OAuth is not used for advertising, user profiling, model or AI training, sale to data brokers, or any unrelated secondary purpose.
- The email provider connection can be removed at any time via Settings > Email Integration inside the app. When the connection is removed, locally stored OAuth tokens are deleted from the device and email sending stops until the user authorises again.
Google's and Microsoft's own privacy policies apply independently to their respective services. These can be found on the respective providers' official websites.
6.Third-Party Providers and International Data Transfers
The following third-party infrastructure providers are used to operate i-Will. Only the minimum data required for the service is transferred to each; vault content is never transferred.
| Provider | Purpose | Data Centre / Country | GDPR / KVKK Safeguard |
|---|---|---|---|
| Google Firebase (Firestore, Functions, App Check) | Control plane metadata, cloud functions, push token management | europe-west1 (Belgium), Google LLC (US entity) | Google processes data under EU Standard Contractual Clauses (SCCs) and the Google Cloud Data Processing Addendum. GDPR compliant. |
| Email delivery service (SMTP) | Sending system emails from i-Will's own mailbox: final-window notices to the user and the Guardian, pause confirmations, Asking After You emails, and internal service alerts to Nexalent | Infrastructure of the mail service provider used by Nexalent | Only what is needed to deliver each message is transmitted: the recipient's email address, the names shown in the message and the message text, including any secure pause or opt-out link. Vault content is never included. International transfers follow the note below. |
| Apple (APNs) | iOS push notifications | Apple Inc. infrastructure (US) | Subject to Apple's own privacy policy and Apple Developer Agreement. Only the notification token and message payload are transmitted. |
| Google (OAuth / Gmail API) | Google account connection and email sending | Google LLC (US) | Governed by Google OAuth and API Terms of Service. SCCs apply. |
| Microsoft (OAuth / Graph API) | Outlook account connection and email sending | Microsoft Corporation (US) | Governed by Microsoft Services Agreement and Data Protection Addendum. SCCs apply. |
| Apple (App Store / StoreKit) | Subscription and payment processing | Apple Inc. (US) | Subject to Apple's App Store privacy policy. Payment data is not visible to Nexalent. |
| Apple WeatherKit | Retrieving forecast data for a city manually selected by the user | Apple Inc. infrastructure | The selected city's coordinates and target forecast time are transmitted to WeatherKit. Device location permission and IP-based location inference are not used by i-Will. |
| Google Gemini API | Primary generation of optional Daily Companion, Personal Ritual and Heart Circle copy, and a safety check of the generated text | Google LLC infrastructure | This route uses Google's unpaid (free-tier) Gemini API service. Under Google's terms for unpaid services, Google may use the submitted context and the generated text to provide, improve and develop its products and services, including machine learning technologies, and human reviewers may read them. No data processing agreement with Nexalent covers this route. For this reason only the minimum, non-identifying context described in Section 2 is sent: no names, email addresses, account identifiers, vault content or recipient data. |
| Groq API | Fallback generation of optional Daily Companion and Heart Circle copy when the primary provider is unavailable | Groq, Inc. infrastructure (US) | Only the same minimum personalisation context is transmitted. Vault content and recipient data are excluded. Provider terms and international-transfer safeguards apply. |
| Anthropic Claude API | Fallback generation of optional Daily Companion, Personal Ritual and Heart Circle copy when the primary provider is unavailable | Anthropic PBC infrastructure (US) | Only the same minimum personalisation context is transmitted. Vault content and recipient data are excluded. Provider terms and international-transfer safeguards apply. |
| Microsoft Azure OpenAI Service | Last-resort fallback generation of optional Daily Companion, Personal Ritual and Heart Circle copy when the other providers are unavailable | Microsoft Corporation infrastructure | Only the same minimum personalisation context is transmitted. Vault content and recipient data are excluded. Provider terms and international-transfer safeguards apply. |
Most of the providers listed above are US-based entities and process data outside the European Economic Area. Transfers are carried out under Standard Contractual Clauses (SCCs) pursuant to GDPR Article 46(2)(c) and/or the relevant provider's data processing addenda. For users in Turkey, these transfers are made under KVKK Article 9 on the basis of user consent and/or the relevant provider's data protection commitments. Such transfers are technically necessary for the operation of the service. The Gemini route is the exception described in the table: Google's terms for unpaid services apply to it instead of a data processing agreement, so only non-identifying context is sent to it.
7.Posthumous Data and Protocol Delivery
i-Will provides a protocol service that can deliver vault content to designated recipients when user-defined conditions are met. The following points apply:
- Vault content is delivered to the recipients designated by the user, based on prior explicit instructions given by the user within the app.
- Nexalent cannot independently determine whether delivered content qualifies as "estate data" or a "testamentary disposition" under GDPR, KVKK, or any other applicable law. Given the legal uncertainty in this area, users are encouraged to seek professional legal advice regarding estate planning and inheritance.
- Once delivery has been made, any processing of the delivered content by recipients falls outside Nexalent's control and responsibility.
8.Retention Periods
| Data | Retention Period | Deletion Trigger |
|---|---|---|
| Local vault data on device | Until the user deletes it or uses "Delete Everything" | User request or app removal |
| Server-side control metadata | While the account is active + 30 days after account deletion | "Delete Account and All Data" action |
| Deletion record | When an account is deleted, the server keeps only the one-way account identifier and the random installation IDs of its devices, so an old device cannot recreate the deleted account. No email address, name or other data is kept. Basis: GDPR Art. 6(1)(f) / KVKK Art. 5(2)(f), honouring the deletion request. | Deleted automatically after 1 year |
| Push notification token | Until device change or account deletion | Device takeover or account deletion |
| Grace period record | 90 days after grace completion (operational log) | Automatic purge |
| OAuth tokens | Until the connection is removed or the account is deleted | User removes connection or deletes account |
| Encrypted backup file | Under user control; not stored by Nexalent | User manages at their own discretion |
| Daily Companion generation context | Processed transiently for generation; recent message hashes and quota/cache records may be retained for repetition prevention and service reliability | User disables the feature, account deletion, or automatic cache/quota expiry |
| Personal Ritual AI context | Processed transiently for generation; accepted output, message hashes, and quota/cache records may be retained for a limited period for daily or weekly repetition prevention and service reliability | User disables the feature, account deletion, or automatic cache/quota expiry |
| Heart Circle links | Connection and display name: until the person is removed or the account is deleted; block record: until the account is deleted; report record: up to 1 year for abuse review; unused invitations until they expire; daily sending counters for 3 days | Removal from the circle, account deletion, or automatic expiry |
9.Security Measures
Nexalent applies the following technical and organisational measures to protect personal data:
- Vault text content is encrypted on the device with AES-256-GCM. The encryption key is held exclusively on your device in the iOS Keychain and is never transmitted to Nexalent's servers. Voice, video and files are protected by iOS device data protection and are not additionally encrypted by the app.
- When app lock is enabled by the user, the vault key is protected by a userPresence constraint: it cannot be unlocked without Face ID, Touch ID, or the device passcode.
- Server-side metadata is protected by Firebase security rules and Cloud Functions; direct client-side write access is blocked.
- The account identifier is derived from an HMAC digest of the email address. The addresses needed for system emails are stored on the server, closed to direct client access.
- The token in the Trusted Contact's pause link is generated randomly, is valid only for that grace window and cannot be used after the window closes.
- OAuth tokens are stored in the secure Keychain on the user's device.
- All server communications are conducted over TLS.
In the event of a personal data breach, affected individuals and competent supervisory authorities will be notified within the timeframes required by GDPR Article 33 and KVKK Article 12(5).
10.Data of Individuals Under 18
i-Will is intended for use only by individuals who are 18 years of age or older. We do not knowingly collect personal data from anyone under 18. If an account belonging to a minor is identified, that account and its associated data will be deleted without delay.
If you believe a minor is using the app, please notify us at info@nexalent.com.tr.
11.Your Rights (GDPR Art. 15–22 / KVKK Art. 11)
You hold the following rights. You may exercise any of them by contacting us using the details below. No legal process is required.
To obtain confirmation of whether your personal data is being processed and to receive a copy. (GDPR Art. 15 / KVKK Art. 11(a–b))
To have inaccurate or incomplete personal data corrected without undue delay. (GDPR Art. 16 / KVKK Art. 11(c))
To request deletion of your personal data when the conditions for processing no longer apply. (GDPR Art. 17 / KVKK Art. 11(d))
To request that processing of your data be limited under certain circumstances. (GDPR Art. 18)
To receive the data you have provided in a structured, machine-readable format. (GDPR Art. 20)
To object to processing based on legitimate interest grounds. (GDPR Art. 21 / KVKK Art. 11(e))
To claim compensation for damages resulting from unlawful processing. (KVKK Art. 11(g))
To file a complaint with your local supervisory authority or, for Turkish residents, with the KVK Board at kvkk.gov.tr.
Where processing is based on consent, to withdraw it at any time without affecting prior lawful processing. (GDPR Art. 7(3))
Send an email to info@nexalent.com.tr with the subject line "GDPR Request" or "Privacy Request". Additional information may be requested to verify your identity. Requests will be responded to within one month under GDPR (extendable by two further months for complex cases) and within 30 days under KVKK.
12.Cookies, SDKs, and Analytics
i-Will is a mobile application and does not use browser cookies. No in-app behavioural analytics or third-party advertising SDKs are present. The Firebase SDK is used solely for function calls, push notification delivery, and App Check; no behavioural user profiling is performed.
13.Policy Updates
This Privacy Policy may be updated from time to time. When material changes are made, users will be informed via in-app notification or email. The current version is always published in the app's legal section. Continued use of the app following an update constitutes acceptance of the revised policy.