1. Who this covers
This policy is published by Wrights Creative Services, L.L.C. ("we", "us", "our"), a limited liability company in Texas, United States, trading as WrightsCS. It applies to the apps we publish under our own name on the App Store and Google Play, to their companion desktop, watch and web versions, and to this website at wrightscsapps.com. Section 3 names them.
We also build apps under contract that are published under a client's own developer account. Those apps are covered by this policy only where the client's store listing points here; otherwise the client's own policy governs, and the client — not us — decides what is collected and why. Section 15 explains that split, which matters because it determines who you ask to exercise your rights.
We are the data controller for the apps we publish ourselves. For client-published apps we normally act as a processor on the client's instructions.
2. The short version
- No account, in most cases. The majority of our catalog is usable without signing up, and an app that needs no account creates no profile on our servers.
- On-device by default. Where an app can keep your content on your own device, it does. Notes, settings, saved items and offline records live in the app's own storage and are not uploaded unless the app's purpose is to sync or submit them.
- No sale of personal information, ever. We do not sell it, rent it, or hand it to data brokers, and we do not use it to build cross-app advertising profiles.
- Deletion is a real button. Apps with accounts offer in-app deletion, and §11 gives you a route that works even if you have already uninstalled the app.
- Sensitive permissions are asked for in context. An app asks for location, camera or the like at the moment the feature needs it, explains why, and keeps working in a reduced form if you decline.
3. Apps covered by this policy
This policy covers the following titles, together with their iOS, iPadOS, watchOS, macOS, Windows, Android and web editions, and any app we publish after the date at the top of this page:
Published by Wrights Creative Services, L.L.C.
- #nowplaying Mac
- AerialCamping iOS · Android
- AppRelay iOS · Android · Mac · Windows
- AutoDrive iOS · Android
- AutoDriveDesktop Mac
- Bored iOS · Android
- FireDash iOS · Android
- FlashCam iOS
- iCarbons iOS
- inSured iOS
- Inventory Control System iOS · Android
- Mobile Kiosk iOS
- Mobile Profiles iOS
- MusicCenter iOS
- PowerCenter Pro iOS
- PowerLock iOS
- QuitUnexpectedly iOS
- RiskDash iOS · Android
- Scanners iOS · Watch
- ShootSmart iOS · Android
- StickrMe iOS
- Wedge iOS
We also build apps that are published under a client's own developer account. Those are not listed above and are not covered by this policy, except where the client's own store listing links here — §15 explains which situation you are in and who to ask about your data.
An individual app may publish a supplementary notice of its own where it does something this page does not describe. Where the two differ, the app's own notice governs for that app, and this policy covers everything the notice is silent about.
4. What we collect
No single app collects all of this. Each item below says which kind of app it applies to. If an app never offers you the feature described, it collects nothing under that heading.
4.1 Information you give us
- Account details — in apps that offer accounts: your email address, a display or contact name, and a password, which we store only as a one-way hash and never in readable form. An app bought by an employer may also record the organization, site or team you belong to and the role it gives you.
- Content you create — whatever the app exists to record. In an inspection or field app that is the records, readings, notes, signatures and photos you enter; in a reference or planning app it is your saved items, calculations and preferences. Content stays on your device unless the app's purpose is to sync it between your devices or submit it to an organization you work for.
- Support correspondence — your email address and whatever you write to us when you report a bug or ask a question, including any screenshots or logs you choose to attach.
- Feedback and reviews you send us directly. Reviews left on a store listing are handled by Apple or Google, not by us.
4.2 Information collected automatically
- Device and app data — device model, operating-system version, app version and build, language and region, and screen class. We use it to reproduce faults and decide which OS versions to keep supporting.
- Crash and performance diagnostics — in apps that include Firebase Crashlytics: a stack trace and the device state at the moment of a crash, tied to a randomly generated installation identifier rather than to your name. If you are signed in, a crash report may carry your account identifier so we can tell whether a fault hit one account or everybody.
- Usage analytics — in apps that include Firebase Analytics: which screens are opened and which features are used, as counts tied to a pseudonymous app-instance identifier. We use it to see what is worth building and what nobody touches. It is not used to target advertising to you.
- IP address and server logs — when an app talks to our servers we record the request, the time and the originating IP address, for security, abuse prevention and debugging. An approximate city or country may be derived from the IP address; this is not GPS location.
- Push notification tokens — in apps that send notifications: the token Apple or Google issues for your installation, so a message can be routed to it. The token identifies an installation, not you, and is discarded when it stops working.
4.3 Device features, only with your permission
These are collected only after the operating system has asked you and you have said yes, and only in the apps whose features need them. You can withdraw any of them at any time in iOS or Android settings; the app will keep working with that feature reduced or switched off. Section 6 maps each permission to the feature that uses it.
- Location — precise or approximate, used for things like placing an asset on a map, finding what is near you, stamping an inspection with where it happened, or giving distance and bearing. A few field apps can collect location in the background while a job is running; where that is the case the app says so before asking, and the platform shows you an indicator while it happens. We do not use location for advertising and we do not sell it.
- Camera and photo library — to take or attach pictures: an inspection photo, a profile picture, a scanned code, a document. We receive a photo only when you take or choose one, never a scan of your library.
- Microphone — for voice notes, dictation and recording features where the app offers them. Recording happens only while the feature is active.
- Contacts and calendar — only where an app's purpose is to invite, assign or schedule. We read the entries needed for the action you asked for and do not upload your address book.
- Health, fitness and motion data — in apps that offer these features, read from Apple Health or the platform's sensors with your explicit consent. This is sensitive information and we treat it as such: it is used only to show you the feature you enabled, it is never used for advertising, and it is never sold or shared for anyone else's purposes.
- Bluetooth and local network — to find and talk to nearby accessories or a companion app on your own network. Discovery data stays on the device.
- Biometrics — where an app offers Face ID, Touch ID or fingerprint unlock, the check is performed by the operating system and the app is told only whether it passed. We never receive your fingerprint or face data.
4.4 Purchases and subscriptions
Paid apps, in-app purchases and subscriptions are processed by Apple or Google, and website purchases by Stripe. We never see or store your card number. We receive a confirmation that an entitlement is valid — a receipt or purchase token, the product bought, and its status — which is what unlocks the paid features and lets us honor restores on a new device. Refunds, tax and billing details are handled by the store or by Stripe under its own policy.
4.5 Advertising
Most of our apps carry no advertising. Where a free, ad-supported app does, it uses Google AdMob, which may use your device's advertising identifier and general location to select ads and measure them.
- On iOS no tracking identifier is used for advertising unless you allow it at the App Tracking Transparency prompt. Decline and you still see ads, just untargeted ones.
- On Android you can reset or delete your advertising ID, and opt out of personalized ads, in Settings → Privacy → Ads.
- We never pass your name, email address, account, health data, or the content you create in an app to an advertising network.
An app's store listing states whether it contains ads. Google's handling of ad data is governed by the Google privacy & terms.
4.6 This website
Browsing wrightscsapps.com is not tracked across sites. Standard web-server logs record the request and IP address for security and reliability. If you use the contact form we receive what you type into it, plus the IP address it was sent from, which we keep as an anti-abuse record.
5. Why we use it
| Purpose | What it uses | Legal basis (UK/EU) |
|---|---|---|
| Running the features you asked for | Account details, your content, permitted device features | Performance of a contract |
| Keeping your account secure and preventing abuse | Email address, IP address, sign-in events | Legitimate interests; legal obligation |
| Fixing crashes and faults | Device data, diagnostics | Legitimate interests |
| Understanding which features get used | Pseudonymous usage analytics | Legitimate interests, or consent where required |
| Answering your support request | Your correspondence | Performance of a contract; legitimate interests |
| Selling and honoring paid features | Purchase and entitlement records | Performance of a contract; legal obligation |
| Sending notifications you turned on | Push token | Consent |
| Showing ads in a free, ad-supported app | Advertising identifier, general location | Consent |
| Using sensitive data — health, precise background location | Only the category you enabled | Explicit consent |
| Meeting tax, accounting and legal duties | Purchase records | Legal obligation |
We do not make decisions about you by automated means that have a legal or similarly significant effect, and we do not profile you for advertising.
6. Device permissions and what each is for
An app requests only the permissions its own features need, at the point of use. This table covers everything any of our apps may ask for; a given app will ask for a small subset.
| Permission | What it is for | Leaves your device? |
|---|---|---|
| Location (while in use) | Maps, nearby search, distance, stamping a record with where it was taken | Only when attached to a record you submit |
| Location (background) | Continuing a job or route while the app is not in front — field apps only | Only when attached to a record you submit |
| Camera | Taking an inspection or profile photo, scanning a code | Only photos you attach |
| Photo library | Attaching an existing picture, saving one you exported | Only photos you choose |
| Microphone | Voice notes, dictation, recording features | Only recordings you save and submit |
| Contacts | Inviting or assigning someone without retyping their details | Only the entry you pick |
| Calendar | Writing a scheduled job or reminder into your calendar | No |
| Health & fitness | Reading or writing the metrics a health feature shows | No, unless the app's purpose is to sync them |
| Motion & sensors | Step, orientation and movement features | No |
| Bluetooth | Connecting to a nearby accessory | No |
| Local network | Finding a companion app or device on your own network | No |
| Notifications | Sending the alerts you turned on | Push token only |
| Biometric unlock | Locking the app behind Face ID, Touch ID or fingerprint | No — we get a pass/fail, never the biometric |
| Files & storage | Importing or exporting a document, saving a report you generated | Only files you export |
Declining a permission never locks you out of an app. The feature that needs it is unavailable or degrades — a map without your position on it, a record without a photo — and the rest works normally.
7. Who we share it with
We share personal information only with the categories of recipient below, only for the purposes given, and only to the extent each one needs. Every provider is bound by contract to use it for our purposes and no other.
| Recipient | What they receive | Why |
|---|---|---|
| Google (Firebase Analytics, Crashlytics, Cloud Messaging) | Diagnostics, pseudonymous usage events, push tokens, device and app data | Crash reporting, product analytics, delivering notifications — privacy terms |
| Google AdMob — ad-supported apps only | Advertising identifier, general location, ad interactions | Selecting and measuring ads — privacy policy |
| Apple | Purchase receipts, push tokens, crash reports you opt to share with developers | App distribution, payments, notifications — privacy policy |
| Stripe — website purchases only | Payment and billing details, which it collects directly | Processing payment — privacy policy |
| Hosting and email providers | Whatever is stored on or sent through our servers | Running the service: hosting, database, backups, transactional email |
| Your organization — apps licensed to an employer | The records you submit and your activity within the organization's account | It is the organization's own data, submitted on its behalf — see §15 |
| Our client — apps published under a client's name | Whatever that app is built to collect | The client is the controller; we operate the app for it — see §15 |
| Law enforcement or a court | Only what a valid, specific legal demand compels | Legal obligation. We require lawful process, object to overbroad demands, and tell you unless we are forbidden to |
| A buyer, in a merger or sale of the business | The records connected to the app being transferred | Continuity. You would be told before it took effect, and this policy would bind the buyer until it published its own |
7.1 Services used only in certain apps
Beyond the providers above, an individual app may include one of the components below. Each is named here so this policy stays comprehensive, but none of them is in every app, and most of our catalog contains none of them. The Data safety section of an app's Google Play listing and the App Privacy label on its App Store listing are authoritative for that title.
| Component | What it receives | Why it is there |
|---|---|---|
| Google Maps / Play services location | Map tile requests and, for a map centered on you, your approximate or precise location | Drawing the map and placing things on it — privacy policy |
| Google User Messaging Platform | Your consent choice for advertising | Showing the EU/UK consent form in an ad-supported app and recording your answer |
| AppsFlyer | Device and installation identifiers, install and in-app events | Measuring which advert or link led to an install, in apps we advertise — privacy policy |
| Meta (Facebook) SDK | Your Facebook sign-in, and app events linked to a Facebook identifier | "Sign in with Facebook" and sharing, where an app offers them — privacy policy |
| OneSignal | Push token, device and app data, notification interactions | Delivering notifications in apps that use it instead of Firebase — privacy policy |
| AdColony / third-party ad networks | Advertising identifier, general location, ad interactions | Serving ads in a free, ad-supported app, alongside or instead of AdMob |
| Parse / self-hosted backend | Your account and the content you sync | Storing and syncing data for apps built on it, on servers we or our client operate |
Where an app includes an advertising or attribution component, it is "tracking" as Apple defines it, so on iOS the app asks for your permission at the App Tracking Transparency prompt and the component stays off unless you allow it. In the EU and UK an ad-supported app shows a consent form before any advertising identifier is read. Decline either and the app still works.
8. What we never do
- We do not sell personal information and never have — including under the broad definitions of "sell" and "share" in California and other US state privacy laws.
- We do not share it with data brokers or people-search services.
- We do not use your content to advertise to you, and we do not build cross-app or cross-site profiles of you.
- We do not use your content to train machine-learning models, ours or anyone else's.
- We do not read your content for any purpose other than running the app and, where you ask us for support, resolving the problem you reported.
- We do not collect anything from a permission you declined, and we do not re-prompt to wear you down.
9. Children
Our apps are built for a general audience and are not directed to children. Unless an app's store listing explicitly says it is designed for families or children, it is not intended for anyone under 13 (or the higher age of digital consent where you live — up to 16 in parts of the EEA and the UK), and we do not knowingly collect personal information from them.
Where an app is listed for families or children, it is built to the corresponding store rules — Google Play's Families policy and Apple's Kids Category requirements — which for us means: no behavioral advertising, no collection of persistent identifiers for advertising purposes, and no collection of personal information beyond what the app needs to function.
If you are a parent or guardian and believe a child has given us personal information, write to privacy@wrightscsapps.com. We will verify the request, delete the information and close any account, and confirm to you when it is done.
10. How long we keep it
We keep personal information only as long as it is doing a job, then delete it. Where a period below is a maximum, we delete sooner if the purpose ends sooner.
| What | How long |
|---|---|
| Account details | While the account exists. Deleted within 30 days of a verified deletion request |
| Content you created in an app | Until you delete it, or with the account. Content submitted into an organization's account belongs to that organization and follows its retention rules |
| Crash and performance diagnostics | Up to 90 days |
| Usage analytics | Up to 14 months, pseudonymous throughout |
| Server logs and IP addresses | 90 days |
| Push notification tokens | Until the token expires, you turn notifications off, or the app is uninstalled |
| Support correspondence | 24 months after the last message, then deleted with its whole thread |
| Purchase and tax records | As long as tax and accounting law requires — generally 7 years |
| Backups | Rotated out within 90 days, so deleted data clears backups within that window |
| Security and abuse records | Up to 24 months; failed sign-in attempts 90 days |
After a deletion request we may keep a minimal record for the narrow purposes the law allows — security, fraud prevention, and tax or accounting compliance. That means the fact a purchase happened, not what you did in the app. Section 11 sets out exactly what survives and why.
11. Deleting your account and your data
- In the app — open Settings (or your profile), then Account, then Delete account, in any of our apps that offers accounts. The app will confirm, then delete.
- By email, from anywhere — write to privacy@wrightscsapps.com with the name of the app and the email address or username on the account. We will verify that it is yours, delete it, and email you when it is done. No account, password or app required.
There is also a standalone deletion page covering the same ground on its own URL — that is the address we give Google Play, so it stays reachable even if this policy is restructured.
We acknowledge a request within 7 days and complete it within 30 days, which is the window the GDPR and the US state privacy laws allow. Deletion is permanent and is not reversible — deactivating, disabling or "freezing" an account is not what this does, and is not something we offer in place of it.
What is deleted: your account and sign-in credentials, your display name and contact details, the content you created and still own, your preferences, your push tokens, and the links between your account and any diagnostics.
What survives, and why:
- Purchase and tax records — the fact of a transaction, its amount and date. Tax and accounting law requires us to keep these, and deleting them is not something we may lawfully do. They stop being linked to a live account.
- A minimal security record of serious abuse or fraud, where deleting it would defeat the purpose of having it. Kept under the retention periods in §10.
- Records belonging to an organization. If you used an app under an employer's or a client's account, the inspections, reports and other records you submitted are that organization's data, not yours to delete — we cannot erase a company's business records on an individual's request. We will delete your personal account and remove your identity from what we lawfully can, and we will tell you who to ask about the rest. See §15.
- Anonymous aggregates that no longer identify anyone — counts and totals. These are not personal information and are not reconstructible.
Deleting without deleting your account. You do not have to go all-or- nothing. You can ask us to delete a specific category instead — your diagnostics, your analytics, your support history, the IP addresses in our logs — and keep using the app. Ask at privacy@wrightscsapps.com.
Apps with no account. If an app never asked you to sign up, we hold nothing tied to you: deleting the app from your device deletes its data. Where diagnostics were sent under a random installation identifier, uninstalling ends the collection, and you can ask us to delete what was already received.
12. How we protect it
- In transit — everything our apps send travels over HTTPS/TLS with modern cipher suites. Our apps refuse plaintext HTTP.
- At rest — passwords are stored only as salted one-way hashes (Argon2id, or bcrypt where Argon2 is unavailable); we cannot read them and neither can anyone who obtains the database. Credentials and tokens on your device are held in the iOS Keychain or the Android Keystore, not in plain files. Server databases and backups sit on encrypted storage.
- Access — production data is reachable only by the few people who need it to run the service, over authenticated connections, and multi-tenant apps keep each organization's records separated at the query level.
- Minimization — the strongest protection we apply is not collecting things. Where a feature can work on your device, it does.
- Breach notification — if a breach affects your personal information we will notify you and the relevant regulator within the deadlines the law sets, without waiting to have every answer first.
No system is perfectly secure, and we will not pretend otherwise. If you find a vulnerability in one of our apps, please tell us at privacy@wrightscsapps.com — we will work with you and we will not pursue good-faith research.
13. Your privacy rights
Wherever you live, you can ask us to do any of the following, and we will do it or explain why we cannot: know what we hold about you, get a copy of it in a portable format, correct it, delete it, restrict or object to how we use it, and withdraw a consent you gave.
Write to privacy@wrightscsapps.com. We respond within 30 days (extendable once, where the law allows and the request is complex — we will tell you). We will ask for enough information to be sure the account is yours, and nothing more. Exercising a privacy right is free, and we will never degrade an app, charge you, or offer you a worse price for it.
If you are in the UK, EEA or Switzerland
You have the rights above under the UK GDPR and the EU GDPR, and the right to lodge a complaint with your supervisory authority — the ICO in the UK, or your national data protection authority in the EEA. You may do that without contacting us first, though we would rather you gave us the chance to put it right.
If you are in California
Under the CCPA as amended by the CPRA you have the rights to know, delete, correct and obtain a portable copy, the right to opt out of the sale or sharing of personal information, the right to limit the use of sensitive personal information, and the right not to be retaliated against for exercising any of them. We do not sell or share personal information, so there is nothing to opt out of — and because we use sensitive personal information only to deliver the feature you asked for, the right to limit does not bite either. We honor Global Privacy Control signals on this website. The categories we collect, our purposes and the recipients are listed in sections 4, 5 and 7, and our retention periods in 10. You may use an authorized agent, with proof that you appointed them.
If you are in another US state
Residents of states with comprehensive privacy laws — including Colorado, Connecticut, Virginia, Utah, Texas, Oregon, Montana and the states following them — have equivalent rights to access, correct, delete, port, and opt out of targeted advertising, sale and profiling, plus the right to appeal a decision we make. To appeal, reply to our response and say so; we will reconsider and answer in writing, and tell you how to contact your state Attorney General if you are still unsatisfied.
14. International transfers
We are based in the United States and our servers and providers are primarily in the United States. If you use our apps from outside it, your information is transferred to and processed there, where privacy law differs from your own. Where we move personal information out of the UK or EEA we rely on the European Commission's and the UK's Standard Contractual Clauses, or another lawful transfer mechanism, and we assess whether additional safeguards are needed. You can ask us for details of the mechanism that applies to you.
15. Apps we build for other companies
A good part of our work is building apps that ship under someone else's name. Who you ask about your data depends on which situation you are in, so here is the distinction stated plainly.
- Apps we publish ourselves. We are the controller. This policy governs, and you ask us — privacy@wrightscsapps.com.
- Apps published under a client's developer account. The client is the controller: it decides what the app collects and why, and its own privacy policy — linked from its store listing — is the one that governs. We act as its processor, under a written agreement that confines us to its instructions, forbids us from using the data for our own purposes, and obliges us to help it answer your requests. Ask the client first; if you cannot reach them, write to us and we will route it.
- Apps licensed by your employer or organization. Your organization controls its own account and the records in it. We cannot delete an organization's business records on an individual's request, and we will not hand an organization's data to an individual without its authority. Your own personal account is a separate matter and you can always have it deleted — see §11.
If you are not sure which of these applies to an app, ask us and we will tell you who the controller is.
16. Changes to this policy
We update this page when what we do changes. The date at the top always reflects the current version. If a change materially affects how we handle your personal information — a new category collected, a new purpose, a new kind of recipient — we will give you notice before it takes effect, in the app or by email to the address on your account, and we will ask for fresh consent where consent is the basis we rely on. We do not apply a materially different use to information already collected without telling you first.
17. How to contact us
A real person reads this address and we answer every message.
- Privacy, data requests and deletion
privacy@wrightscsapps.com - App support
support@wrightscsapps.com - Anything else
hello@wrightscsapps.com or the contact form - Postal
Wrights Creative Services, L.L.C., Austin, Texas, United States
Wrights Creative Services, L.L.C. is the entity named on our App Store and Google Play developer listings, and is the entity responsible for the personal information described in this policy.