Privacy Notice | Diftiva

Operator and contact

Diftiva is operated by the individual whom Apple identifies as the Seller for Diftiva on its U.S. App Store product page (the “Diftiva operator”). In this notice, “Diftiva” refers to that individual and the service they operate.

Privacy and support contact: diftiva@mavurem.com.

Scope and age eligibility

This notice applies to Diftiva’s website, account service, and iOS app. The initial account service is intended for people in the United States who are at least 13 years old. Diftiva is not directed to children under 13, and an under-13 child may not create an account.

If you are at least 13 but have not reached the age at which you may independently consent to an online service where you live, use Diftiva only with permission from a parent or legal guardian who has reviewed the service with you. The submitted U.S. P0 native registration flow does not ask ordinary registrants for a birth month, birth year, exact birth date, or separate age declaration. The 13+ requirement remains an eligibility rule in the Service Terms; it is not identity or precise-age verification. If we learn that an account was created by a child under 13, contact us so the account and associated personal information can be deleted.

If an older Web, WAP, or beta native compatibility path is deliberately enabled, it may submit a legacy 13+ checkbox. Birth month and year are requested or submitted only when the legacy enforce-mode age-assurance path is enabled. The checkbox is not retained or treated as age assurance. In that legacy enforce-mode path, the server uses the birth month and year only in memory to calculate a broad range and does not retain the month or year. If an eligible registration using that path completes, Diftiva may keep only the resulting range (13–15, 16–17, or 18+), how and when it was assessed, and the applicable age-policy version. An under-13 result on that path stops before an email challenge or account is created.

On supported Apple devices, when Apple indicates that an age-related regulatory requirement applies, Diftiva may ask you to share an Apple-provided age range. The app maps the response to a broad range (under 13, 13–15, 16–17, or 18+) without retaining the raw bounds or a birth date. Diftiva may also verify a signed app-identity record from Apple so that a later parental-consent withdrawal can be applied to every Diftiva account associated with the same app identity.

Information you provide or share through a requested flow

Account details such as your email address, language, time zone, base currency, and confirmed country or region.
A broad age range and limited source or observation details when a conditional Apple flow or an enabled legacy enforce-mode age-assurance path applies. A legacy 13+ checkbox or birth month and year, and the raw bounds supplied by Apple, are not retained.
Planned and actual amounts, goals, goal assignments, amounts you mark as moved, corrections, notes, and receipt images you choose to add.
Information in support messages and in access, correction, export, or deletion requests.
Your choices about optional analytics and your acceptance of the current service terms and acknowledgement of this notice.

Do not put passwords, verification codes, full payment-card details, bank credentials, government identifiers, or another person’s private information in notes, receipts, or support requests.

App Store purchases

If you buy paid access in the iOS app, Apple processes the payment. Diftiva receives verified purchase facts needed to provide and protect the feature, such as a random account token, product and transaction identifiers, purchase time, store environment, and refund or revocation status. Diftiva does not receive your complete payment-card or bank account details from Apple.

Diftiva uses those facts to unlock access, restore an eligible purchase to the same Diftiva account, prevent a purchase from being claimed by multiple accounts, reconcile store updates, and handle refunds, revocations, disputes, and support requests.

When the conditional Apple flow runs, Diftiva verifies the signed app-identity record but does not keep its raw identifier or signed payload in the account binding. Instead, Diftiva keeps the App Store environment, a one-way keyed identifier, Apple authority time, consent state, and the account association. The account association can also keep only the coarse age range reported by the supported Apple flow and when Diftiva observed it; raw age bounds are not kept. Diftiva uses that range only to apply the applicable age-related eligibility or restrictions, not to infer an exact age. If Apple reports that parental consent was rescinded, ordinary account features and optional analytics are disabled. A new signed record, reinstall, or repeated sharing does not automatically restore access. Account export, correction and deletion, support, legal information, sign-out, and processing of an already charged App Store transaction remain available.

Service, security, and device information

Diftiva records an operational trace identifier, request method and path without its query string, response status and duration, coarse signed-in or anonymous state, and a limited set of browser and transport headers needed to operate, protect, and troubleshoot the service. Structured request logs exclude request bodies, cookies, authorization credentials, CSRF tokens, and URL query values.

A client IP address may be written to a separate restricted operations log for abuse prevention and incident diagnosis. That log is configured for no more than seven days of retention. When a request is verifiably delivered by Cloudflare, its two-letter network country may be used to suggest an account region. The suggestion is not saved until you confirm it.

Diftiva uses necessary session and security storage to keep you signed in, prevent forged requests, remember privacy choices, and protect the service. The first-party consent cookie can remember your choice for up to one year. If an analytics-withdrawal request cannot immediately be confirmed, local storage and a necessary cookie mark it as pending so the browser can retry; the cookie expires after no more than 30 days and is cleared after completion. When you sign out, a separate browser marker may remain for up to 24 hours so an analytics identity can be cleared if the service is opened again on a shared browser. These markers are not used for advertising.

If the legacy enforce-mode age-assessment path is enabled and receives an under-13 result, short-lived session and server-cache markers may prevent immediate repeat registration attempts. The server marker uses a one-way keyed token derived from network information; it does not retain the raw IP address. These markers contain no birth month or year, are not used for analytics or marketing, and expire with the retry restriction. The no-account demo and other anonymous paths do not create a product-analytics identity.

How information is used

To create and authenticate your account and provide Diftiva’s tracking and goal features.
To provide purchases, exports, corrections, deletion requests, support, and transactional email.
To protect the service, prevent misuse and fraud, investigate errors, and maintain reliability.
To comply with law, enforce the service terms, and establish or defend legal claims.
To improve product flows when you have separately opted in to optional analytics.

Separately from optional product analytics, Diftiva may use account-linked registration, confirmed region and coarse audience status where available, core feature activity, and verified App Store purchase facts to produce privacy-minimized aggregate service and product metrics, such as whether new accounts create a first entry or goal. The resulting reports contain aggregate counts, dates, definitions, and rates; they do not include email addresses, account or Apple transaction identifiers, exact amounts, merchant names, notes, or raw age bounds. This does not enable optional ProductEvent, click, dwell-time, advertising, or cross-app tracking collection.

Diftiva does not sell personal information and does not use personal information for cross-context behavioral advertising.

Optional product analytics

Product analytics is off unless you opt in, and it is unavailable for an account treated as under 18 or lacking an approved adult-eligibility signal. When enabled for an eligible adult account, Diftiva creates random browser and session identifiers and may record page views, navigation and primary-button actions, coarse scroll-depth milestones, and broad engagement-time ranges. If you are signed in, an event may be linked to your Diftiva account.

These identifiers do not contain your name or email by themselves, but they can be stable and account-linked, so Diftiva treats this data as pseudonymous rather than anonymous. Analytics events must not contain spending amounts, merchant names, notes, email addresses, passwords, verification codes, uploaded images, or authentication tokens.

You can stop future optional analytics through the cookie controls or account settings without losing access to core features. Disabling analytics does not by itself erase events already stored; use the Data & Account controls to request deletion of account-linked data.

The submitted U.S. P0 release does not persist optional ProductEvent analytics. Before optional product analytics is enabled, Diftiva must approve and configure a positive retention period, update this Privacy Notice before the affected collection begins, and obtain any separate consent required for that collection.

When information is disclosed

Diftiva discloses information only as needed:

To infrastructure, security, storage, and email-delivery providers acting for Diftiva, including Cloudflare and AokSend when transactional email is enabled.
To Apple for App Store purchase processing, verification, refunds, revocations, and related support.
When required by law or reasonably necessary to protect users, the public, Diftiva, or legal rights.
As part of a merger, acquisition, financing, reorganization, or transfer of the service, subject to appropriate confidentiality and notice where required.

Providers may process information from locations outside your state. Before production use, Diftiva reviews the information sent, permitted uses, security controls, processing locations and subprocessors, and the applicable basis for deletion.

Transactional-email providers may process message or template content, recipient details, and delivery or security metadata. Retention of that information is based on what is reasonably needed to send and secure the message, prevent abuse, troubleshoot and document delivery, comply with legal obligations, and resolve disputes. Diftiva’s retention criterion is that the information should not be kept after it is no longer reasonably needed for those purposes or a legal obligation. Provider-side deletion or de-identification depends on the applicable provider arrangements, which Diftiva reviews before production use.

Retention and deletion

Account and user-created information is generally kept while the account is active and as needed to provide the service. Security, support, purchase, and legal records are kept only as long as reasonably needed for the purposes described above, subject to the specific periods below and any longer period required by law.

After you verify your identity and submit an account-deletion request, Diftiva completes deletion within seven calendar days and emails a completion confirmation. To send that confirmation after the account is removed, Diftiva temporarily retains the account email address in encrypted form. It is normally removed after the provider accepts the message and is kept no more than 30 days if delivery cannot be confirmed.

Backups rotate on a separate schedule, are access-restricted, and are used only for disaster recovery. The current rolling policy keeps 14 daily, eight weekly, 12 monthly, and three yearly snapshots, so some encrypted backup copies may remain for approximately three years. Deleted account data is not intentionally restored into the live service. If a backup must be restored, deletion records are reapplied before normal operation resumes.

Diftiva may keep an encrypted App Store server-notification payload for replay and reconciliation for up to 30 days after successful processing, then clears that ciphertext. Limited notification identifiers, digests, status, attempt history, and timestamps may remain for purchase integrity, disputes, security, and legal obligations.

Deleting an account removes its link to the one-way Apple app-identity record. An unlinked record with no consent withdrawal is then removed. If Apple reported a parental-consent withdrawal, Diftiva keeps the unlinked one-way identifier and withdrawal state so that creating a new account cannot silently bypass that instruction. Diftiva keeps this minimal record only as long as needed to honor the withdrawal, prevent it from being bypassed, or meet a legal obligation. It is not used for analytics or advertising. When it is no longer needed for those purposes or a legal obligation, Diftiva deletes or irreversibly de-identifies it.

If an account has App Store purchase history, deletion severs the purchase from the account and removes active access. Diftiva retains a minimal tombstoned record of purchase ownership, transaction status, and entitlement history to process refunds and revocations and prevent the same purchase from being claimed twice. A non-expiring purchase record may be kept for the life of that purchase plus any legally required or dispute-resolution period. It is not used for advertising.

Your choices and rights

Download a structured JSON copy of your Diftiva account data after signing in.
Correct editable account information or request correction of information you cannot edit directly.
Change optional analytics choices at any time.
Submit a verified account-deletion request in the service without making a separate support request.
Contact Diftiva to exercise any additional privacy right that applies in your state.

Diftiva may need to verify your request and may retain a minimal record showing that it was completed. To submit an appeal of a denied privacy request, email the Privacy and support contact above with “Privacy Appeal” in the subject.

Security

Diftiva uses administrative, technical, and organizational safeguards designed for the nature of the information it handles. No service can guarantee absolute security. Use a unique password and contact Diftiva promptly if you believe your account has been compromised.

Changes and contact

Diftiva may update this notice as the service or law changes. A new effective date will be posted, and Diftiva will provide additional notice or request a new acknowledgement when required. Material changes do not apply retroactively where prohibited by law.

Email diftiva@mavurem.com with a privacy question, request, or concern.

Manage your data

Sign in to manage data