1. Controller and contact
Srex Digital ApS (CVR 44123967), c/o Stig Rex Rørkær, Yrsavej 4, 2. th., 5200 Odense V, Denmark, is the controller for Haps account administration, product operation, security, support, and optional analytics.
Contact us about privacy or your rights by email or telephone. Stig Rex Rørkær is the current privacy contact; Srex Digital ApS has not appointed a formal data protection officer.
2. Personal data we handle
- Account and profile data: email address, optional display name, preferred language, timezone, your starting height and weight and your goal weight, email-verification state, age-confirmation time, account status, and account timestamps. Your starting height and weight and your goal weight are saved with your account and included in your export. When you choose to maintain weight, your goal weight equals your starting weight. Haps uses the sex, age, height and current weight entered during setup on your device to calculate your calorie target. When you save setup after registration, Haps saves these answers with your account, along with your tracking experience, initial and chosen goal, chosen weekly rate, measurement units and any calorie target you entered. These setup answers are included in your export, kept until account deletion and excluded from analytics. The resulting calorie target, starting height and weight, and goal weight are also saved with your account. Your goal weight does not change that calculation.
- Authentication and legal records: sign-in and verification information, Apple or Google account references where you choose social sign-in, device and session information, Android account-restoration credentials and their account and session links, and the versions and times of your legal-document acceptance.
- Calorie-ledger data: calorie targets, food names, calories and any macronutrient values you supply, portions, dates, times, timezone, and information needed to save and synchronise your records. Manually logged activities include their name, type, active calories, date and time. Haps uses activity names and patterns in recorded activity types, dates and times on your device to suggest activity icons. When a name is not recognised on your device, Haps may process that name online using Haps-hosted AI to suggest an icon across languages. This processing does not include your calories, activity history or diary dates. The name and suggestion are not retained for this processing or used for model training. You can change the icon before saving, and manual logging remains available offline.
- Meal-photo data: Before AI processing, Haps asks you to enable Scan images with AI. This shared account choice covers meal scanning, corrections, nutrition-label AI assistance and catalogue checks using OpenAI and Anthropic. Existing meal-scanning users must accept the updated choice again. You can change it in Privacy settings. Declining keeps manual logging and on-device label reading available; new AI sharing and pending catalogue AI checks stay paused until you allow them. Haps processes meal, snack or drink photos, all metadata available from the photo and camera session, your selected country, scan answers, estimates and corrections. Metadata can include camera and capture information, location and device identifiers where present. Haps retains the original metadata it receives. Relevant camera details are sent with the photo for AI analysis; free-text metadata and other fields unrelated to camera interpretation are not included in that analysis context. Haps does not collect location separately to fill missing photo metadata. Opening the meal camera can automatically upload a photo for analysis before you tap the scan action. An upload notice is shown in the camera. Haps privately retains meal conversations, current and proposed food values, recent changes, confirmation choices, unfinished messages and pending changes to support meal review. You can keep an unfinished scan on your device to continue later, or discard its local progress when closing it. Unsaved changes to a logged meal are discarded when you leave its review. Retention periods are described below. Photos and meal values are excluded from analytics.
- Food-search data: descriptions you search for and records available to your account. Any retained derived search data from earlier versions remains encrypted, is included in your private export, and is removed when the source changes or your account is purged. Private records and derived search data are excluded from public catalogue downloads and retrieval-model training.
- Connected-health data: your chosen provider and permissions, connection and update times, limited error information, daily active calories, timestamped body-weight measurements, and your newest available height. Haps also keeps account and source references needed to associate and synchronise these records. If you select Google Health or Apple Health, total calories, steps, distance and exercise duration can be kept in encrypted storage on your device. Google activity details pass through Haps without being retained on the server; Apple Health details are read on the device. Health Connect reads only active calories, body weight and height. Total calories include active and resting energy. The daily summary shows active calories as Burned and the resting part of a provider total as Passive; only active calories affect calories remaining. Weight and height do not change your calorie target.
- Packaged-food contribution data: your account reference, product barcode, name, brand, country, serving basis, reviewed calorie and nutrient values, cropped nutrition-label image, text read from the label, verification results, and publication, duplicate-check and contribution-point information. Product-front photos are no longer collected.
- Conversation feedback: a thumbs-up or thumbs-down rating linked to your AI meal conversation. A thumbs up shares no transcript. Only when you confirm sending a conversation for quality review does Haps retain the text conversation currently shown, its food details, available meal photos and AI processing results, recent changes and confirmation choices, and any optional improvement note you choose to write. Older reports keep the sharing restrictions that applied when they were submitted. Haps does not attach unfinished messages, account identifiers, diary dates, calorie targets or unrelated entries to that report; any personal details you include in your optional note are shared as written. Haps keeps a limited record of recent AI processing results for up to 72 hours to investigate mistakes. When you submit a report, an available copy can be retained with it until that report expires. Processing records, ordinary ratings and quality reports are not sent to analytics or used for model training. After rating a scan, you can separately confirm a training contribution, including the values currently shown in your review. This shares the retained photos, all available photo metadata, the scan result, your rating and optional reason with Haps for training and evaluation. Haps retains this separate copy indefinitely without account, conversation or scan identifiers. The photos, metadata or reason can still identify someone, so these contributions are not described as anonymous. Deleting an account, scan or rating does not automatically delete a contributed copy because Haps keeps no account link to it. Contact support about contributed data and your rights. Contributing is optional and is not required to scan, rate or log food.
- Food-correction data: the food or drink you report, its barcode or catalogue reference, your description, proposed edits, previous product values, your account reference, supporting sources and review decisions. Reports are stored privately. Descriptions are not sent to external AI or treated as evidence. Independently supported facts may update the shared catalogue; uncertain or conflicting reports require review. Existing diary entries are unchanged.
- Content safety: Haps checks names and optional brands submitted for shared catalogue publication and keeps screening results and review decisions. These checks do not send account identifiers, barcodes, photos, nutrition or diary details to an external screening provider. Private diary entries and AI meal results are not published to the shared catalogue or automatically sent for human review. Reports of offensive foods are reviewed and can prevent that contributor’s shared foods from appearing in the reporter’s future searches, without changing existing diary entries. Contact support to request removal of such a block. Account-linked screening and review records are included in your export and removed through account deletion; shared products can retain review information after the contributor link is removed.
- Nutrition-label assistance data: a cropped nutrition-panel image, recognised text, detected nutrition values, scan-quality information and temporary processing records. These are used to read the label and help you check the values. If you send label-scanner feedback, Haps also receives the available cropped panel, your optional note and scan details for quality review. Feedback images and notes are kept privately for up to 30 days from capture and can be processed with AI to investigate reported problems. A failed capture can be reported without an image. Sending feedback is optional and does not contribute it to model training.
- Notification data: your reminder choices, local reminder time, timezone, last sign-in or profile-check state, latest food-log activity, device platform, push token, delivery state, and limited diagnostic codes.
- Consent and analytics data: your separate analytics and advertising-measurement choices, applicable policy versions and acceptance records, historic preferences from older app versions, and processing records associated with submitted catalogue evidence. After analytics consent, Haps collects limited product actions, public-website usage measurements and technical context as described below.
- Launch-reminder data: for an existing request for one Haps launch update, your email address, confirmation and consent records, the page where you requested it, and a protected reference derived from your IP address as evidence of that consent.
- Technical and support data: IP address and security information, country derived from your network and any manual override, app and operating-system details, synchronisation status, limited crash diagnostics, support correspondence, privacy requests, verification and export-delivery records, and account-deletion information.
3. Where personal data comes from
Most data comes directly from you when you create an account, enter records, choose settings, contact support or make a privacy request. Sign-in providers supply authentication information when you choose social sign-in. Technical and security information comes from your device, browser, network and use of Haps. Haps can derive your country from your network address; it does not request your precise location for this purpose.
With Scan images with AI enabled, Haps may send a cropped nutrition panel to Anthropic for online label reading. On-device text recognition remains available when you decline, are offline or AI is unavailable. Haps also processes recognised text, detected nutrition values and information about the quality of the result. Image metadata is removed before forwarding. A private copy of the crop and temporary results remain for up to 10 minutes so you can check the values or include the crop in optional scanner feedback. Scanning alone does not submit it for quality review or training. Limited processing records remain until account purge to prevent duplicate submissions. Anthropic processes and retains this data under its applicable service terms. Manual calorie entry and local scanning remain available offline.
Packaged-food contribution data comes directly from you when you create or verify a food using a barcode and scanned nutrition label. With Scan images with AI enabled, creating or confirming that food submits the cropped nutrition-label photo and reviewed values for catalogue verification. Opening the camera or capturing a label alone does not submit retained catalogue evidence. Haps links the submission to your account for verification, duplicate checks, contribution points, security and abuse prevention. OpenAI processes the cropped label image without receiving your account identifiers or the values you entered. Only verified contributions can be published or qualify for points. Unreadable, incomplete, conflicting or failed evidence stays private for authorised review. Pending AI checks also require your current Scan images with AI permission; earlier meal-only grants do not qualify. Evidence processing and account attribution are required for this workflow; manual calorie entry remains available without it. Haps does not use advertising networks or data brokers to enrich your ledger.
Connected-health data comes from Google Health, Android Health Connect or Apple Health only after you choose Agree and connect and grant the relevant permissions. All three can supply active calories, body weight and height. Google Health and Apple Health can additionally supply total calories, steps, distance and exercise duration. Health Connect does not request or read these four extra activity types. Activity and weight imports begin on the day you connect. Haps may read older height records but retains only the newest valid height. Extra Google Health and Apple Health activity details stay in encrypted storage on your device; apart from the Passive figure, they are not shown in the daily summary. Haps does not read exercise names, notes, routes, heart rate, sleep, food or location from these connections. You choose the source for active calories and body measurements when multiple providers are connected. Haps requests only read access to Apple Health and never writes anything back. If Apple Health access to a data type is declined, that type may simply appear as unavailable. Google Health can update your Haps account while the app is closed. For new Health Connect and Apple Health connections, background updates start when you connect and grant the required device access, unless you have turned them off on this device. Existing connections that are already off stay off until you enable them. Background updates use the same permitted data and selected sources; device conditions may delay them. You can turn background updates off in Haps without disabling updates while the app is open. You can change permissions or disconnect at any time. Imported weight and height are stored and exported but do not change your calorie target, calories logged, calories remaining or calories over target.
4. Purposes and legal bases
- Contract and requested steps (GDPR Article 6(1)(b)): create and secure your account, save and synchronise your ledger, preserve local dates, provide recent-food, local-catalogue, scan, and copy features, follow your country override, deliver settings you request, and respond to support and privacy requests.
- Legal obligations (Article 6(1)(c)): keep records and respond to authorities where applicable law requires it, and handle data-protection requests.
- Legitimate interests (Article 6(1)(f)): protect Haps and its users, prevent abuse and duplicate contribution rewards, improve label scanning, verify, maintain and improve the shared packaged-food catalogue using cropped label evidence and reviewed nutrition, keep private supporting evidence and the account attribution needed for duplicate and eligibility checks, operate a reliable service and backups, keep limited security and diagnostic records, investigate incidents, and establish or defend legal claims, balanced against your rights.
- Consent (GDPR Article 6(1)(a)) and explicit consent for connected-health data (Article 9(2)(a)): connected-health access and optional product and website analytics stay off until you allow the relevant choice. Optional meal-photo training contributions require the separate confirmation described above; ordinary ratings do not grant this permission. Existing health connections may need their provider or operating-system permission completed again before Haps can read newly added data types. Google activity details use the activity-and-fitness read-only scope you approve when connecting. Health Connect asks for active-calorie, body-weight, and height read access, with optional past-data access only to find the newest height. Apple Health asks for total-calorie, step, distance, and exercise-duration read access alongside the core types; declining an optional activity type does not disable the types you allowed, and you can allow it later in the device's health settings. You can disconnect a health provider or switch the selected activity or body-measurement source at any time. Disconnecting Google Health removes its authorisation, connection and imported data from Haps; the original health data remains with Google. The launch reminder is a separate consent: nothing is sent until you confirm the address from the email we send, and every message carries a one-click opt-out.
5. Required and optional data
An email address, age confirmation, current legal-document acceptance, timezone, a calorie target, and the values required by a logging workflow are needed to create and use the relevant parts of Haps. Without them, those features cannot work.
A display name, social sign-in, food-entry name, macronutrient values, manually logged activities, country override, local food suggestions, connected-health access, online nutrition-label assistance, packaged-food contribution, push notifications, inactivity reminders, daily reminders, and analytics are optional. Submitting a packaged-food contribution requires its private cropped label image, reviewed nutrition values, account attribution and verification information to validate the product and determine eligibility for points. Creating or verifying a barcode product from a scanned label automatically submits this evidence. Manual calorie entry does not start this workflow. Product-front photos are no longer collected. You can leave connected health and optional analytics off, add foods manually, and use Haps without connecting another app, enabling notifications, or making a catalogue contribution. The launch reminder is entirely optional and is not connected to having a Haps account.
7. International transfers
Haps is designed to use EU regions for core hosting, analytics and transactional email. Global providers, including OpenAI, Anthropic and Cloudflare, and their subprocessors may nevertheless process data outside the European Economic Area.
Srex Digital ApS verifies every provider, subprocessor, selected region, retention control, data-processing agreement, and transfer route. Where required, a transfer relies on an adequacy decision or the European Commission’s Standard Contractual Clauses with appropriate supplementary safeguards. Provider and transfer details will be updated if the production configuration changes.
8. Analytics, website storage, and crash diagnostics
Separately from optional usage analytics, Haps may compare onboarding versions using totals of new account registrations during scheduled periods. We use our legitimate interest in improving onboarding and minimise this processing to registration counts. These comparisons do not use your food records, body measurements, profile answers or a history of your steps, and we do not send them to an analytics provider. We retain the comparison records for up to 90 days after a test ends or is stopped. Existing registration-statistics objections and explicit analytics refusals sent by older apps are respected. You can contact us about this processing and your right to object. Once counts are irreversibly anonymised, we cannot identify or remove an individual's contribution. This processing does not enable optional usage analytics or recordings.
Mobile Firebase Analytics and PostHog event collection are disabled until you choose optional analytics. Newer app versions offer optional analytics after onboarding or in Privacy settings. Older app versions may offer this choice during setup and, with consent, record a random experiment identifier, setup version, completed steps, errors and whether a new account is created. Profile answers are excluded. Haps also collects limited product actions and status information, such as sign-in method or whether a setting is enabled. With this consent, PostHog also receives label-scan success and failure counts, processing times, whether OCR or AI was used, and approximate country derived from the network request. Label photos, extracted text and nutrition values are excluded from these measurements. Food names, calories, targets, dates, email addresses, account identifiers and free text are excluded. After a new analytics choice under this policy, PostHog also records masked session replays to help us understand navigation and usability problems. Personal data, user content, inputs and personal images are hidden; camera previews, calorie information and health charts are excluded. Approved static button labels and navigation remain visible. Fixed screen names and selected action names help explain the journey; route parameters and personal values are excluded. Network requests, console logs and touch coordinates are not recorded. Earlier analytics choices do not enable replay. Withdrawal, sign-out or an account-deletion request stops new recordings. Previously delivered recordings remain subject to PostHog’s configured retention and privacy policy; withdrawal does not recall them.
After you choose analytics under this policy version, Haps also measures synced food-logging activity, free, trial, paid and complimentary membership, trial starts and first verified payments through PostHog EU. Haps shares monthly recurring subscription amounts and their currencies, derived from verified charges, to measure revenue retention, cancellations, downgrades and upgrades. A random measurement identifier links these observations across visits while your analytics choice remains current. Synced logging records when a new food entry reaches Haps, which can be later than an offline action; it excludes meal dates and food details. Purchase references, payment credentials, food data, email addresses and Haps account identifiers are excluded. Earlier analytics choices do not enable this measurement. You can refuse or withdraw through the same analytics setting. Withdrawal or an account-deletion request removes the local identifier and pending events; a later choice uses a new identifier. Pending delivery lasts up to 48 hours and local event records last up to 90 days. The measurement identifier, latest revenue observation and records used to prevent duplicate conversion counts remain while that analytics choice is current. Previously delivered events remain subject to PostHog's configured retention and privacy policy; withdrawal does not recall them.
The public website saves your analytics choice on your device. PostHog and Google Tag Manager load only after you choose “Accept all” or enable Analytics through “Customise” and save. “Reject all” refuses optional analytics and ad measurement; “Customise” lets you choose them separately. After analytics consent, Haps measures public-site visits, navigation, Google Play link clicks, time spent and how much content is viewed. PostHog receives temporary session and visit identifiers, time and content-depth measurements, without persistent identity, page addresses, titles, search queries, referrers or campaign parameters. After a new analytics choice under this policy, PostHog also records masked session replays to help us understand navigation and usability problems. Text, inputs and images are hidden; forms and calculator results are excluded. Replay does not record page addresses, network requests or console logs. Person profiles remain disabled. Google Analytics receives public-page addresses and names without query strings or fragments and referrers limited to the originating site. Historic launch-signup measurements recorded accepted requests, not confirmed email addresses; the homepage no longer collects launch-reminder addresses. Email addresses, form contents, body inputs and calculator results are excluded; advertising storage and personalisation remain denied. You can change your choice through “Analytics settings” in the site footer. Clearing Haps site data removes the saved choice.
Advertising-measurement choices are separate from analytics and off by default. You can change them in mobile Privacy settings or through Ad measurement settings in the website footer. After separate consent, Haps shares public-page visits and app-open events with TikTok, Meta, Reddit, Snapchat and Pinterest. Measurement can include IP address, browser or app and operating-system information, and provider advertising identifiers where permitted. Haps excludes form contents, calculator inputs, food, health data, email, account identifiers and free text. Pending mobile events are encrypted and may be retried for up to 48 hours; expired events are removed when measurement next runs. Withdrawal, logout or deletion discards pending events. Haps retains delivery receipts for up to 48 hours without event contents or IP addresses. Withdrawal stops new measurement but cannot recall data already received; provider retention and deletion follow their own policies. Analytics consent does not authorise ad measurement. Mobile measurement also requires iOS tracking permission, and withdrawal stops it on the device even while an account update is waiting for a connection.
Crash diagnostics are separate from optional analytics and may remain enabled to keep the mobile apps reliable. They include limited error types and technical stack traces; Haps removes handled error messages, nutrition and identity information. Unexpected software failures can expose unintended context, so Haps reviews and tests these protections.
9. Notifications and communications
Push notifications are off until you enable a reminder and grant the operating-system permission. Haps sends neutral notification text and a generic destination rather than food names, calorie values, or targets. Delivery depends on Firebase, Apple, Google, your device, and network availability and is not guaranteed.
We send service emails when needed for sign-in, privacy-request verification, export delivery, security, and support.
Haps runs no newsletter and no marketing campaigns. Existing launch-reminder requests cover a single Haps launch update after the address is confirmed, with an opt-out link in each message. Opting out erases the address. The homepage links directly to the iPhone and Android downloads and no longer collects launch-reminder addresses. Existing reminders are not repurposed as an iOS campaign.
10. How long data is kept
- Android security checks: temporary verification challenges expire after five minutes, completion markers after 24 hours and aggregate security-check counts after seven days. Haps does not retain integrity tokens, raw security assessments or lists of installed apps. Google's processing follows its own privacy terms.
- Active account, ledger, settings, consent, and synchronisation data are retained while the account is active and as needed to provide Haps.
- A connected-health connection attempt expires after 10 minutes. Connection information, daily active calories, timestamped weight and your newest valid height remain while the provider is connected. Extra Google Health and Apple Health activity details remain only in encrypted storage on that device and are removed on disconnection, signout or account switching. Google activity details are not retained on the Haps server. Haps deletes previously cached Health Connect total-calorie, step, distance and exercise-duration data when upgrading to the app version that removes access to those details; active calories, pending uploads, weight and height remain. Disconnecting removes the provider’s connection and imported records from Haps. If Google cannot temporarily revoke the connection, Haps retains the encrypted connection and imported records so you can retry. You can also withdraw permissions through the provider or device settings. Original records remain with the health provider, and Haps backups follow the expiry below.
- Email sign-in codes expire after 10 minutes, public privacy-request verification codes expire after 20 minutes, and API sessions expire after 90 days unless revoked earlier. Apple sign-in verification challenges expire after five minutes. Where available, Haps securely retains an Apple sign-in credential to disconnect that authorisation when you delete your account. Failed disconnections may be retried for up to seven days. The credential is removed after successful disconnection or account purge. If automatic disconnection is unavailable, Haps explains how to remove its access through your Apple Account; this does not delay account deletion. Android restore credentials are linked to active sessions. Signing out or revoking a session removes its link; if no active links remain, Haps deletes the credential. Expired sessions cannot authorise restoration. Account deletion also removes these credentials, and Haps asks the device provider to clear its copy on sign-out. Expiry stops use of the credential; limited security records may remain where necessary.
- A requested CSV export uses a private, single-use download link that expires after 72 hours. Haps aims to complete verified privacy requests within 25 days.
- Nutrition-label assistance images are deleted by Haps immediately after processing, including failures. Temporary results remain private to the requesting account for no more than 10 minutes and are not included in the account export. AI-provider retention is separate.
- Meal photos sent for early analysis and their results expire in Haps five minutes after upload and are removed by cleanup. Haps also attempts earlier removal when the camera closes, the app leaves the foreground or the image changes. Limited records needed to keep photo deletions effective can remain for up to 30 days. Unlogged chosen photos and scan evidence expire thirty days after capture. Logged photos, scan evidence and private review context expire at the end of the thirtieth calendar day including the meal’s original diary date, in its original timezone. A future diary date can therefore keep evidence longer than thirty days after capture. Reopening or correcting the meal never resets this deadline. You can delete retained photos and review context earlier without deleting the logged diary foods. Diary foods and pending saves remain available after evidence expires. OpenAI retention is separate from Haps deletion. Full photo metadata follows the same expiry and deletion rules as its scan. Separately confirmed training contributions remain indefinitely after the original scan expires or is deleted; contact support about contributed data.
- Nutrition-label images, recognised text, extracted values, verification results and associated processing records are removed after 30 days or earlier on account purge. Product-front photos are no longer collected. A published product can retain verification information without a contributor link. OpenAI retention is independent of Haps deletion. Retained account-owned processing records are included in your CSV export. A private contributed product is deleted on account purge; published catalogue records can remain after their contributor link is removed.
- Conversation ratings remain linked to your account until purge and are included in your private export. Confirmed conversation reports are available only to you and authorised reviewers and expire within 72 hours, or sooner if the related scan expires. Changing the rating, deleting the scan, account deactivation or expiry prevents further access. Reports are included in your export while retained and deleted on account purge. Downloaded reviewer copies cannot be recalled remotely and must be erased by the report expiry or a verified earlier deletion request. Feedback waiting to be sent stays on your phone. These extra chat and note copies are removed after delivery, on signout or after expiry. AI-provider retention is separate from Haps deletion.
- Account-linked food-correction proposals and retained research are included in your private export and deleted on account purge, along with private saved foods. Shared source-backed product revisions may remain as public catalogue history after their link to the account-owned review has been removed. Personal corrections remain private.
- A verified deletion request deactivates your account and revokes access immediately. You may recover the account for 30 days. After that, live account data is purged and encrypted rolling backups expire within a further 30 days. Restoring a backup does not cancel your deletion request.
- Limited deletion, privacy-request, legal, security and dispute records may remain as needed to keep deletions effective, demonstrate compliance, meet legal duties or establish or defend claims. They are not used to reconstruct your deleted calorie ledger.
- A launch-reminder address that is never confirmed is deleted 30 days after you submit it. A confirmed address is deleted 30 days after the launch email is sent, or immediately when you opt out, which keeps only a hashed record so the address is not added again by mistake. Deleting your Haps account also removes a launch-reminder entry for the same address.
- The selected country code and Haps catalogue are cached in encrypted device storage for offline use until refreshed, replaced, or cleared at sign-out.
11. Data on your device
Haps keeps encrypted account data on your device so core logging works offline and pending changes can be sent when you reconnect. This includes your ledger, selected country and food catalogue, connection information, health records, and any catalogue evidence or feedback awaiting delivery. Extra Google Health and Apple Health activity details stay on the device and are excluded from the server-generated account export; Health Connect does not read or store these extra details. Device-stored credentials and encryption keys use the operating system’s secure storage. On iPhone, Haps excludes its local account, ledger and health data from backups. Secure sign-in credentials may still transfer through an encrypted device backup, subject to your settings, but local records and pending changes do not. Sign in to recover synchronised account data; unsynchronised local changes cannot be recovered from Haps. Expired or revoked sessions require sign-in. Android can transfer a separate encrypted sign-in credential through the device-transfer or cloud-backup choice you make during setup. This feature does not copy your local ledger or its encryption key.
Signing out through Haps clears the app’s locally stored account records and pending changes. Device-level backups, screenshots, notification history, or exports you save outside Haps are controlled by your operating system and your own storage choices.
12. Your data-protection rights
Depending on the circumstances, you may request information and access, correction, deletion, restriction, objection, and data portability, and you may withdraw consent at any time. You may also complain to the Danish Data Protection Agency. These rights can be limited where applicable law allows.
Use the public export and deletion journeys or contact stig@rexdigital.group, including to request correction or removal of a packaged-food contribution or its retained private image. We verify control of the account email before acting and do not reveal whether an account exists before verification. Account exports contain CSV files in a ZIP download that you can open with common spreadsheet software.
13. Security
Haps restricts access to personal data and uses encrypted connections, encrypted device storage, protected account access and backups. Private export links expire and can be used once. Access is revoked immediately when deletion begins.
No technical or organisational measure makes a service completely secure. Protect your email and devices, install trusted updates, revoke sessions you do not recognise, and report suspected misuse to stig@rexdigital.group.
14. Adults only and automated decisions
Haps is intended only for people aged 18 or older and is not directed to children. We record an 18+ confirmation rather than a date of birth. Contact us if you believe a person under 18 has created an account.
Haps does not make decisions producing legal or similarly significant effects solely by automated processing. Daily target comparisons, recent-food ordering, sync conflict detection, and notification schedules are operational or arithmetic features, not personalised health decisions.
15. Changes to this policy
The version and effective date appear above. We will update this policy when Haps changes what it collects, why it processes data, its providers, retention, or user choices. Material changes will be highlighted in the service, and renewed consent will be requested if an optional consent purpose changes.