remakan is a private food journal. This privacy notice (our privacy policy) says what personal data we keep, why, who else sees it, what you can choose, and how to delete it. This notice explains our practice. It does not by itself give consent for all processing: where we need your consent, we ask for it separately.
What we keep
Your account. You sign in with Apple or Google, or with HUAWEI ID in the app from Huawei AppGallery. From that provider we receive and keep the account ID, your email address, and your name if the provider shares it. You can also enter or change your account name in the app. We keep that name with your account, and we use it in service emails, which Bento sends (see below). With Apple, the email address can be a private relay address. HUAWEI ID sign-in needs a verified email address that you allow remakan to receive. If you later sign in with Apple or Google, it opens the same account when that provider manages your email address (a Gmail address with Google, an iCloud or private relay address with Apple), and we email you that it was added. If you sign in with HUAWEI ID and its email address belongs to a remakan account without HUAWEI ID, we email a six-digit code to that address. The right code adds HUAWEI ID to that account, and we email you that it was added. Until then we keep the HUAWEI ID account ID and the code, which is stored only in a form that cannot be read back. For other addresses, use the method that you signed up with. For Apple sign-in we also keep an encrypted Apple token, so that we can check that you have not removed remakan from your Apple account. If you add a profile photo, we keep it with your account. We also keep your answer to the food suggestions question and the time of that answer. For each device that is signed in, we keep a session with the device type (iOS or Android) and the time it was last used.
Your journal. The foods you save, with their names, ratings, notes, photos, and dates. The places you save, with an optional photo, with their names, your ratings, labels, notes, and the other details you set, such as "want to visit". If you link a place to Google, we keep its Google place ID.
Tags and groups. Food tags, dish families, collections, and monthly and yearly recaps that the service makes from your journal, and the time zone that you choose for recaps. Before your first recap, the app suggests your device's time zone, and we save the zone that you confirm. If you allow food suggestions, we also receive tag and dish family suggestions from TypeSafe AI, as described below.
Your photos, including your profile photo, if you add them. The app makes them smaller before upload, and we store the file that the app uploads. A photo file can contain information from your camera, such as the time and the location where it was taken. Before we store the file, we remove the location and the extra metadata blocks that can contain it. The time and the camera details stay in the file. Other remakan users cannot see your photos. Our hosting and storage providers store them for us, and we open them only to run the service, to answer your requests, or when the law requires it.
Service logs. Our hosting service records requests, with network addresses, device software details, response status, and timing. Application logs can include account IDs and error details. This information is created when you use the service. We use it to protect the service and to find faults. We do not use it for advertising.
Your requests to us. If you email us, we receive your email address, your message, and any information that you give us to answer the request or to check that the account is yours. Emails to our support address pass through Cloudflare Email Routing and are stored in Google Gmail.
Why we use it
We use this data to sign you in and protect your account; to keep and sync your journal on your devices; to show your photos, places, tags, collections, and recaps; to run the place searches that you ask for; to send service emails; to answer your requests; to find faults; and to recover the service after a failure. Food names and notes go to TypeSafe AI only if you allow food suggestions.
You do not need to give health, religious, or other sensitive information to use the journal. But a note, a food name, or a photo that you add can contain such information, or information about other people. Add only what you need. If food suggestions are on, personal information in food names and notes also goes to TypeSafe AI.
Required and optional data
"Required" here means needed for the stated function. It does not mean that the law requires you to use remakan or to give the data.
| Data or choice | Required? What happens without it |
|---|---|
| Sign-in provider account ID and email address; the Apple token for Apple sign-in | Required for that sign-in method. Without it, we cannot give you an account with that method. You can use an Apple private relay address. For HUAWEI ID, allow remakan to receive your email address when Huawei asks. |
| Device sessions and technical logs created during use | Needed to provide and protect the service. There is no switch to turn all of it off while you use the service. Contact us if you want to limit it; if required processing must stop, we may not be able to continue the related function or your account. |
| Your account name | Optional. It can come from Apple, Google, or Huawei, or you can enter or change it in the app. We do not ask you for a name as a condition of the journal. |
| Food name and rating | Required only to save a food. Without them, that food cannot be saved. You do not need to save foods to have an account. |
| Place name | Required only to save a place. Without it, that place cannot be saved. |
| Notes, food photos, place photos, profile photo, a link from a food to a place, place ratings, labels, and other place details | Optional. You can use the journal without them; those details are then not shown. |
| A Google Places link and the text that you type in the place search | When you type 2 or more characters in the place search, the text goes to Google to suggest places. Your notes, ratings, and photos do not go to Google. A Google place is optional: you can save a place by its name only. Without a Google link, Google details for that place are not available. |
| Your current location | Optional. Without it, you can still search for places, but the suggestions cannot use your location or show a distance, and "Find places near me" does not work. |
| Permission for food suggestions | Optional. Choose "Don't allow" if you do not want food names and notes to go to TypeSafe AI. The journal still works, and grouping by dish names that we reviewed still runs on our server. We record your answer and its time, also when you decline. |
| The time zone for recaps | Needed only for recaps. Without it, recaps are not shown. |
| Information to check a request for access, correction, or deletion | Give reasonable information so that we can check that the account is yours and find the request. If we cannot check it, we may not be able to show or change data safely. We tell you what else we need. |
Location
When you type a place name of 2 or more characters in the place search, the app sends the text to our server, which sends it to Google to suggest places. The app asks for location permission only when you tap "Find places near me". Then the app sends only your location, to find food places near you. If location access is already on, the app also sends your current location with the text that you type, so that places near you come first and show a distance. While you search with location access on, the app also asks for food places near you. For this, it sends only your location. Then matching places near you come first. Our server sends your location to Google only for these searches. We do not save your location in your account or journal. Our hosting service's request logs can keep it for the log period (see below). You can search for places without allowing location, and you can withdraw location permission in your device settings.
Who else sees your data
Apple, Google, and Huawei sign you in. They handle your sign-in under their own privacy policies. In the app from Huawei AppGallery, HUAWEI ID sign-in runs through Huawei Mobile Services (HMS Core) on your device.
Google Places provides place search, suggestions as you type, nearby food places, place details, ratings, and photos. Our server sends Google the place name that you type, and your location if location access is on. For "Find places near me", it sends only your location. The app loads Google place photos directly from Google, so Google receives your device's network address for those requests. For place search, Google does not receive your email address, your notes, or your photos from us. The Google Privacy Policy applies to Google's handling of data.
TypeSafe AI (typesafe.ai, its Jev model), a service in the United States, suggests food tags and dish families, but only if you turn on food suggestions. The app asks you first, and you can turn them off at any time in My Account. When they are on, our server sends it the name and the note of each food that you save. It does not receive your account name, email address, or photos, but it receives any personal information that you write in a food name or note. Without food suggestions, remakan still groups foods by dish names that we reviewed, on our own server. TypeSafe AI handles the data under its own terms and its privacy policy.
Bento sends our emails, such as the account deletion confirmation. It receives your email address, your name, and the message, and it keeps a record of the emails that it sends under its own retention rules and its privacy policy.
Laravel Cloud hosts the service in Singapore. Photos are stored in Laravel Cloud object storage, which Cloudflare provides. Our website and API are served through Cloudflare, which processes network addresses and request details to protect the service from attacks and can set security cookies for that purpose.
Transfers outside Malaysia. These providers process data outside Malaysia: hosting in Singapore, food suggestions in the United States (only with your permission), and sign-in, Google Places, service email, support email (Cloudflare and Google Gmail), and network protection where those providers run their services. We transfer data to them only to provide the service that you use.
Shared places. If you share a place, anyone with the link can see a public page for it. That page shows the place's name, address, Google rating, and Google photos. It does not show your name, your rating, your notes, or your photos. Its photos load from Google in the visitor's browser. The link stays public after you change the place or unlink it from Google, and search engines can list it. Other remakan users who share the same Google place get the same link. To remove a shared link, email us.
Shared recaps. If you share a recap, the app makes the image on your device and gives it to the app that you choose. We do not upload the image or keep a copy. The image shows place names only if you turn them on. The app that you choose handles the image under its own terms.
No advertising. We do not sell your data, use it for advertising, or track you across other apps. The app has no advertising or analytics SDK.
How long we keep it
| Data | How long we keep it |
|---|---|
| Foods and their photos | Until you delete them or delete your account |
| Places, your account, and your food suggestions answer | Until you delete your account |
| Shared place links | Until you ask us to remove them |
| Your emails to us and our replies | 12 months after we close your request |
| A HUAWEI ID sign-in code and its record | Until it is used, a new code replaces it, or five wrong codes are entered; otherwise we delete it within one day after it expires (10 minutes) |
| An email that we could not send | We try three times within a few minutes, then delete it |
| A background task that stopped after a rare system fault (for example the account deletion email or the request to Apple to revoke access) | Encrypted, until we delete it, within 30 days |
| A photo that you remove | We delete the file when you save the change |
| Sign-in sessions on your devices | They stop working after 30 days or when you sign out, and we delete expired sessions within one more day |
| Service logs | Up to 30 days |
| Our admin record of who looked at an account: the account ID (not the name or the email address), what was viewed, the time, and the IP address of the request | 12 months, also after the account is deleted |
| Database backups (restore history) | 7 days |
These periods are for our service. Records that providers keep, such as Bento's sending records, also follow the provider's rules described above.
Deleting your account
In the app, open My Account and choose Delete account. You lose access at once, and we delete your account, your journal, and your sign-in sessions at once. We delete your photo files at the same time; if our storage fails, we try again every day until they are gone. We send a confirmation to your account's email address. If you cannot use the app, email support@remakan.com from that address; if you cannot, tell us, and we check in another way that the account is yours, for example by asking you to sign in to the app if you can, or for other details of the account. We then delete the account within 30 days. For Apple sign-in, we also ask Apple to revoke remakan's access about 15 minutes later, so that the confirmation email has time to pass Apple's email relay. For HUAWEI ID sign-in, the app asks Huawei on your device to cancel remakan's access to your HUAWEI ID. Shared place links stay, because they are not linked to your account; ask us if you want one removed. Copies in database backups expire after 7 days. Deleting your remakan account does not delete data that Apple, Google, or Huawei keep for your account with them.
Your choices and withdrawing consent
You can limit optional data by not adding notes or photos, not using Google search, not sharing places, and not allowing location or food suggestions.
To withdraw permission for food suggestions, turn off Food suggestions in My Account. When the change is saved, we stop new requests to TypeSafe AI, including waiting work that has not sent its request yet. This does not by itself delete data already sent to TypeSafe AI; contact us about that data. The journal and the dish name matching on our server keep working.
To withdraw location permission, use your device's app permission settings. This stops the use of your location for later searches, but it does not delete earlier logs before their period ends.
You can also withdraw consent or ask us to limit processing by writing to support@remakan.com. Say which account and which processing you mean. If the request concerns processing that an account or a function needs, we explain the effect: we may not be able to continue that account or function. Declining food suggestions alone never ends your account. Withdrawal does not undo processing that happened before it, and it is different from a deletion request.
Access, correction, and other requests
You can ask us to confirm what personal data we process, for access to it or a copy of it (your journal as a JSON file, and your photo files), to correct data that is wrong, or to delete it. Email support@remakan.com. For a correction, say what is wrong and what it should be. We may need to check that the request comes from you or from a person who may act for you; we ask only for reasonable information to do that. We act within the period that the applicable law sets. If we cannot do all of a request, we explain why and what you can do next, as far as the law allows. You can also ask us to send your data to another service; a JSON export to you is not the same as a direct transfer to another service.
You can complain to us, or to the Personal Data Protection Department of Malaysia. Using our support does not take away any of your legal rights.
Age
remakan is for people aged 18 and over, and we do not knowingly keep data about anyone younger. If you think that someone under 18 uses remakan, email us. We check, and if the user is under 18, we delete that account.
Changes
If we change what we collect or who sees it, we will change this page and its date. We will tell you about important changes in the app or by email before they apply. If a change needs new consent, we ask for it before that processing starts; using the app after an update does not by itself give consent for a new optional purpose. The Bahasa Malaysia and English versions describe the same practice.
Contact
For questions, complaints, withdrawing consent, or requests for access, correction, transfer, or deletion: the developer of remakan, an individual based in Malaysia. Email support@remakan.com.