Privacy Policy
This Privacy Policy explains how Ateshgah Money handles information when you use its mobile application, web version, and public support, privacy and deletion pages on ateshgahmoney.com. Ateshgah Money helps you record personal finances and, if you choose, share expenses in a separate family budget.
At a glance
- Your personal financial entries stay on your device or in your browser. Signing in does not automatically back them up online.
- Account information is processed online. Expenses you deliberately add to a family budget are stored online and visible to its members.
- The current app has no advertising or behavioural analytics integration. We do not sell personal information or use your financial entries to train AI models.
- For privacy questions or an account-deletion request, contact support@ateshgahmoney.com. Signing out or uninstalling is not online account deletion.
This summary is an introduction. The sections below explain the details and limitations.
1. Who is responsible for your information
Ateshgah Money is operated by “ATESHGAH TECHNOLOGİES” Məhdud Məsuliyyətli Cəmiyyəti, a limited liability company registered in Azerbaijan on 16 November 2026, tax identification number (VÖEN) 1310229961 ("we", "us", or "our"). The operator is responsible for deciding how personal information is used for the service.
Registered address: AZ1141, Bakı şəhəri, Yasamal rayonu, Şəfayət Mehdiyev, ev 77, mənzil 24, Azerbaijan. The company's registered Azerbaijani name is retained above; “limited liability company” describes its legal form in English.
Scope of this policy
This policy covers the application, its web version, our public support website and communications with our support team (the “Service”). “Personal information” means information that identifies you or can reasonably be linked to you. We act as the data controller where that term applies. Features may differ between versions and platforms.
The current Service records information you enter; it does not hold or transfer funds, execute currency exchanges or access your bank. An account labelled “bank card” is a record in the app, not access to a real payment card.
This policy explains data practices; it is not blanket consent to optional processing. Where consent is required, it must be requested separately. Nothing in this policy removes rights or obligations that cannot lawfully be excluded.
2. Information we process
Account information
When you register, we process your name, email address, account identifier and authentication information through Supabase. If you choose Google sign-in, Google provides the account identifier and basic profile information authorized during sign-in, which may include your name, email address and profile picture. We do not receive your Google password or request access to your Gmail messages or contacts.
Personal finance records
Amounts, account names, currencies, categories, notes, income, expenses, transfers, debts, goals, budgets and challenge progress that you enter are stored on your device or in your browser. The current version does not automatically upload these personal records to our database or synchronize them across devices. Subscription suggestions and reports are calculated from these records on your device. The app does not connect to your bank or read your SMS messages.
Family budget information
If you create or join a family budget, Supabase stores the family name, account identifiers, chosen member names, monthly limits and the expenses you explicitly add to that budget. A shared expense includes its author, amount, currency, conversion rate, date, category and note. Personal records are not automatically copied into the family budget. Invitation codes are stored on the server as hashes.
Technical information and correspondence
Services contacted by the app receive network information such as your IP address and request metadata. Authentication and email providers may maintain security and delivery logs. If you contact support, your message, email address and any information you choose to send are processed to handle your request. Please do not send passwords, verification codes or full payment-card details.
Our authentication and API infrastructure also records sign-in and request events, session identifiers, browser or device user-agent information, response status and timing, and approximate country or city inferred from an IP address. Infrastructure security logs may include a connection fingerprint derived from TLS connection characteristics. This is network-based information, not GPS tracking. We use relevant operational records to maintain the service, investigate faults and protect accounts; they are not used by us for advertising profiles. Google profile-picture links may remain in the authentication provider's account metadata even though the current app does not display a profile photo.
Our public website is hosted and protected by Cloudflare. When you visit it, Cloudflare processes connection and request information, such as IP address, requested page, time, browser information and security signals, to deliver the pages, maintain reliability and prevent abuse. Opening a support page does not give the website access to financial records stored by the mobile app. Sending an email from that page uses your chosen email service.
Preferences and sensitive details
Local preferences include language, theme, reminder and app-lock settings, remembered email if selected, session state and cached exchange rates. Authentication providers also process verification status, sign-in events and session identifiers to operate your account.
Free-text notes and category choices can reveal sensitive information, such as medical expenses. We do not need medical details, political or religious information, identity-document numbers or banking passwords. Avoid entering them, especially in shared records. Do not submit another person's information unless you have an appropriate basis to do so. Remove unrelated personal information from support attachments.
3. Purposes and legal grounds
- To create and authenticate your account, maintain your session, and send verification and password-reset emails.
- To provide financial records, reports, currency calculations, challenges and optional reminders.
- To share explicitly submitted family expenses with authorized members and enforce access permissions.
- To respond to requests, investigate technical problems, prevent abuse and meet applicable legal obligations.
The current app does not include advertising or a dedicated third-party behavioral analytics SDK. We do not sell your personal financial records or use them for targeted advertising. Reports and challenges do not make credit, lending or other decisions with legal or similarly significant effects.
| Purpose | Relevant information | Basis |
|---|---|---|
| Accounts and requested features | Account, session, financial and shared-budget information relevant to the feature. | Performance of the service relationship where necessary; consent where applicable law requires it. |
| Verification and recovery emails | Email address, verification or recovery information and delivery status. | Providing and protecting the requested account service. |
| Support and privacy requests | Correspondence and proportionate verification information. | Service performance, applicable legal obligations, or our legitimate interest in resolving enquiries. |
| Prevent abuse and investigate faults | Relevant account, request and incident information. | Our legitimate interest in protecting users and service integrity, balanced against users' rights; legal obligations where applicable. |
| Legal obligations and claims | Only information relevant to the particular matter. | Applicable legal obligations and, where permitted, legitimate interests in establishing or defending legal rights. |
A valid basis must exist under the law applicable to the particular processing. Legitimate interests do not replace consent where it is legally required. You may withdraw consent for future processing where consent is the basis. Disabling an optional permission may disable its associated feature without cancelling unrelated functions.
Email and authentication information are needed for an online account; shared entries are needed to provide a family budget. Optional notes and support attachments are your choice. Registration does not subscribe you to promotional emails in the current Service.
Financial insights and automated processing
Month-to-month comparisons, possible recurring-payment detection, challenge progress and monthly summaries are calculated from your entries. Personal-finance calculations run locally; shared-budget calculations use the shared entries. A suggested subscription is an inference from records, not access to the subscription provider or authority to cancel payments. We do not send financial entries to a generative-AI provider in the reviewed version.
5. Local storage and permissions
The app stores session information to keep you signed in, together with language, appearance and other preferences. The web version uses browser storage, including local storage. Clearing that storage may sign you out and remove local records. The app does not implement advertising cookies; external sign-in pages may use their own cookies.
Notifications are optional and scheduled locally. If you enable the monthly summary, its text can include financial totals visible on your lock screen, depending on device settings. You can disable reminders and change notification permissions in your device settings.
Optional biometric or device-passcode locking uses the operating system's authentication mechanism. The app receives the authentication result, not your fingerprint, face template or device passcode.
Where a version offers file import or export, access relates to the file you choose. A file shared to another app is handled by the destination you select. Files outside the app are not automatically removed when an account is deleted. The current app does not request address-book, precise-location, camera, microphone or SMS access for financial tracking.
Signing in on another device does not recover personal records from your previous device. Device or browser backup and synchronisation services that you independently enable may keep their own copies, subject to those services' settings.
Public website
Our support, deletion and privacy pages have no account login or advertising cookies. They do not use browser storage to save financial records. The pages' security policy blocks analytics scripts. Cloudflare may use security cookies if a bot check or security challenge is required. These are separate from advertising or financial profiling; see Cloudflare's cookie information. External sign-in, email and linked websites have their own notices and settings.
6. Security
The app connects to its online services using HTTPS. On mobile, personal finance records and persisted authentication data are encrypted locally, with encryption keys kept in the platform's protected key storage. The web version does not apply this mobile-vault encryption to browser storage.
Server-side functions check family membership and permissions, and direct client access to family tables is blocked. Family-budget data is not end-to-end encrypted. No storage or transmission method can provide an absolute security guarantee. Protect your device, email account and sign-in credentials.
Optional app locking protects access on supported devices but does not replace server authentication. Report suspected unauthorised access to our support address. We will assess incidents and provide notifications where required by applicable law. These security limitations do not exclude our statutory duties or your legal remedies.
7. Retention and deletion
Local records: personal finance records remain on the device or browser until you remove them or clear the relevant storage. A previous local state is also kept for recovery. The app's local-data clearing action removes the financial records for that account on that device and the recovery copy. It does not delete the Supabase account, family records or files you saved elsewhere. Signing out is not account deletion.
Family records: leaving a family or being removed ends your access, but your previously added shared expenses remain in that budget. The owner can delete the budget and its shared records for all members. Under the current database rules, deleting an authentication account removes that user's shared expenses; deleting the owner's account also removes the entire budget they own.
Other copies: information independently saved by other members or exported outside the app is not automatically removed by deleting server records. Removing the app does not delete your online account.
Retention criteria
We do not retain identifiable information indefinitely merely because it might be useful. Retention depends on the feature used, unresolved requests and applicable legal obligations.
| Category | Retention criteria |
|---|---|
| Online account and family records | While the relevant account or shared budget exists, subject to valid deletion requests, available deletion controls and limited lawful retention. |
| Support and privacy correspondence | While resolving the request, any outstanding follow-up, and any necessary evidence of its handling. The criteria are whether the matter remains open, whether the information is needed to demonstrate fulfilment of a privacy request, and whether a specific obligation or legal claim requires it. Unneeded attachments and duplicate records are removed when no longer necessary; there is no blanket indefinite retention of correspondence. |
| Authentication, security and email logs | For operating and protecting the service, investigating a specific incident, and meeting a relevant legal obligation. Provider log windows and account audit records are different: expiry of a dashboard log does not mean all account information has been deleted. Any separately retained incident evidence must remain limited to that incident or obligation. |
| Website request and security information | For delivery, reliability, abuse prevention and investigation under Cloudflare's applicable service and security retention rules. It is not used by us to build financial or advertising profiles. |
| Provider backups, where retained | Deleted information may remain until backup expiry or overwrite. It must not return to ordinary use; restoration must respect completed deletion requests. |
For context, Supabase currently publishes a one-day API/database log window for its Free plan, which this project uses. That window is not a deletion deadline for stored account audit records. Resend publishes 30-day email/log retention for its standard Free, Pro and Scale plans. Provider backups and separately required security records can have different periods. See Supabase's plan information and Resend's retention information. Contact us for the period and reason applicable to particular information in your request.
Requesting account deletion
You can request deletion without installing or signing in to the app through our account-deletion page. It explains the email route and the consequences for shared budgets.
In app versions with this control, open Settings → Delete account. Confirm your identity using your password or Google sign-in, review the consequences and type DELETE. The service checks your account and recent active sign-in before deleting it and revokes its sessions. The app then clears the personal records, local recovery copy, reminders and saved sign-in on that device. If local cleanup fails, the app offers a retry; clearing the app or website storage is a fallback. Older installed versions can use the email route below.
Email support@ateshgahmoney.com with the subject “Account deletion request”, preferably from your registered email address. Identify the account, but do not send your password or verification code. We may need proportionate proof of account control to prevent unauthorised deletion.
After verification, we will process the request and explain any information that must lawfully be retained, the reason and applicable retention period. A request can also concern particular information without closing the entire account. We remain responsible for deletion from systems and processors under our control as required by law.
We cannot remotely erase records held only on a disconnected device, browser or independently saved file. Clear local records before losing access to the account and remove copies you no longer need. Account-deletion confirmation must explain the shared-budget consequences above, particularly if you own a budget.
8. Your choices and rights
You can edit or remove records using the available app controls, choose whether to use a family budget, and change optional permissions. Depending on applicable law, you may also have rights to access, correct, delete or obtain a copy of information, restrict or object to processing, withdraw consent where processing relies on consent, and complain to a competent data-protection authority.
Send requests to support@ateshgahmoney.com. Describe the request and relevant account. Verification must be proportionate to its risk; do not send identity documents unless we explain why they are necessary and how to provide them appropriately.
We will respond within the period required by applicable law. If a lawful extension, limitation or refusal applies, we will explain the reason and available next steps. Rights are subject to applicable exceptions, including protection of other people's information. We will not penalise you for exercising a protected privacy right.
Because personal finance records are kept locally, we cannot retrieve a lost device's records from our server. Available on-device controls and any supported export functions are relevant to those records. This practical limitation does not limit rights over account, shared-budget or support information we do hold.
Regional information
Azerbaijan: where Azerbaijani personal-data law applies, it governs the relevant collection, processing, protection and cross-border transfer. European legal grounds described above do not displace Azerbaijani requirements.
EEA and United Kingdom: where the GDPR or UK GDPR applies, you can object to processing based on legitimate interests for reasons relating to your situation. We normally must respond to a rights request within one month; extensions are possible where permitted by law, with notice. You can complain to your local supervisory authority without first contacting us.
United States and other locations: local rights may include access, correction, deletion, portability and, where applicable, appeal of a denied request or use of an authorised agent. Contact us to make a request or appeal. We do not claim that every regional statute applies to our company; rights and obligations are determined by applicable law.
9. International processing
We operate from Azerbaijan. The currently configured Supabase project is hosted in Sydney, Australia. Our Zoho account was set up in its United States data centre. Authentication, email and other providers may process relevant information in additional countries through their infrastructure or support operations. Cloudflare uses an international network, and Google processes sign-in information under its own privacy policy. Your device-only financial records are not automatically transferred to these services.
International processing is subject to applicable transfer rules. Where a transfer requires a specific safeguard or authorisation, that requirement must be met. Accepting this policy is not a blanket waiver. You may contact us for information about safeguards applicable to your data.
The Supabase Data Processing Addendum forms part of its service terms and provides standard contractual clauses and regional addenda where their conditions apply. Resend states that its data processing agreement, including EU standard contractual clauses, applies to its accounts upon signup. These contracts do not remove other requirements of the law applicable to a transfer. You can ask us for information or a copy of the safeguards relevant to your information; confidential or unrelated details may be redacted.
10. Children's privacy
The Service is intended for people aged 16 and above. Where local law requires a higher age or parental authorisation, those requirements also apply. The Service is not designed for children under 16. Family-budget membership is not a substitute for any required parental authorisation. We do not collect a date of birth or identity document as part of routine registration.
We do not knowingly seek personal information from children below the applicable minimum age. If you believe a child has created an account contrary to this rule, contact us. We will investigate, restrict inappropriate processing and remove information as required, subject to necessary legal or safeguarding obligations.
11. Changes to this policy
This policy will be updated when the app's data practices change. The published version will display its effective or last-updated date. Where required by law, material changes will be communicated separately and consent will be obtained before introducing processing that requires it.
A revision will not, by itself, authorise a new use of previously collected information that requires additional permission.
12. Contact
Application: Ateshgah Money
Operator: “ATESHGAH TECHNOLOGİES” Məhdud Məsuliyyətli Cəmiyyəti
VÖEN: 1310229961
Registered address: AZ1141, Bakı şəhəri, Yasamal rayonu, Şəfayət Mehdiyev, ev 77, mənzil 24, Azerbaijan.
Privacy, support and deletion requests: support@ateshgahmoney.com
Verification and password-recovery messages may arrive from noreply@ateshgahmoney.com. Send enquiries to the support address above.