Privacy Policy

1. About Billinger

Billinger is an invoice creation and management application that allows users to create, manage, store, synchronize, preview, export, and share professional invoices for personal or business use.

The App may also provide business profiles, client management, invoice templates, reporting, subscription features, cloud synchronization, notifications, and other related functionality.

2. Information We Collect

2.1 Information You Provide

When using Billinger, you may provide information including:

• Your name
• Email address
• Business name
• Business address
• Phone number
• Tax or registration information
• Business logo or other uploaded images
• Client names
• Client contact details
• Client addresses
• Invoice numbers
• Invoice dates and due dates
• Invoice line items
• Item descriptions
• Quantities
• Prices
• Taxes
• Discounts
• Payment status
• Payment instructions
• Notes
• Invoice totals
• Currency information
• Other information you voluntarily enter into the App
• Information you provide when contacting support

This information is used primarily to provide Billinger’s invoice creation, management, synchronization, storage, export, and account functionality.

3. Automatically Collected Information

When you use Billinger, certain technical and usage information may be collected automatically.

This may include:

• Device model and device type
• Operating system and operating system version
• App version
• Application identifiers
• App installation information
• Session information
• Country or region information
• Language
• Time zone
• App usage and interaction events
• Screens viewed
• Feature interactions
• Subscription and paywall interactions
• Technical service logs
• Crash information
• Crash stack traces
• Relevant application state when a crash occurs
• Push notification registration identifiers
• Firebase Cloud Messaging registration tokens
• IP address where technically necessary for service operation, security, fraud prevention, or infrastructure

We use this information to operate the App, understand how users interact with Billinger, diagnose technical problems, improve usability, improve conversion and onboarding experiences, maintain security, and improve App reliability.

The categories above relate to different services and purposes described in this policy; they are not all sent to every provider. Optional Meta advertising measurement is subject to the separate limits and consent controls in Section 23.

4. Firebase Analytics

Billinger uses Google Firebase Analytics to understand how users interact with the App.

Analytics may help us understand events such as:

• Whether users begin or complete onboarding
• Which onboarding steps users reach
• Whether users sign in successfully
• Whether users complete initial business setup
• Whether users begin or complete invoice creation
• Whether invoice previews are viewed
• Whether users attempt to export or share invoices
• Whether subscription paywalls are displayed
• Which subscription options users select
• Whether subscription purchase flows are started or completed
• Which App features are used
• General App engagement and usage patterns

We use this information to:

• Improve onboarding
• Identify areas where users experience difficulty
• Improve App navigation and usability
• Improve invoice creation workflows
• Evaluate feature usage
• Improve subscription experiences
• Understand product performance
• Improve Billinger based on aggregate usage patterns

Information We Do Not Intentionally Send to Firebase Analytics

Our Analytics implementation is designed not to intentionally send user-entered invoice or business content to Firebase Analytics.

We do not intentionally send Analytics events containing:

• Client names
• Business names
• Email addresses
• Phone numbers
• Physical addresses
• Invoice numbers
• Invoice descriptions
• Item names
• Item descriptions
• Invoice notes
• Bank account information
• IBAN information
• Tax identifiers
• Payment instructions
• Invoice PDF contents
• Arbitrary user-entered text
• Apple account identifiers
• Firebase user IDs

Analytics events use predefined product-behavior categories rather than user-entered content.

Billinger does not use Firebase Analytics for third-party advertising or cross-app advertising tracking.

Billinger's Analytics implementation does not use Apple’s Identifier for Advertisers (IDFA).

5. Firebase Crashlytics

Billinger uses Google Firebase Crashlytics to identify, diagnose, and resolve crashes and technical problems.

Crashlytics may collect information including:

• Crash stack traces
• Device information
• Operating system information
• App version
• Relevant application state
• Technical diagnostic information

Because Firebase Analytics is also enabled, Crashlytics may receive limited analytics breadcrumb information describing App interactions immediately before a crash. These breadcrumbs help us understand what happened before a technical failure.

We use Crashlytics information solely to:

• Diagnose crashes
• Identify technical defects
• Improve App stability
• Improve App reliability
• Investigate performance and technical issues

We do not intentionally attach invoice contents, client information, payment information, or other user-entered business content to Crashlytics reports.

6. Sign in with Apple

Billinger may allow you to authenticate using Sign in with Apple.

Depending on the choices you make when signing in, Apple may provide us with:

• A unique account identifier
• Your name, if shared
• Your email address
• An Apple Private Relay email address if you choose to hide your email

We use this information for:

• Account authentication
• Secure login
• Account identification
• Account management
• Synchronization of your Billinger data across supported devices

We do not receive or store your Apple ID password.

7. Cloud Storage and Data Synchronization

Billinger uses Google Firebase and Google Cloud infrastructure to provide account, storage, synchronization, and related functionality.

Cloud-stored information may include:

• Business profiles
• Client profiles
• Invoice information
• User preferences
• App settings
• Uploaded logos or images
• Subscription-related status or identifiers
• Account-related information

Cloud storage and synchronization allow you to access your Billinger information across supported devices associated with your account.

Services used may include:

• Firebase Authentication
• Cloud Firestore
• Firebase Storage
• Google Cloud infrastructure

8. Push Notifications

Billinger may use Apple Push Notification Service (APNs) and Firebase Cloud Messaging to provide notifications.

To provide push notifications, technical identifiers such as device notification tokens or Firebase Cloud Messaging registration tokens may be processed.

These identifiers are used to deliver App-related notifications and are not used by Billinger for third-party advertising.

You can manage notification permissions through your device settings.

9. Firebase Remote Config

Billinger may use Firebase Remote Config to manage certain App configuration or feature settings.

Remote Config may process limited technical information such as:

• App version
• Operating system information
• Language
• Country or region
• Time zone
• Device or App configuration information

This information is used to provide and configure App functionality and does not include invoice contents or user-entered business information.

10. Subscriptions and Purchases

Billinger may offer optional premium subscriptions through Apple App Store In-App Purchases using Apple StoreKit.

Payments are processed by Apple.

Billinger does not directly collect, process, or store your credit card number or full payment card details.

We may receive limited purchase-related information necessary to:

• Determine subscription status
• Activate premium features
• Restore purchases
• Confirm entitlement to subscription functionality

Payment processing is subject to Apple’s terms and privacy practices.

Optional advertising measurement of eligible subscription trials or verified charges is separate from payment processing and Premium access. It is subject to the event-category approvals and consent restrictions in Section 23; production paid-event reporting is currently disabled.

11. PDF Invoice Generation and Export

Billinger allows you to generate invoices or other documents based on information you provide.

Generated invoice content may include:

• Business information
• Client information
• Invoice items
• Dates
• Notes
• Totals
• Taxes
• Payment information

Generated files may be stored on your device or shared using iOS sharing functionality.

When you choose to export or share a file, the destination and recipient are selected by you.

Billinger does not control how exported files are handled after you share or save them outside the App.

You are responsible for the information you enter into invoices and for how you choose to distribute generated documents.

12. How We Use Information

We may use information collected through Billinger to:

• Create and manage your account
• Authenticate users
• Create and manage invoices
• Generate invoice documents
• Store and synchronize information
• Manage clients and business profiles
• Restore subscription access
• Provide premium features
• Deliver notifications
• Provide customer support
• Analyze App usage
• Measure the effectiveness of Billinger advertising through approved installation, activation, and eligible in-app conversion events, only if the corresponding measurement category is enabled and the required consent and authorization have been granted
• Understand user interactions
• Improve onboarding
• Improve product conversion and usability
• Improve features and user experience
• Diagnose crashes and technical errors
• Improve App stability and reliability
• Protect the security of the App
• Prevent misuse, fraud, or abuse
• Comply with applicable legal obligations

13. How We Share Information

We do not sell your personal information for money or rent personal information. We do not disclose user-entered business or document content for advertising.

Our current production app does not share personal information with Meta for advertising measurement because that feature remains disabled.

If optional Meta measurement is enabled, limited event and technical information may be shared with Meta as described in Section 23. Depending on applicable law and the provider’s use, advertising-related disclosures may be treated as a “sale,” “sharing,” or targeted advertising even without payment. The feature will not be activated until the required notices, choices, and validation are in place.

Information may be processed by service providers that help us operate Billinger.

Apple

For:

• Sign in with Apple
• App Store distribution
• In-App Purchases
• StoreKit subscriptions
• Push notifications

Google Firebase / Google Cloud

For services including:

• Authentication
• Firestore database
• Cloud storage
• Analytics
• Crashlytics
• Cloud Messaging
• Remote Config
• Supporting cloud infrastructure

Meta Platforms

For optional advertising measurement, if made available and enabled with the required consent and authorization. The information, limits, and controls are described in Section 23. Meta may also process this information under its own applicable terms and privacy policy; its role should not be assumed to be identical to that of a provider processing data solely on our instructions.

These providers may process limited information necessary to provide their respective services and operate under their own privacy policies and data protection terms.

14. Legal Requirements

We may disclose information when reasonably necessary to:

• Comply with applicable laws
• Comply with court orders or lawful government requests
• Enforce applicable agreements
• Protect our legal rights
• Investigate fraud, abuse, or security incidents
• Protect the safety of users or others

15. Business Transfers

If Billinger or the business operating Billinger is involved in a merger, acquisition, financing, restructuring, reorganization, sale of assets, or similar transaction, information associated with Billinger may be transferred as part of that transaction.

Any successor would be expected to handle personal information consistently with applicable law and this Privacy Policy or provide appropriate notice of material changes.

16. Data Retention

We retain information only for as long as reasonably necessary to:

• Provide Billinger services
• Maintain your account
• Provide synchronization and storage
• Fulfill legitimate business purposes
• Maintain App security
• Diagnose technical problems
• Comply with legal obligations

Account and cloud data may remain stored while your account is active.

Information may also remain temporarily in secure backups where required for system integrity, disaster recovery, or legal compliance.

Analytics, diagnostic, and crash information may be retained according to applicable Firebase and Google service settings and retention policies.

When an account deletion request is completed, we will delete or anonymize associated information where legally and technically possible, subject to legitimate retention requirements.

If Meta measurement is enabled, Meta’s retention of measurement and technical information is subject to its applicable policies and settings. We do not promise a fixed Meta retention period or that deleting a Billinger account automatically deletes every record already processed by Meta. Withdrawing consent does not by itself erase information already received. You may use the contact and deletion-request instructions in Sections 17 and 20, and Meta’s own privacy controls, to exercise applicable rights.

17. Account and Data Deletion

You may request deletion of your Billinger account and associated cloud data.

Where account deletion functionality is available directly within the App, you may use that functionality to initiate deletion.

You may also contact us regarding a privacy or deletion request at: meri.arakelyan.developer@gmail.com

Certain limited information may be retained where legally required or reasonably necessary for security, fraud prevention, dispute resolution, or enforcement of legal obligations.

18. Data Security

We use commercially reasonable technical, administrative, and organizational measures intended to protect information processed through Billinger.

These protections may include secure authentication, access controls, encrypted network communication, and security protections provided by our cloud infrastructure providers.

However, no electronic storage or internet transmission method can be guaranteed to be completely secure.

19. International Data Transfers

Billinger uses service providers that may process or store information in countries other than the country where you live.

As a result, information may be transferred internationally through service providers such as Apple, Google Firebase, and Google Cloud and, if optional advertising measurement is enabled, Meta Platforms.

Where required, appropriate safeguards are used in accordance with applicable data protection laws.

20. Your Privacy Rights

Depending on where you live, you may have rights regarding your personal information.

These may include the right to:

• Request access to your information
• Request correction of inaccurate information
• Request deletion of information
• Request a copy of your information
• Restrict certain processing
• Object to certain processing
• Withdraw consent where processing is based on consent
• Request account deletion
• Exercise other rights available under applicable privacy laws

To submit a privacy-related request, contact: meri.arakelyan.developer@gmail.com

We may need to verify your identity before completing certain requests.

21. Children’s Privacy

Billinger is not intended for children under the minimum age required by applicable law, including children under 13 in the United States.

We do not knowingly collect personal information from children in violation of applicable law.

If we learn that personal information from a child has been collected improperly, we will take reasonable steps to delete it.

22. Location Information

Billinger does not request or collect precise GPS location information for its core functionality.

Some service providers may derive general country or region information from technical data such as IP addresses or device configuration.

This is not used by Billinger for precise location tracking.

23. Advertising and Tracking

Billinger does not currently display third-party advertising.

Billinger does not sell personal information for money.

Billinger does not use Apple’s Identifier for Advertisers (IDFA) for Firebase Analytics.

Billinger does not use Firebase Analytics to track users across unrelated companies’ apps or websites for advertising purposes.

The Firebase product analytics described in Section 4 are used to understand and improve Billinger itself. Optional Meta advertising measurement is a separate purpose and integration.

Meta Platforms and the upcoming release

The upcoming Billinger release includes the Meta App Events SDK, provided by Meta Platforms (“Meta”), the company behind Facebook and Instagram, for optional advertising measurement.

Production Meta measurement is currently disabled. The production integration does not initialize the SDK or request Meta activation reporting. Publishing this policy does not enable it. The following describes the intended behavior if and when the feature is made available after the required disclosures, consent controls, and validation are completed.

Purpose and event scope

If enabled with the required choices, Meta measurement helps us understand whether Billinger advertising leads to app installations and activations and helps us evaluate the effectiveness of our advertising campaigns.

The implemented code supports explicit app activation reporting, and the SDK may also report the first app launch for installation measurement. It also supports the following carefully limited events, each subject to its production approval and the required consent and authorization:

• Successful new-account registration and eligible first invoice or first estimate creation, without account identifiers or document contents.
• A subscription paywall being viewed, with only a predefined, non-identifying source category such as Settings or a feature gate.
• An eligible verified subscription free-trial start, without purchase revenue.
• An eligible verified first paid subscription or trial-to-paid conversion, and verified positive subscription charges or renewals, if paid reporting is separately approved.

Implemented code does not mean production reporting is active. Production SDK measurement and every production event approval remain disabled at the time of this update. Activation, registration/first-document events, paywall events, free trials, and paid events have separate rollout controls. In particular, production Subscribe and Purchase reporting is not live and remains disabled pending further verification and explicit approval. Categories may be introduced in stages only after the applicable notices, consent controls, provider configuration, and validation have been approved.

A paywall-view event is not a purchase or trial. Tapping a subscription button, cancelling a purchase, restoring Premium access, or marking a customer invoice paid is not treated as proof of a new Meta subscription purchase. The implemented subscription recorder uses verified StoreKit evidence and conservative eligibility and duplicate-suppression checks; it does not backfill historical or pre-consent transactions. Firebase Analytics events are not automatically forwarded to Meta.

Information Meta may process when measurement is enabled

Depending on the supported SDK functions and configuration, the limited information processed for measurement or SDK operation may include:

• Installation and activation events, event times, session information, and whether this is the first recorded launch.
• The approved eligible registration, first-document creation, paywall-view, and subscription-trial event categories described above, when their production controls are enabled.
• If paid-event reporting is separately approved and enabled, the verified Billinger subscription charge amount and currency, plus a predefined billing-environment category. These are subscription purchase details, not amounts from your invoices or estimates. No payment-card details, transaction identifiers, receipts, or signed transaction payloads are supplied as event parameters.
• SDK-generated installation or device identifiers, measurement-permission and configuration flags, and supported attribution or campaign information when available.
• Technical app and device information such as app identifiers and versions, SDK version, operating system, device model, language, time zone, carrier or network information, and technical screen dimensions or device characteristics.
• IP address as part of network communications and general region information that may be inferred from network or device data; this is not precise GPS location.
• Limited SDK diagnostic information, such as technical errors or crash information, when the SDK’s diagnostic functions apply.

SDK initialization itself may contact Meta and process technical information before an event appears in a reporting dashboard. In the intended enabled flow, initialization is therefore subject to the same required consent and authorization controls.

SDK-generated identifiers should not be assumed to be anonymous merely because Billinger does not attach your account name. The current Meta configuration keeps IDFA collection disabled even if you authorize tracking.

Information excluded and restricted features

Billinger does not provide Meta event parameters or launch payloads containing client or business names, contact details, invoice or estimate numbers, line items, notes, document amounts, tax identifiers, bank details, payment instructions, PDFs, logos, handwritten signatures, or other user-entered financial or document content. We do not supply Firebase user IDs, Apple account identifiers, email addresses, or phone numbers for Meta matching. Raw launch URLs and notification payloads are not forwarded to this integration.

Our configuration disables automatic app-event and StoreKit purchase logging, additional screen-title and AppLink URL metadata, and automatic product-improvement collection. Technical screen dimensions are not screenshots, screen layouts, or document contents. The planned production setup also excludes automatic advanced matching and codeless collection of screen contents; those provider controls are part of the required validation before rollout.

Optional consent, controls, and withdrawal

When the feature is offered, sharing is off by default. Billinger will ask for a separate, optional advertising-measurement choice after the main app is ready. If you opt in, Billinger will also request Apple’s App Tracking Transparency authorization when eligible. This integration requires both your in-app agreement and authorized tracking status before SDK measurement can start. ATT authorization alone is not treated as satisfying every applicable consent requirement.

Declining, dismissing the invitation, or leaving the option off does not prevent normal Billinger use. Denied or restricted tracking authorization does not cause Billinger to substitute another identifier to bypass your choice.

When this feature is available, you can change the in-app preference at Billinger Settings → General → Advertising Measurement. The entry is not shown while the feature remains unavailable. Your app-level choice and its date are stored locally on your device.

You can separately manage Apple’s authorization in iOS Settings → Privacy & Security → Tracking, under Billinger. The label or availability may vary by iOS version, region, or device restrictions. See Apple’s tracking-permission guidance.

Turning off the in-app choice or withdrawing ATT authorization stops new explicit activation and conversion submissions made by Billinger. Billinger reinforces restrictive SDK settings, stops automatic flushing through its suspension path, and does not resume measurement in that app process. The SDK has no public shutdown or queue-purge API: requests already in progress cannot be recalled, previously queued SDK data cannot be guaranteed to be erased, and withdrawing consent does not erase information Meta has already received. Reopening the app does not bypass consent or ATT, and persisted SDK data-use restrictions may remain. See Sections 16, 17, and 20 for retention and privacy requests. Real-device withdrawal and re-consent behavior must be approved before production measurement is enabled.

Apple also provides privacy-preserving attribution technologies that can operate without ATT permission. Their existence does not authorize bypassing your tracking choice; this integration does not initialize the full Meta SDK for denied or restricted users solely to obtain such attribution.

Third-party processing

When measurement is enabled and authorized, Meta may associate measurement information with information it holds from its services or other sources to provide attribution, reporting, and related advertising services under its applicable terms and privacy practices. Billinger’s purpose for this optional sharing is measuring its advertising, not making private client or financial documents available for advertising.

Meta’s processing, retention, and available rights are also described in the Meta Privacy Policy and its Business Tools Terms. Required disclosures and choices will be reviewed before rollout, including where advertising-related sharing is subject to additional local requirements.

24. Third-Party Services

Billinger may use services provided by third parties including:

• Sign in with Apple
• Apple App Store
• Apple StoreKit
• Apple Push Notification Service
• Google Firebase Authentication
• Google Cloud Firestore
• Google Firebase Storage
• Google Firebase Analytics
• Google Firebase Crashlytics
• Google Firebase Cloud Messaging
• Google Firebase Remote Config
• Google Cloud infrastructure
• Meta Platforms, for optional advertising measurement if made available and enabled as described in Section 23

These providers operate under their own privacy policies, terms, and data protection practices.

25. Legal Bases for Processing

Where applicable data protection law requires a legal basis for processing personal information, we may process information based on:

• Performance of a contract — where processing is necessary to provide Billinger functionality requested by you
• Legitimate interests — including improving Billinger, maintaining security, preventing abuse, analyzing product performance, and diagnosing technical problems
• Consent — where required by law or where you provide permission for specific functionality
• Legal obligations — where processing is necessary to comply with applicable laws

Where processing is based on consent, you may withdraw that consent where permitted by law.

Optional Meta advertising measurement is subject to the specific in-app choice, Apple tracking authorization, and any additional applicable requirements described in Section 23. It is not enabled solely on the basis of using Billinger, acknowledging this policy, or our general legitimate interests in product improvement.

26. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect:

• Changes to Billinger features
• Changes to service providers
• Changes to data practices
• Legal or regulatory requirements

When we update this Privacy Policy, we will update the Effective Date shown at the top.

If changes are material, we may provide additional notice where required by applicable law.

27. Contact Us

If you have questions, concerns, requests, or complaints regarding this Privacy Policy or Billinger’s privacy practices, contact us at: meri.arakelyan.developer@gmail.com