Privacy policy
Version 1.0 · Effective 16 November 2026
This policy explains what Metally and metally.app do with personal data. "We" means the operator named in section 1. "You" means a user of the app or a visitor of the site. Earlier versions of this policy are available on request.
1. Who is responsible
Azmi Rutkay Biyik, trading as Significant Labs
Bonn, Germany
Email: hello@metally.app
We are the controller under the General Data Protection Regulation (GDPR). Write to hello@metally.app for every privacy request.
2. Summary
- Counting runs on your device. The counting model is inside the app.
- There is no account and no sign-up.
- Photos leave your phone only through photo sharing, feedback with pictures, a count you attach to a message, or files you export yourself.
- Usage statistics and crash reports are off until you turn them on.
- A few technical services run when the app starts. Section 9 explains them.
- Purchases go through Apple's App Store or Google Play. RevenueCat confirms your access.
- We do not sell personal data.
3. Data on your device
Metally stores everything you create on your device. This includes your counts, photos, marks, business details, location and address, signature, company logo, attachments, custom fields, report templates and settings. Original photos keep the metadata that your camera wrote, such as the capture time.
We have no access to this data. It stays on your device until you delete the count or the app.
- You are responsible for personal data of other people that you enter, such as names and drawn signatures. We never receive it from the app.
- Exports, such as PDF reports, marked images, CSV files and template files, go wherever you send them. The receiving app or service handles them under its own terms.
- Your device may back up app data to iCloud or to your Google account, depending on your device settings. Apple's or Google's terms apply to those backups.
4. Device permissions and the trial reminder
Metally asks for a permission only when you use the function that needs it. The operating system shows the request.
- Camera: to take photos of a stack.
- Photo library: to pick existing photos, and on iPhone and iPad to save exported images.
- Location: only for the address lookup in section 5.
- Notifications: only for the trial reminder below. On Android, this version of the app asks for no notification permission.
- Motion sensor: for the level shown on the camera screen. Its readings are not stored.
Apart from the address lookup in section 5 and the photos you choose to share (sections 6 and 7), nobody receives data through these permissions. You can withdraw each permission in your device settings.
If you accept a reminder before a free trial ends, the app schedules a notification on your device. Nothing leaves your phone for this reminder.
5. Address lookup
If the location-on-reports setting is on, the app reads your location when you take the first camera photo of a count. A count made only from picked photos gets no location. If the count later has no camera photo left, for example after Undo, its location goes too. The next camera photo then reads the location again. It uses medium accuracy. It then asks the operating system's geocoder for an address at those coordinates.
- Data: your coordinates at that moment.
- Recipient: Apple's geocoding service on iPhone and iPad. On Android, the system geocoder, which is usually provided by Google. These providers act under their own privacy policies.
- Purpose: to print the place of the count on your reports.
- Legal basis: Article 6(1)(b) GDPR, because you asked for this function. Otherwise Article 6(1)(f) GDPR, our legitimate interest in providing the function you turned on.
- Retention: the coordinates and the address are stored on your device with the count. We do not receive them.
- You do not have to provide this data. If you keep the setting off, reports show no address. Nothing else changes.
- How to stop it: turn the setting off, or withdraw the location permission in your device settings.
6. Photo sharing
Photo sharing is off by default. If you turn it on, the app uploads data from counts that you finish after that moment. Counts that you finished before, demo counts and unfinished counts are not uploaded. You can exclude a single count with its own sharing switch.
What is sent
- Each photo you counted. The app removes the metadata blocks from the original, such as location, capture time and camera details. It keeps the orientation and the full resolution.
- A new, smaller marked image.
- The results of the count: the marks, areas, edits, counts and your review choices, with timing relative to the start of counting.
- The item material and size, if you entered them, and the size of each photo.
- Technical details of the count: the model and its settings, and the counting time.
- App details: the app version and build, the operating system name and major version, and the exact phone model identifier.
- Random identifiers for the record and each photo, the upload day and the version of the sharing notice you accepted.
- Your feedback answer and note, if you gave them for this count, except an answer and note that section 7 holds back.
What is not sent
- Count title, project, supplier, delivery number, counted-by name, notes and place.
- Coordinates and address.
- Photo labels and photo notes.
- Length, grade and theoretical weight inputs.
- Attachments, signature, company name and logo, custom fields and report templates.
- The capture time and the camera metadata of the original photo.
- Any user, device, account or install identifier.
When and how
- Uploads of a count start when you close its result screen after you finish it, or at the next app start. The app must be open and have a network connection.
- Images upload only over Wi-Fi or Ethernet, unless you turn on the mobile-data setting for sharing.
- The record without images uploads over any connection.
- Recipient: Google Cloud Storage, a Firebase service, in the us-central1 region in the United States. Google acts as our processor. Apps can write to this storage but cannot read it.
- The upload request carries your IP address and an App Check token. App Check starts with the first upload. It proves that the request comes from the real app. On iPhone and iPad it uses Apple's App Attest or DeviceCheck. On Android it uses Google's Play Integrity. The attestation goes to Apple or Google and then to Firebase. Firebase keeps no attestation material. App Check tokens expire within days. Google processes these data to deliver and protect the request. They are not stored with the record. Legal basis: Article 6(1)(f) GDPR, our legitimate interest in a working and protected upload service.
- We then move the records from the storage to our own archive.
Purposes and recipients
The app shows a sharing notice before you turn sharing on. If you accept it, we use shared data only to develop, train, test and improve our counting products.
Service providers may process shared data for this purpose. These are cloud, AI and labeling providers. AI providers may, for example, suggest marks on a photo. They may be located in the United States.
Each provider works for us under a data processing agreement. We tell you which providers we use if you ask.
We do not sell shared data. We do not give it to other companies for their own purposes. We do not publish it. If another company takes over Metally, shared data and these rights move to it, and these uses still apply.
We delete photos that show people, vehicle number plates or personal information, and notes with personal data, when we notice them.
The record carries the version of the notice you accepted. If a later notice changes these uses, it applies only to data shared after you accept it.
Legal basis for sharing: your consent, Article 6(1)(a) GDPR.
Free counts
If the app offers free counts for turning on sharing, it shows how many. You keep the free counts you received if you turn sharing off later. Buying paid features never requires sharing.
Consent and withdrawal
- You give consent on the sharing notice in the app. You withdraw it with the sharing setting. The per-count switch excludes one count.
- Withdrawal stops future uploads. An upload that is running stops.
- Shared records carry no identifier that links them to you or your device. So we cannot find your earlier records on our own (Article 11 GDPR).
- If you describe a shared photo to us, we search for it. Give us the upload date, what the photo shows and the count. We then delete the matching raw copies from the storage and from our archive.
- If a service provider holds the matching data, we tell it about the deletion (Article 19 GDPR).
- A counting model that was already trained with the data is not retrained.
How long we keep shared data
- In the cloud storage: at least 7 days, and until a verified copy reaches our archive. We then delete the records from the storage. We do this regularly.
- In our archive: as long as we need the data to develop and test our counting products, and at the latest until they are all discontinued. Training and test sets must stay stable so that model versions can be compared.
- Photos that show identifiable people, number plates or personal information, and notes with personal data: deleted when noticed.
- Service providers keep data only as long as their task and their agreement with us require.
7. Feedback
After a count, the app may ask whether the count looks correct. This works even when photo sharing is off.
- Data sent with a Yes or No answer: the answer, the counts per photo, your review choices and the technical details of the count. Also the item material and size, the photo position and size, and the app, operating system, phone model, random identifiers and upload day from section 6, and the notice version. No photos.
- Data sent with the form: the same, plus your note if you wrote one. Please write no names, company details or other personal data in the note.
- If you choose to send the pictures of this count, the app also sends the photos, marked images, marks, areas and edits of this count, as in section 6. This does not turn on photo sharing for other counts.
- Once pictures of a count were sent, later records of that count still name each picture that still matches its photo, with the photo's current marks, areas and edits. An answer still sends no photo.
- If you exclude this count with its own sharing switch, an answer or a send uploads nothing. The card shows Not sent.
- Your phone holds back an answer and its note in two cases. First, you gave the answer while the count was excluded. Second, you tapped Cancel or turned on the count's switch before its upload finished. The note is then deleted from your phone. Later uploads of the count carry neither, until you give a new answer or send from the count's feedback card while the count is not excluded. Attaching the count to a message while it is not excluded also ends this: the answer then goes with the count. Cancel and the switch do not delete a record that already uploaded. A later upload can replace that record.
- If photo sharing covers this count (section 6), your answer and note go with its shared data, except an answer and note held back as above. Section 6 then applies: an edit uploads the count again, all its pictures upload, and the card shows no Cancel.
- For any other count, an answer or a send uploads a record of the count, as it is when it uploads. After the send ends, an edit of the count uploads nothing.
- A send can wait. Its record waits for a network connection. Its pictures wait for Wi-Fi or Ethernet, unless you turn on the mobile-data setting for sharing. While a send waits, the feedback card shows Cancel.
- While pictures wait, the record uploads without them. An edit during this wait uploads the record again. When the pictures upload, the record uploads once more.
- A send without pictures adds no pictures. Pictures that an earlier send left waiting still upload, unless you tap Cancel.
- Purpose: to measure and improve the quality of counting.
- Legal basis: your consent, Article 6(1)(a) GDPR, given when you tap an answer or send from the count's feedback card.
- Recipient, retention and deletion: as in section 6. Pictures sent with feedback have the purposes and recipients in section 6.
- How to stop it: while a send waits, tap Cancel. This stops what has not left your phone yet. You can also delete the count, or, if photo sharing is on, exclude the count with its own sharing switch. The switch stops every upload of this count, also feedback and waiting uploads. To stop future questions, choose not to be asked again.
Messages from the app
You can send us a message from the app, for example about a problem or an idea. You can attach one finished count to it.
- Data sent with a message: your text, the app version and build, the operating system name and major version, the phone model, the app language and the upload day. Also the random record identifier of an attached count.
- A message carries no user, device or install identifier. Please write no names, email addresses or company details in it.
- If you attach a count, the app also sends that count as "Send with captured pictures" on its feedback card does. These are the photos with their metadata removed, the marked images, and the marks, areas, edits and results, as in section 6.
- Your earlier answer for that count goes with it, also an answer held back as above. Your note goes too, unless a hold deleted it. The report details listed in section 6 are not sent.
- If photo sharing already covers the attached count, section 6 applies to it as before.
- When: the message uploads when you tap Send. It needs a network connection and does not wait. If the upload fails, the app keeps your text and sends nothing.
- The attached count's pictures wait for Wi-Fi or Ethernet, unless you turn on the mobile-data setting for sharing.
- The upload request carries your IP address and an App Check token, as in section 6.
- Recipient: the cloud storage in section 6, as our processor. We then copy messages to our own archive. Service providers may process them as section 13 describes.
- Purpose of a message: to handle the problems and ideas you report and to improve Metally.
- An attached count is shared as pictures sent with feedback. It has the purposes and recipients in section 6.
- Legal basis: Article 6(1)(f) GDPR, our legitimate interest in handling the problems and ideas you report and in improving Metally.
- An attached count is shared with your consent, Article 6(1)(a) GDPR. You give it when you attach the count and tap Send. The form shows what this shares under the count.
- While the attached count's pictures wait, tap Cancel on the count's feedback card to stop them. If photo sharing covers the count, the card shows no Cancel. Then exclude the count with its own sharing switch to stop them.
- Retention: as long as we need messages to develop and improve Metally, and at the latest until all our counting products are discontinued. Messages also stay in the cloud storage until we delete them there. An attached count is kept as in section 6.
- You can object to the processing of your messages (section 17).
- A message has no reply address, so we cannot answer it. For an answer, write to hello@metally.app (section 12).
Rating requests
After a finished job, such as a sent report, the app may ask you to rate Metally in the App Store or Google Play.
- The app shows Apple's or Google's review sheet, or its own dialog that opens the store page. A rating goes to Apple or Google under their own terms, not to us.
- Rules on your device decide when the app asks. They use counters: how often and when the app asked, which milestones it reached, and which counts you finished.
- The counters are stored with your other app data, as section 3 describes. They also run when usage statistics are off. We cannot read the rating counters on your device, so we do not process them there.
- Remote Config delivers the rules.
- If usage statistics are on, the app reports the requests, your answer in its own dialog and taps on Rate Metally. Section 8 covers this.
- The app has no setting for these requests. Deleting the app removes the counters from your device.
8. Usage statistics and crash reports
Both are off until you turn them on. The app asks you once about each, and you can change each choice in the privacy settings. Both work only in store builds of the app.
Usage statistics
- Data: events about how you use the app, with their details. In general words: screens and steps opened, counts started and finished, photos approved and edited, exports, report templates, paywall views, offers and purchases, sharing and feedback actions, rating requests, and settings chosen. The details are numbers and fixed choices, never your text or photos.
- Firebase also records automatic events, such as the first opening of the app, an app instance ID, your device model, operating system, app version, language, and a coarse location derived from your IP address.
- Not collected: the advertising ID, a user ID or user properties. Ad features are turned off.
- Recipient: Google (Google Analytics for Firebase), as our processor.
- Purpose: to understand how the app is used and to improve it.
- Legal basis: your consent, Article 6(1)(a) GDPR and § 25(1) of the German TDDDG.
- Retention: event-level and user-level data for 14 months. Aggregated reports without personal data stay longer.
Crash reports
- Data: the error type and the stack trace, which shows where in the app's code the error happened. Crashlytics adds device and app state data: device model, operating system, app version, time, and an installation ID. We add no custom keys and no app data.
- Recipient: Google (Firebase Crashlytics), as our processor.
- Purpose: to find and fix errors.
- Legal basis: your consent, Article 6(1)(a) GDPR and § 25(1) TDDDG.
- Retention: 90 days.
How to stop them: turn each setting off. Unsent crash reports are deleted the next time the app starts.
9. Technical services at app start
When the app starts, these services run without asking you.
- Firebase Installations creates a random installation ID for this app install. Remote Config uses it. Usage statistics and crash reports use it if you turn them on.
- Remote Config fetches app settings from Google, at most every 6 hours. Examples are offer rules, rating rules, limits and the review mode. The request carries your IP address, the installation ID, the app and SDK version, your language, country setting and time zone, and your operating system and its version.
- RevenueCat checks whether this install has a paid plan. Section 10 gives the details.
- Purpose: to deliver app settings and to know which features are open to you.
- Legal basis: Article 6(1)(f) GDPR. Our legitimate interest is a working app with current settings. For RevenueCat, section 10 gives the legal basis.
- Recipients: Google and RevenueCat, as our processors.
- Retention: Google keeps the installation ID until we delete it through Firebase. We cannot link it to you, so we cannot find it on request.
- How to stop them: the app has no setting for these services. The only way to stop them is to delete the app. Section 17 explains your right to object.
10. Purchases and offers
You buy paid features through Apple's App Store or Google Play. The store processes the payment. We never see your payment details.
- The app uses RevenueCat to confirm which purchases belong to this app install. RevenueCat creates a random app user ID for the install. We do not link it to your name or account. On Android, after you start a plan, RevenueCat's software also keeps this ID in Google's Block Store. With Google backup on, it can return after a reinstall or on a new device, so that your purchases stay linked.
- Data processed by RevenueCat: that ID, the store receipt or purchase token, the product, price, currency and storefront country, the app and operating system version, and the IP address of the request. Also your device model and brand, and your language settings. On iPhone and iPad also Apple's identifier for vendor, a device ID for one developer's apps. Also other technical details that RevenueCat's software adds to its requests, such as Apple's tracking status.
- When: each time the app starts, whether or not you bought anything, and while you use the app, whenever it needs your purchase status, plans or prices. Also at a purchase and when you restore purchases. On iPhone and iPad, the app also syncs purchases once, and again after you use the offer code screen, so that it finds a redeemed offer code.
- Purpose: to unlock paid features and to restore them on a new device, to show current plans and prices, and to check whether a discount can apply.
- Legal basis: Article 6(1)(b) GDPR while you have an active plan, including a free trial or an offer code, to perform the purchase contract. Otherwise Article 6(1)(f) GDPR, our legitimate interest in knowing whether this install has a paid plan, in showing current plans and prices, and in checking whether a discount can apply.
- You do not have to provide this data. The app has no setting for these requests. Without it, paid features cannot be unlocked. The free functions keep working.
- Recipients: RevenueCat, Inc., as our processor. Apple and Google as independent sellers under their own privacy policies. Google keeps the Block Store copy under its own terms.
- Retention: while we use RevenueCat. We ask RevenueCat to delete your data on request. We need the order ID from your store receipt to find it. If you never started a plan, the app user ID is not linked to you, so we cannot find it on request. A deletion covers RevenueCat's records, not the Block Store copy, which Google's terms govern. If the app stays on your device, its next request creates a new record under the same ID. So delete the app first.
Discount offers
The app can show you a discount on a paid plan for a limited time. Rules on your device decide when. They use counters of what you do in the app, such as paywall views, finished demos, free counts used and your return after a while. They also use your subscription status, for example a cancelled plan.
- The counters are stored with your other app data, as section 3 describes. They also run when usage statistics are off. We cannot read the counters on your device, so we do not process them there.
- Remote Config delivers the rules.
- If usage statistics are on, the app reports which rule started an offer. Section 8 covers this.
- These rules have no legal or similar effect on you. The store shows the price before you buy.
- The app has no setting for these rules. Deleting the app removes the counters from your device.
11. Website
Hosting
metally.app is hosted on Firebase Hosting by Google. Each visit sends your IP address, the time, the page, the referrer and browser data to Google's servers. Google uses them to deliver the page and to detect abuse. Google keeps IP data for a few months.
Legal basis: Article 6(1)(f) GDPR. Our legitimate interest is a secure and reliable website.
Your choice
The site stores your analytics choice in your browser's localStorage under the name "metally-consent". It stays in your browser until you clear it. Legal basis: § 25(2) no. 2 TDDDG. You can change the choice with the cookie settings link in the footer.
Analytics
Google Analytics 4 runs only after you accept it, and only when we have set up a property. It sets the cookies "_ga" and "_ga_" followed by an ID. It records pages viewed and interactions with them, such as sections seen, scrolling, link and button clicks, file downloads, FAQ answers opened and language changes. Google also records the browser, the device type, the page language and a coarse location derived from your IP address. Google signals and ad personalization are off. Ad storage is denied.
- Recipient: Google, as our processor.
- Purpose: to measure how the site is used and which store links are clicked.
- Legal basis: your consent, Article 6(1)(a) GDPR and § 25(1) TDDDG.
- Retention: event-level and user-level data for 14 months. Aggregated reports without personal data stay longer.
- How to stop it: choose Decline in the cookie settings. The site then deletes the analytics cookies.
Fonts and icons are served from metally.app. Nothing loads from other hosts before you accept analytics. Store links open Apple's or Google's sites and carry only placement and language tokens.
12. Email
If you write to hello@metally.app, we process your address, your name, your message and any attachments to answer you.
- Legal basis: Article 6(1)(b) GDPR if your request concerns a contract, such as a purchase or a refund. Otherwise Article 6(1)(f) GDPR, our legitimate interest in answering requests.
- Recipient: Namecheap, Inc. (Private Email), as our processor.
- We may use service providers and automated tools, including AI providers, to sort, summarize and draft answers to mail. They work for us under a data processing agreement. No such tool makes a decision with legal or similar effect on you.
- Retention: we delete mail when the request is resolved. We keep mail for up to 3 years after the end of the year of the last contact where we may need it to defend claims. Mail about purchases and refunds is business correspondence under German tax law. We keep it for 6 years, or 8 years where it belongs to the accounting records.
13. Service providers
These companies process personal data for us or receive it. We may use further service providers, including AI and automation tools, to process the data in this policy for the same purposes. Each works for us under a data processing agreement. Each processor is bound by a data processing agreement under Article 28 GDPR with the same level of protection as this policy.
| Provider | Role | Services | Location | Transfer basis |
|---|---|---|---|---|
| Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA. Where Google's terms provide, the contracting entity is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. | Processor | Cloud Storage for Firebase (us-central1), Firebase Installations, Remote Config, App Check, Google Analytics for Firebase, Crashlytics, Firebase Hosting, Google Analytics 4 | USA and EU | EU–US Data Privacy Framework (Google LLC is certified) and the standard contractual clauses in the Firebase and Google Cloud data processing terms |
| RevenueCat, Inc., 1032 E Brandon Blvd #3003, Brandon, FL 33511, USA | Processor | Purchase confirmation and restore, plans, prices and discount checks | USA | Standard contractual clauses in RevenueCat's data processing addendum |
| Apple Inc., One Apple Park Way, Cupertino, CA 95014, USA; in the EU Apple Distribution International Ltd., Hollyhill Industrial Estate, Cork, Ireland | Independent controller | App Store sales, App Attest and DeviceCheck, geocoding on iPhone and iPad | USA and EU | Apple's own policies and certifications |
| Google LLC; in the EEA Google Commerce Limited, Gordon House, Barrow Street, Dublin 4, Ireland | Independent controller | Google Play sales, Play Integrity, Block Store on Android, geocoding on Android | USA and EU | Google's own policies; EU–US Data Privacy Framework |
| Namecheap, Inc., 4600 East Washington Street, Suite 300, Phoenix, AZ 85034, USA | Processor | Mailbox for hello@metally.app | USA | Standard contractual clauses in Namecheap's data processing addendum |
| Cloud, AI, labeling and automation providers. We name them on request. | Processor | Processing shared data (section 6), mail (section 12) and other data in this policy for the purposes stated there | USA and EU | Data Privacy Framework where the provider is certified, and standard contractual clauses |
14. Transfers outside the EU
Google, RevenueCat and Namecheap process data in the United States. Further service providers may do so too. For each transfer we rely on two bases:
- the EU–US Data Privacy Framework, where the provider is certified. Google LLC is certified;
- the standard contractual clauses of the European Commission, which are part of each provider's data processing terms. They apply in any case, and alone if the Data Privacy Framework no longer applies.
Apple and Google, as independent sellers and attestation providers, transfer data under their own policies. You can ask us for a copy of the clauses we rely on.
15. How long we keep data
| Data | Retention |
|---|---|
| Data on your device (section 3) | Until you delete the count or the app. We hold no copy. |
| Address lookup (section 5) | On your device with the count. |
| Shared data and feedback (sections 6 and 7) | Cloud storage: at least 7 days, and until a verified copy reaches our archive. Archive: as long as we need the data to develop and test our counting products, and at the latest until they are all discontinued. |
| Messages (section 7) | As long as we need messages to develop and improve Metally, and at the latest until all our counting products are discontinued. Also in the cloud storage until we delete them there. |
| Rating counters (section 7) | With your other app data, until you delete the app. |
| Upload request data (section 6) | Google's terms. Not stored with the record. |
| Usage statistics (section 8) | 14 months for event-level and user-level data. Aggregated reports longer. |
| Crash reports (section 8) | 90 days. |
| Installation ID and app settings requests (section 9) | Google's Firebase retention. Google keeps the installation ID until we delete it through Firebase. We cannot link it to you, so we cannot find it on request. |
| Purchases (section 10) | While we use RevenueCat. Deleted on request with the store's order ID. If you never started a plan, we cannot find it on request. Google keeps the Block Store copy under its own terms. A deletion covers RevenueCat's records, not the Block Store copy, which Google's terms govern. If the app stays on your device, its next request creates a new record under the same ID. So delete the app first. |
| Offer counters (section 10) | With your other app data, until you delete the app. |
| Website hosting logs (section 11) | Google keeps IP data for a few months. |
| Website consent choice (section 11) | In your browser until you clear it. |
| Website analytics (section 11) | 14 months for event-level and user-level data. Aggregated reports longer. |
| Email (section 12) | Deleted when resolved. Up to 3 years to defend claims. Tax-relevant mail 6 or 8 years. |
16. Your rights
Under the GDPR you have these rights towards us:
- access to your personal data (Article 15);
- rectification (Article 16);
- erasure (Article 17);
- restriction of processing (Article 18);
- data portability (Article 20);
- withdrawal of a consent you gave, with effect for the future (Article 7(3)). Sections 6, 7, 8 and 11 say how;
- objection, as section 17 describes (Article 21).
To make a request, write to hello@metally.app. We answer within one month. For a complex request we may extend this by two months, and we tell you if we do.
Most data we hold carries no identifier that links it to you. We may then ask you for information that helps us find your data, for example the upload date and what a shared photo shows (Articles 11 and 12(6) GDPR). If we cannot identify you, we tell you, and some rights may not apply.
You can complain to a data protection authority, in particular in the EU country where you live or work. The authority responsible for us is the State Commissioner for Data Protection and Freedom of Information of North Rhine-Westphalia (LDI NRW), Kavalleriestraße 2–4, 40213 Düsseldorf, Germany.
17. Your right to object
You may object at any time, for reasons arising from your particular situation, to processing that we base on legitimate interests (Article 6(1)(f) GDPR). This covers:
- the address lookup, where it is not based on your request (section 5);
- the upload request data (section 6);
- messages (section 7);
- the technical services at app start (section 9), except the requests to RevenueCat while you have an active plan;
- the requests to RevenueCat in section 10, if you have no active plan;
- the website hosting logs (section 11);
- email we answer in our legitimate interest (section 12).
After an objection we stop the processing, unless we show compelling legitimate grounds that override your interests, rights and freedoms. Write to hello@metally.app.
The app has no setting for the technical services at app start or for the requests to RevenueCat. We cannot link an installation ID to you. So if you object, the only way to stop them is to delete the app.
We send no direct marketing by email, push notification or any other channel outside the app. Discount offers appear only inside the app, from the rules on your device in section 10.
18. What we do not do
- No account and no sign-up.
- No advertising and no advertising ID. The app removes the advertising ID permission on Android.
- No tracking across other companies' apps or sites.
- No sale of personal data.
- No profiling on our servers. The offer rules in section 10 run only on your device.
- No automated decisions with legal or similar effect on you (Article 22 GDPR).
19. Children
Metally is not directed at children. If you are under 16, ask a parent or guardian before you turn on photo sharing or usage statistics.
20. Security
- All connections use encrypted transport.
- Apps can write shared records to the upload storage but cannot read or list them. A newer version of a record can replace an older one.
- App Check lets only the real app use the upload service.
- The app removes metadata from photos before upload.
- Uploaded images cannot be overwritten.
21. Regional information
United Kingdom
If you are in the UK, the UK GDPR gives you the rights in section 16. The transfer bases in section 14 include the UK extension of the Data Privacy Framework and the UK addendum to the standard contractual clauses. You can complain to the Information Commissioner's Office (ICO).
Switzerland
If you are in Switzerland, the Federal Act on Data Protection gives you comparable rights. The transfer bases include the Swiss–US Data Privacy Framework for certified providers. You can complain to the Federal Data Protection and Information Commissioner (FDPIC).
United States
- We do not sell or share personal information as the California Consumer Privacy Act (CCPA) defines these words.
- We do not meet the thresholds that make the CCPA apply to a business. We still honor the requests in section 16 for residents of US states with privacy laws.
- We do not respond to browser Do Not Track signals, because we load analytics only after you accept them.
- We do not knowingly collect personal information from children under 13.
Brazil
If you are in Brazil, the Lei Geral de Proteção de Dados (LGPD) applies. Article 18 LGPD gives you rights that match section 16. Our contact for LGPD requests is hello@metally.app.
India
If you are in India, the Digital Personal Data Protection Act 2023 applies from 13 May 2027. You then have the rights it grants, including access, correction, erasure and grievance redressal. Our grievance contact is hello@metally.app.
Other countries
If your country gives you other rights over your personal data, write to hello@metally.app. We honor them where the law requires it.
22. Changes to this policy
- We may update this policy at any time, for example for new processing or a new law.
- The version line at the top shows the current version and its effective date.
- Where a change needs your consent, we ask for it in the app first.