Privacy Policy

Last updated November 2, 2026

1. Who this policy covers

This policy explains how Dazlight (“we”) handles information in TableNest for Android and iOS, including test builds. Feature availability may differ by platform and release. Dazlight is operated by Kakushadze Maksym, an individual in Ukraine. For privacy questions, email info@dazlight.com.

This policy covers the app. The Dazlight website and support form have a separate Website Privacy Policy, including information about website analytics. The local features described on the TableNest page work offline without registration.

2. Local tables and photos

TableNest stores the tables, columns, entries, saved views, local change history, settings and photos you create or import on your device. Built-in templates are local; copying one creates a personal table. Guest data and data used after an account sign-in are kept in separate local libraries. Signing in does not automatically move guest tables into an account library.

Local tables and photos are not automatically uploaded by TableNest. The app uses them to show and edit your records, search, filter, calculate, import and export. Its local database is not protected by a separate app-specific encryption key, so use your device’s screen lock and storage protections. The Android app disables automatic system backup of its app data; use TableNest’s full archive to keep a transferable copy. On iOS, app data may be included in device backups depending on the operating system and your backup settings. Device backups are separate from TableNest cloud synchronization.

3. Optional account and online features

If you choose to sign in, Firebase Authentication processes account information such as your email address, account identifier, password or Google sign-in information, and technical information needed for sign-in and security. On supported iOS builds, you may also choose Sign in with Apple. Apple and Firebase Authentication process the Apple account identifier, the name and email address Apple makes available when you authorize sign-in, and the credentials needed to authenticate. If you choose Hide My Email, Apple provides a private relay email address instead of your personal email address. TableNest does not receive your Apple password. Google provides Firebase Authentication and Cloud Firestore. Firebase Authentication is processed in the United States; Cloud Firestore data for this project is stored in the configured United States region, while Google may process service information elsewhere.

If you separately enable cloud storage for a table, TableNest sends its structure and supported row values to Cloud Firestore under your account when you synchronize it. Local photos and local file paths are not included. If you explicitly include project settings in synchronization, the synchronized settings include the project budget, currency, column mappings and completion status. You can continue using local tables without enabling cloud storage. An account is required for online publishing, rating or other community actions when available.

Where available, you may separately enable automatic synchronization while the app is open, save cloud versions or share a table with invited viewers or editors. People you authorize can access shared data permitted by their role and may make their own copies. Revoking access prevents new authorized access but cannot recall copies already obtained by others.

If you choose to submit a template, you review a preview before sending its structure and any demo values you entered. Your real personal rows and photos are not automatically included. A submitted template may be reviewed before it becomes public. Approved public template content and its author details may be visible to others. Ratings, favorites, reports and other account-linked actions, when available, are stored to provide those features. Online features may be unavailable in the current app version; this section explains how data is handled if you use them.

4. Imports, exports and backups

CSV imports are read from files you choose. CSV exports contain the entries you select, but they do not carry the underlying photo files. A full TableNest archive can include tables and local photos. PDF reports are generated on your device from the project information shown in the report, including project names, budgets and item information. Notes are included only when selected. A PDF report is not a full TableNest backup.

You choose where to save or share exported files and PDF reports. The app may create temporary local copies to prepare files for sharing; these are not guaranteed to be removed after a fixed time. If you use a cloud file provider, that provider handles the copy under its own policy. TableNest cannot recall files you have shared or saved elsewhere.

5. Service providers and support

TableNest uses RevenueCat to retrieve and manage subscription information. In builds configured with RevenueCat, signing in links your TableNest account identifier to RevenueCat even if you have not purchased a subscription or purchasing is unavailable. RevenueCat processes this identifier, subscription and transaction information, and device or platform information needed for its service. TableNest does not send your table contents or photos to RevenueCat. Purchases, when available, are processed by Apple or Google Play; TableNest does not receive your payment card details.

Cloudflare hosts TableNest’s backend API. It processes requests needed for online features, including authentication information and data submitted for the requested operation. Network and service information, such as IP addresses and request metadata, may also be processed to deliver and secure the service.

The app does not include advertising, Firebase Analytics or Crashlytics. Firebase, RevenueCat, Cloudflare, Apple and Google Play may process technical or service information needed for their respective services. We do not sell your table contents to advertisers. Provider processing locations and retention periods differ; the United States Firestore region above does not describe every provider.

If you contact us by email or through the website support form, we receive the contact details and message you send to respond to your request. Avoid sending table contents, photos or passwords unless they are necessary for your request.

Legal bases for processing in the EEA

Where the GDPR applies, we use the following legal bases for the purposes described in this policy:

• Providing the service you request (Article 6(1)(b)). This covers the information needed to create and sign in to an account, provide optional cloud storage, synchronization, sharing and publication that you choose, and manage an available subscription.
• Our legitimate interests (Article 6(1)(f)). We use limited account, request and technical information to secure the service, prevent unauthorized access, abuse and purchase replay, maintain the integrity records described below, and respond to ordinary support questions. Our interests are protecting users and the operation of TableNest; you may object where this basis applies.
• Legal obligations (Article 6(1)(c)). We process information when necessary to respond to privacy rights requests or keep records required by applicable law.

Choosing an optional feature does not by itself mean that we rely on consent as the legal basis. If we ask for consent for a separate purpose, we will explain that purpose and how to withdraw it.

International processing and transfers

Using an optional account or online feature can involve processing outside the European Economic Area, including in the United States. Firebase Authentication and this project’s Cloud Firestore data are processed in the United States as described above. Cloudflare processes backend requests; RevenueCat processes account and subscription information. Their service providers may process some information in other countries.

For qualifying restricted transfers covered by Cloudflare’s Data Processing Addendum, its terms provide for EU Standard Contractual Clauses and other applicable safeguards. RevenueCat’s standard terms incorporate its Data Processing Addendum for customer personal data; that addendum provides for EU Standard Contractual Clauses where its restricted-transfer conditions are met. These clauses are not a statement that every transfer to either provider uses the same mechanism.

We are still verifying which Google Cloud data-processing terms apply to our account and confirming the account-specific contractual record for RevenueCat. We will update this section when that review is complete. We do not claim that all transfers to these providers are covered by Standard Contractual Clauses or that a Data Privacy Framework certification has been verified. To ask about a particular transfer or the applicable safeguards, contact info@dazlight.com.

6. Your choices and account deletion

You can edit or delete local records in the app, export them, clear app data or uninstall TableNest. Deleting an online copy of a table is a separate action; your local table and photos remain on your device. You must also manage any CSV or archive files you exported and any independent template copies held by others.

To request deletion of a TableNest account and its associated online data, use the in-app account deletion option where available, or email info@dazlight.com with the subject “TableNest account deletion.” We may need to verify that you control the account; do not send us your password. We handle requests manually and complete a verified deletion request within 30 calendar days after receiving it. If we cannot verify control, we will explain what is needed. When deletion is complete, we send confirmation to the email address linked to the account.

After verification, an operator processes account-linked private and shared cloud data, publications and associated online records, then the Firebase Authentication account. The process includes requesting deletion of the associated RevenueCat customer record. Account deletion does not cancel an Apple or Google Play subscription; manage or cancel renewal separately through the relevant store.

Minimal account, publication and shared-object identifiers, and protected purchase-chain identifiers may remain to prevent stale access, identifier reuse and purchase replay. These records do not contain table entries or photos. Service logs and provider backups may follow separate retention schedules. Independent copies of public templates and shared data obtained by others cannot always be recalled.

Data stored only on your device or in an archive elsewhere cannot be erased remotely by deleting the online account. For access, correction or other data questions, contact the same address.

7. How long information is kept

Local tables and photos remain on your device until you change or remove them, clear app data or uninstall the app. Temporary export files may remain until a later cleanup operation or device-level removal; TableNest does not promise deletion at a fixed interval. Android automatic backup is disabled for app data. iOS device backups and copies you save with another provider follow your device settings and that provider’s retention rules.

Private cloud tables, synchronized project settings and cloud versions remain while the relevant online feature is in use, unless you remove them or request account deletion. Shared tables and public templates remain until removed through the available feature or operator process. Copies made by other people are independent and may remain after the original is removed.

Firebase Authentication account information and RevenueCat customer information are handled through their respective services. A verified deletion request starts the manual account cleanup and a request to RevenueCat; it does not mean that provider logs or backups are erased immediately.

We keep support messages for 12 months after the support case is closed. We keep a minimal operator record of an account deletion request, its completion and email confirmation for 12 months after completion. Temporary in-app request and status records may be removed earlier after cleanup verification and token-expiry checks. These periods may be extended only where a specific legal obligation or an active dispute requires it.

Minimal account fences and publication, shared-object and purchase integrity identifiers are retained while the corresponding online service operates and the identifiers are needed to prevent stale access, reuse or purchase replay. When that protection is no longer needed or is replaced, we remove the identifiers. They do not contain table entries or photos. Firebase, Cloudflare, RevenueCat and platform stores may retain their own service or security logs and backups under their policies.

8. Your privacy rights

Depending on the law that applies to you, you may request access to, correction or deletion of your personal information, restriction of processing, a portable copy, or object to certain processing. If processing is based on consent, you may withdraw it. You may also be able to complain to a competent data protection authority. Email info@dazlight.com to make a request or ask how a stated basis applies to your data. Some rights have legal conditions and exceptions.

9. Security, children and changes

Protect your device, account and exported archives. Access rules restrict private cloud tables to their owner. Where shared tables are available and you choose to share one, access is also granted to authorized participants according to their role. No storage or transfer method is perfectly secure.

TableNest is not designed for children. If you believe a child has sent personal information through an account or support channel, contact us so we can address it. We will update this policy and its “Last updated” date if our data practices change.