Roof Pitch Calculator:
Roofing

The following never leaves your phone. It is not uploaded, backed up to us, shared, or sold, because we have nowhere to put it:

• Pitch, angle and grade readings, including any reading you freeze or save
• Gauge calibration offset
• Roof sections — names, lengths, widths and pitches
• Materials inputs and results, including any price per bundle you enter
• Rafter runs, overhangs and results
• Projects, client names and saved project items
• Your business name for the PDF header, and the estimate number counter
• Your settings — units (imperial/metric), app language, bundle coverage, default waste percentage
• PDF estimates you generate

Technically this lives in the app's private storage (an on-device database and preferences file), and generated PDFs are written to the app's private cache directory. When you tap Export & share PDF, Android hands the file to whichever app you choose — that app's own privacy policy then applies to it.

• No account, no sign-up, no login, no email address collected
• No camera, no microphone, no photos
• No location — the app never requests or receives your location, GPS or otherwise
• No contacts, no phone number, no files outside its own storage
• No selling of personal information to anyone, for any purpose
• No advertising or analytics SDKs beyond the two Google services named below

The app declares no Android runtime permissions of its own. The permissions you may see listed on Google Play are added automatically by the Google advertising and Firebase libraries: internet and network-state access, the advertising ID permission, the Android Privacy Sandbox advertising permissions, wake lock, foreground service, and the Play install-referrer permission.

The app shows banner ads on the results tabs and, at most once per session, a full-screen ad after you have saved something. There are never any ads on the live pitch gauge screen, and none on the PDF estimate.

To serve those ads, Google AdMob collects and processes:

Advertising ID

A resettable Android identifier — used for serving and measuring ads, frequency capping and fraud prevention.

Coarse device and app info

Device model, OS version, app version, language, and a coarse region derived from your IP address — used for ad delivery and measurement.

Ad interaction events

Impressions and clicks — used for measurement and billing.

This data is transmitted to Google and is therefore shared with a third party under Google Play’s definition. We receive only aggregated, anonymous revenue reporting from it — never a list of users, never anything that identifies you.

Google’s handling of this data is governed by the Google Privacy Policy: https://policies.google.com/privacy and How Google uses information from sites or apps that use our services: https://policies.google.com/technologies/partner-sites

Your control: Android lets you reset or delete your advertising ID at any time in Settings → Privacy → Ads. Deleting it stops personalised advertising; you will still see ads, but non-personalised ones.

The app uses Firebase Analytics, Firebase Crashlytics and Firebase Performance Monitoring to understand whether the tools are actually usable, to find crashes, and to see whether the app is fast enough.

This collection is off by default and only starts if you allow it (see the consent section below). When it is on, it sends:

• Usage events from a fixed, closed list — which calculator produced a result, whether you use imperial or metric, onboarding started or completed, which screen you started typing on, which features you used, which error message you saw, which tab you viewed, and a coarse revenue band for an ad impression.
• Crash reports — the technical stack trace, device model, OS version and app version at the moment of a crash.
• Performance data — app start-up time, screen rendering time and network request timings for the app's own ad and analytics traffic.
• Firebase’s own automatic events — first open, session start, app removal — plus a Firebase-generated app instance identifier.

What it can never contain. The analytics event list is a closed catalog in the source code with no free-text path: every value is a fixed keyword or a numeric band. It is not possible for the app to send a measurement, a roof dimension, a project or client name, a business name, a price, or a PDF — not by accident, and not by a future change that forgets the rule. The ad revenue figure is deliberately sent as a range rather than an exact value.

We use this only in aggregate, to decide what to fix and what to build next. It is not used to build a profile of you, and it is not shared with anyone beyond Google as our processor. Firebase data is governed by the Google Privacy Policy: https://policies.google.com/privacy and the Firebase privacy documentation: https://firebase.google.com/support/privacy

Everyone — the in-app switch. Settings → Usage statistics turns the Firebase analytics, crash reporting and performance collection on or off. Turning it off stops collection; ads are unaffected either way.

In the EEA, the UK and Switzerland. Before any ad or analytics data is collected, the app shows Google’s certified consent form (the Google User Messaging Platform, part of the IAB Transparency & Consent Framework). Your answer there is respected literally:

• If you do not consent, no analytics, crash or performance data is collected at all — regardless of the in-app switch. You will still see ads, but they will be non-personalised.
• Analytics collection requires your genuine consent to the relevant TCF purpose. We deliberately do not key it to whether ads can still be shown, because that signal stays positive after a refusal and would turn collection on for exactly the people who declined.

You can reopen that form at any time from Settings → Ad privacy choices and change your answer.

A note on device transfer. Your consent answer is tied to the device you gave it on. It is deliberately excluded from Android’s app backup, so a new phone asks you again rather than inheriting a decision you never made there. Your projects and settings do travel with Android backup so you do not lose your saved jobs.

The pitch gauge reads your phone’s rotation vector sensor (falling back to the game rotation vector) to work out the angle the phone is held at. Android does not require a permission for this, the readings are used only to draw the needle and the pitch readouts on screen, and they are never transmitted or stored — except when you deliberately freeze and save a reading, which stays on the device like everything else.

If your phone has no such sensor, the app falls back to manual entry and tells you so.

• On-device data: kept until you delete it in the app, clear the app's data, or uninstall the app. We hold no copy and set no expiry.
• AdMob data: retained by Google under Google’s own retention policy.
• Firebase Analytics data: retained on Google’s servers for the retention window configured for this app’s Firebase project, then deleted or aggregated by Google.
• Crash and performance data: retained by Google under Crashlytics and Performance Monitoring retention policies.

Depending on where you live, you may have rights to access, correct, delete or port your personal data, and to object to or restrict its processing (GDPR/UK GDPR), or to know about and opt out of the "sale" or "sharing" of personal information (CCPA/CPRA — we do not sell personal information, and the only sharing is the advertising ID transmission described above, which you control by resetting the ID or declining consent).

Everything you created is already in your hands — it is on your device only. You can view, edit and delete it in the app, or remove all of it at once by clearing the app’s data or uninstalling.

For the ads and analytics data, we cannot action an individual access or deletion request ourselves, because we never receive anything that identifies you and we have no way to link a record to a person. The effective controls are the consent controls and the advertising ID reset described above.

If you have a question or a request anyway, email contact@rombastudio.com and we will respond and help you route it correctly.

This app is a professional construction tool and is not directed to children under 13, and we do not knowingly collect personal information from children under 13. It is not part of Google Play's Designed for Families programme. If you believe a child has provided personal information, contact us at contact@rombastudio.com.

Data transmitted by the Google advertising and Firebase libraries is encrypted in transit. Data you create is held in the app’s private, sandboxed storage, which other apps on the device cannot read. No method of storage or transmission is perfectly secure, and we cannot guarantee absolute security.

Google processes AdMob and Firebase data on servers that may be located outside your country, including in the United States. Those transfers are made under Google’s own safeguards, described in the Google Privacy Policy: https://policies.google.com/privacy

If this app’s data practices change — in particular if any SDK is added or removed — this page and the app’s Google Play Data safety declaration will both be updated before the change ships, and the "Last updated" date above will change. Material changes will be noted on the page.

Romba Studio — questions, privacy requests or deletion requests: contact@rombastudio.com