Privacy Policy
How Sweet Elegance handles information when you use this website. Last updated: November 2, 2026.
Last updated: November 2, 2026
1. Introduction
This Privacy Policy explains how the Sweet Elegance website handles information. Sweet Elegance is the patisserie at 637 Veerasamy Rd, #01-121, Singapore 200637.
In this policy, "the site", "we" and "us" mean the operator of this Sweet Elegance website, the patisserie published at 637 Veerasamy Rd, #01-121, Singapore 200637. You can call +65 9323 9161 or email [email protected]. A separate registered company name and a company registration number have not been published. This policy does not invent them. Privacy requests can use the postal address, phone number and email address above.
The policy applies to the pages of this website only. It does not apply to websites we link to, including the sites of font or browser providers.
2. Information we may collect
The site is built to work without asking you to create an account. The information that can arise from a visit falls into three groups: information you type into a form, information stored only in your own browser, and technical information that a web host or a font service may process when your browser loads a page.
We do not ask for payment card numbers, government identity numbers, precise location, health information or account passwords. Please do not include those details in any message you prepare on the site.
3. Information provided by visitors
If you choose to use a contact form, you may type a name, an email address, a subject, an inquiry type and a message. Those fields exist so a question about the website or its dessert writing can be described clearly. Providing them is voluntary. You can browse every public page without filling in a form.
The site does not offer comments, reviews, user profiles or a newsletter signup. There is no separate account information to provide.
4. Contact form information
The contact forms on the home page and the contact page do not post your details to a Sweet Elegance web server. When you submit, the browser stops the normal submission and opens a draft in your own email application. The draft is addressed to [email protected]. The subject line includes the inquiry type you chose. The body contains the fields you filled in.
The message reaches Sweet Elegance only if you send that draft. If you close the draft without sending it, we do not receive the name, email address or message. A copy may remain visible on the page until you leave it. That on-page copy is not stored by us.
When you do send the email, your email provider carries it, and the mailbox [email protected] receives it. From that point we hold the message as ordinary email correspondence. Your provider's terms apply to the sending. Our use of the message is described in this policy.
5. General inquiry information
Inquiry types in the form are general categories such as a question about dessert writing, cake inspiration, website feedback or privacy.
An email you actually send is read so we can understand the question and reply. We do not add that address to a marketing list. There is no newsletter signup on this website, and we do not sell inquiry details.
6. Technical information
When a browser requests a page, the computer that hosts the website may record standard server logs. Those logs can include an IP address, the date and time, the page requested, a referring address and the browser type. This is a common feature of web hosting. The site operator has not named a hosting company on these pages, and this policy does not invent one.
Logs of that kind, where they exist, are used to keep a site available and to investigate abuse or faults. We do not use them to identify you for advertising, and the site does not include an analytics product that would turn those logs into a visitor profile.
The site loads typefaces from Google Fonts. To do that, your browser contacts Google servers (fonts.googleapis.com and fonts.gstatic.com). Google receives the technical data needed to deliver the font files, which can include your IP address. Google's own privacy policy describes that processing. You can block third-party font requests in your browser. The pages will still display, using a fallback typeface.
7. Cookies and similar technologies
The Sweet Elegance pages do not set advertising cookies, analytics cookies or social-media cookies. We have not installed Google Analytics, a Meta pixel or a similar tracking tool, and this policy should not be read as if those tools were present.
The site does use your browser's local storage for two limited purposes:
| Key | Purpose | When it is written |
|---|---|---|
| cookie-ok | Remembers that you closed the storage notice | When you press "OK, close notice" |
| se-checklist-v1 | Remembers reading-list ticks on the gallery and sweet creations pages | Only if you tick or reset a checklist |
That information stays on your device. The site code does not send it to a Sweet Elegance server. You can remove it in your browser settings, and you can clear checklist ticks with the reset button on the page. More detail is in the Cookie Policy.
8. How information is used
Information is used only for the limited purposes that match how the site actually works:
- To display pages, typefaces and images you request.
- To remember, on your device, that you closed the storage notice.
- To remember, on your device, which reading-list items you ticked.
- To keep the website secure and available, including through ordinary host logs where a host keeps them.
- To read and answer email, calls and letters you choose to send to the published contact details.
We do not use information for automated decisions that produce legal effects, for selling personal data, or for building advertising audiences. Dessert pages do not require an account, so there is no profile of dessert preferences stored by us.
9. Communication with visitors
You can write to [email protected], call +65 9323 9161, or post a letter to 637 Veerasamy Rd, #01-121, Singapore 200637. The website form starts that email when you send the draft it opens. We read messages in order to answer the question or correct a page.
We do not add correspondents to a promotional list. No newsletter exists on this site. If you want us to stop emailing you about a thread you started, reply and say so, or write to the same address with that request. We may still keep a short record of the request itself.
10. Website operation
Personal information is not required to operate the public pages. Navigation, galleries, filters and expandable notes run in your browser. The dessert collection search compares your search text with the cards on the page. That search is not sent to a server as a query log by the site's own scripts.
Checklist ticks and the storage notice are the only site features that intentionally write to local storage. Closing the notice is optional in the sense that the pages remain readable if you do not press the button. The notice will appear again on later visits until it is closed or until storage is blocked.
11. Data security
Because the forms do not transmit inquiries to us, the main personal data risk on the form is what remains visible on your screen and in your own email application if you later copy the text elsewhere. Do not leave a prepared message open on a shared computer.
No method of internet transmission or electronic storage is perfectly secure. Where a hosting provider stores server logs, that provider's security measures apply to those logs. We do not claim a certification, a specific security product or a formal security audit that has not been stated by the owner.
12. Data sharing
We do not sell, rent or trade personal information. An inquiry reaches us only if you send the email draft, call, or write to the published address. We do not pass those messages to advertisers or data brokers.
Technical data can be processed by the parties that actually deliver the site: a hosting provider serving the files, and Google, when your browser requests fonts. We would also disclose information if a binding legal duty required it, or if we needed a professional adviser to handle a privacy request under a duty of confidentiality. A company registration number is not printed in this policy because it has not been supplied for publication.
13. Third-party service providers
The third-party service the pages actively call is Google Fonts, as described above. Browser vendors and, where relevant, a hosting provider may also process technical data as part of ordinary internet delivery.
We do not use a payment processor, a shopping cart, an advertising network or an analytics vendor on this website. If one were added, this policy and the cookie policy would need to name it before it went live. They are not named here because they are not in use.
14. Data retention
Local storage entries remain until you delete them, reset a checklist, or clear site data in your browser. We cannot set an expiry for those entries from a server, because they are not on our server.
Email that arrives at [email protected] is kept for as long as we need it to answer you and to keep a fair record of what was asked and what was replied. We do not keep those messages for advertising. When the exchange is finished and we have no continuing reason to hold it, we delete it or archive it only where a legal duty requires a record. This policy does not invent a fixed number of months, because no such period has been set beyond that purpose limit.
Server log retention, if logs exist, is set by the hosting arrangement. That period has not been published on this site.
15. User rights and choices
Depending on where you live, privacy law may give you rights to access personal data, correct it, delete it, restrict or object to certain uses, or receive a copy in a portable form. Those rights apply to personal data a controller actually holds.
For the checklist and the storage notice, you can act without us: use the reset button, close or ignore the notice, or delete site data in your browser. We cannot look up those entries, because we never receive them.
If you sent an email to [email protected], you can ask us to access, correct or delete the personal data in that correspondence, or to tell you how we have used it. Write to the same address or send a letter to the Veerasamy Road address, and put "Privacy request" in the subject or on the envelope. We will need enough detail to find the message, such as the email address you used and an approximate date. We may ask you to confirm that you are the person the message is about before we disclose it.
Sweet Elegance is published from Singapore. The Personal Data Protection Act 2012 (PDPA) is the main privacy law we look to for personal data handled in connection with this website. Under the PDPA, an individual may ask an organisation for access to personal data it holds about them and for correction of that data, subject to the exceptions the Act allows. A separately named data protection officer and a company registration number have not been published. Use [email protected] and the postal address for privacy requests. We have not appointed an EU or UK representative on this website.
You may also raise a concern with the Personal Data Protection Commission of Singapore (pdpc.gov.sg) if you believe the handling of your personal data has not met the PDPA. If you live elsewhere, you may have a right to contact the authority in your own country. This policy does not remove those rights.
16. External links
Some pages link to outside resources, such as Google's privacy information or a browser maker's help page about site data. If you follow those links, the other site's policy applies. Sweet Elegance is not responsible for how those sites handle information.
Viewing the dessert photographs does not sign you in to another service. They are not loaded through a social network plugin.
17. Children's privacy
The website is a general-interest explanation of cakes and pastries. It is not directed at children, and it does not knowingly collect personal information from children. The forms should not be used to submit a child's information. If you believe a child has sent personal information to a future mailbox for this site, ask us to delete it once a working contact method exists.
18. Changes to this policy
We may update this policy when the site changes, for example if an email address is connected to the form, if a host is named, or if a new tool is added. The date at the top will change when we do. The revised policy applies to the site from the date it is posted, unless a later date is stated. Continued use of the site after an update is the way most visitors will see the new text. We do not currently have a list of subscribers to notify by email.
Business identity
Sweet Elegance is the name published on this website for the patisserie at 637 Veerasamy Rd, #01-121, Singapore 200637. The telephone number is +65 9323 9161. The email address is [email protected]. These are the details a visitor, an advertising reviewer or a person making a privacy request can use without guessing.
A company registration number, a tax number and a data protection officer's personal name have not been supplied for this page. They are omitted rather than replaced with samples. If you need to address a formal letter, use "Sweet Elegance" at the postal address above and the email address for a faster reply. Opening hours are not part of this identity section because they have not been published.
The same details appear on the contact page and in the footer. If you ever see a different phone number, email address or street address on this website, treat the contact page as the source to follow and tell us about the mismatch. Consistency of contact details is part of being clear about who operates the site.
Advertising and this website
This website does not set advertising cookies, does not use a remarketing pixel and does not build audiences for ads. If Sweet Elegance is advertised, the advertisement should describe the same business a visitor finds here: a patisserie website with dessert writing and the contact details in this policy. The landing pages do not add a checkout, a price or a limited-time offer that the articles themselves refuse to show.
Reaching the site from an advertisement does not change this policy. We still receive personal data only in the ways already described: email you choose to send, a call you choose to make, a letter you choose to post, local storage that stays on your device, and technical data involved in loading pages and fonts. We do not receive a special advertising profile from the click itself through any tool installed on these pages.
We do not ask advertising partners to match your visit to a list of email addresses. We do not sell visitor data to fund the site. Dessert pages can be read without identifying yourself. Identifying yourself is necessary only if you want a reply.
Visitors outside Singapore
The website can be opened from outside Singapore. The premises and the mailbox are in Singapore, and we handle personal data in that context under the PDPA as described above. Your own country may give you additional rights. You may contact us using the published email address or postal address to exercise a right you believe you have, and you may also contact a regulator where you live.
Google Fonts are requested from Google's servers when a page loads. That request can involve a transfer of technical data, such as an IP address, to Google. It happens because the typefaces are part of the page design, not because we are profiling visitors. You can block third-party font requests. The text remains available in a fallback typeface. We do not use that font request to identify you for marketing.
Email you send may pass through providers outside your country and outside Singapore before it reaches [email protected]. That is how email ordinarily travels. Do not use email for information you are unwilling to see handled by an email provider. In particular, do not email payment card data. The website has no payment function that would justify it.
Information you should not send
Please do not send passwords, payment card numbers, bank details, identity-document images, or information about a person's health. Please do not send someone else's personal data unless you have a proper reason and, where the law requires it, their permission. The forms and the mailbox are for questions about the website, dessert writing, privacy, and general inquiries.
Please do not send a child's information. The site is a general explanation of cakes and pastries. It is not directed at children, and we do not knowingly collect personal data from children. If you believe a child's information has been emailed to us, write to [email protected] and ask us to delete it.
Local checklist ticks and the storage-notice flag are not a profile of a child or an adult. They never leave the browser as a submission to us. Clearing site data removes them without a request to the shop.
When you email [email protected], the personal data in that message is typically your name, your email address, and whatever you chose to write. We use it to reply, to correct the site if you reported an error, and to keep a fair record of the exchange. We do not use it to build a marketing audience, to score you, or to decide whether you may read the public pages. Reading the public pages does not require an account, and we do not create one for you in the background.
If we need to refuse a request, we will say so in ordinary language. A request to see or correct personal data we actually hold is handled as a privacy request under the PDPA, subject to the Act's exceptions. We may take a reasonable time to locate the email and to confirm we are writing to the right person.
Host logs, where the hosting arrangement creates them, are a separate category from the mailbox. They can include an IP address, a time and a page address. We do not use them to identify you for advertising, and we have not installed an analytics product that would turn them into a visitor history. How long a host keeps such logs is set by that host. This policy does not invent a number of days for a retention period the host has not stated to us for publication.
How a message is handled from the first word to the reply
Most personal data this website ever holds arrives because a person decided to write, call or post a letter. The website does not create an account when you read a page. It does not ask you to register to see the gallery or the cake notes. The moment personal data begins, for our purposes, is the moment you send something to [email protected], speak to us on +65 9323 9161, or address a letter to 637 Veerasamy Rd, #01-121, Singapore 200637.
An email typically contains your address, a subject, and a body. If you used the form, the body also contains the name you typed, the inquiry type you chose, and your message. We read that material in order to understand what you want. We reply to the address you gave, unless you asked us to use a different one. We do not add the address to a promotional list. We do not sell it. We do not use it to build a profile of which dessert pages you opened, because the pages do not report that history to us.
After the reply, the thread remains in the mailbox for as long as we need it. Need includes answering a follow-up, checking what we already said, and showing what happened if you later ask for access. When the thread is finished and there is no continuing reason to keep it, we delete it or reduce it. We do not publish a fixed number of months, because the right period depends on whether the conversation is truly over. A privacy request about the message itself is a reason to keep a short record of the request and the outcome.
Telephone calls are different only in form. We may note a name, a number and the substance of the question so a reply can be made. Those notes are treated like correspondence. Letters are kept as paper or as a scan, with the same purpose limit. Please do not send payment card numbers or copies of identity documents by any of these routes. We do not need them to answer a question about the website or the patisserie, and receiving them creates a risk you did not need to take.
What stays on your device
Two pieces of browser storage are described in the cookie policy and repeated here because they are the only ones the site writes on purpose. The key cookie-ok remembers that you closed the notice. The key se-checklist-v1 remembers checklist ticks on the gallery and on sweet creations, and only if you use those lists. Both remain in your browser. Our scripts do not transmit them. Clearing site data deletes them. Ignoring the notice means cookie-ok is never written, and the notice can appear again.
Search boxes on the dessert collection filter cards that are already on the page. The words you type are not sent to Sweet Elegance as a search log. Expandable notes, filters and the mobile menu run locally. The inquiry form does not save your draft into local storage. It opens your email program. If you abandon the draft, we never see it.
Fonts, logs and other technical data
Pages request typefaces from Google Fonts so headings and body text match the design. Your browser contacts Google to fetch those files. Google may process an IP address and related technical data for that delivery. Their policy describes that processing. You may block third-party fonts. The words remain readable in a fallback face. We do not use the font request as a marketing tool.
A host that serves the files may keep standard logs: time, page, browser type, referring address, IP address. Those logs, where they exist, are for keeping the site available and for investigating faults or abuse. We have not installed an analytics product that turns logs into a visitor profile, and we do not use them to decide what dessert page to show you next. How long a host retains logs is set by the host. We do not invent a number of days for a period that has not been stated for publication.
Access, correction and other requests in practice
If you want to know what personal data we hold about you, write to [email protected] or post to the Veerasamy Road address with the words "Privacy request" easy to see. Tell us the email address or phone number you used, and roughly when you wrote or called. We will look for correspondence that matches. We may ask a simple question to confirm we are writing to the right person before we disclose anything. Access covers the personal data in the messages we hold, not a tour of pages you merely read, because we do not keep that tour.
If something we hold is wrong, ask for a correction and say what the accurate version is. If you want deletion, ask for it and we will delete what we can, keeping only what we still need for a legal reason or for a record of the deletion request itself. You may also tell us to stop using your data for a purpose you previously accepted. Because we do not run a mailing list, the usual meaning of that request is "do not write to me again except to confirm this." We will follow that.
The Personal Data Protection Act 2012 is the Singapore law we look to. It allows exceptions, for example where disclosure would reveal another person's data or where a legal hold applies. If we rely on an exception we will say so plainly. You may also contact the Personal Data Protection Commission if you believe your data has been handled improperly. Contacting the Commission does not require you to stop talking to us. A named data protection officer and a company registration number are not printed here because they have not been supplied for publication. The email address and the postal address are the working route.
Children, other people, and people writing from abroad
Do not send us a child's personal data. The site is general reading about cakes and pastries. It is not directed at children and it does not ask children to register. If a child's information reaches the mailbox, write and ask us to delete it. Do not send another adult's information unless you have a sound reason and, where the law requires it, their agreement. A question about a page rarely needs anyone's data but your own reply address.
Readers outside Singapore are welcome. The mailbox and the premises are in Singapore, and we handle personal data in that context. Your country may give you additional rights. You can still use [email protected] to raise them. Email may cross borders on its way to us, which is ordinary for email. Do not use it for secrets you are unwilling to trust to an email service.
Purposes, stated one by one
We use personal data to answer you. That is the first purpose and, for most people, the only one. The answer might be a clarification of a page, a note about a visit, or a confirmation that we have deleted an earlier message. We use personal data to keep a record of that answer so a later message does not contradict it. We use technical data, such as ordinary host logs where they exist, to keep the website available and to look into faults or misuse. We use the font request only so the page can display the typefaces in the design.
We do not use personal data to decide whether you may read the site. Reading is open. We do not use it to score you, to advertise to you on other websites, or to sell a list. We do not combine your emails with a history of pages, because we do not have that history. If a purpose is not listed in this policy, we do not treat this policy as permission to invent one. A new purpose would require an update you can read, and, where the PDPA requires consent or a fresh notice, we would not simply assume the old email thread covers it.
Care with the mailbox and the paper
Email is a convenient channel and not a vault. Messages travel through providers. Inboxes can be accessed if a password is weak or reused. We ask you not to send highly sensitive numbers for that reason, and we apply ordinary care on our side: access to the mailbox limited to people who answer for Sweet Elegance, no publication of correspondence, and deletion when the purpose has ended. Paper letters are kept so they are not left in a public place. None of this is a certification or a promise that a breach is impossible. It is a description of the care we take. If we learn that personal data has been exposed in a way the law requires us to tell you about, we will tell you and, where required, the relevant authority.
You can reduce your own risk. Use a unique password on your email account. Do not forward our reply to a crowd if the reply was meant for you. Do not include a child's information or a card number "just in case." The form on the website only assembles a draft. It does not store the draft on our server. The risk begins when the message is sent, which is also the moment we become able to help.
When this policy changes
We change this policy when the site changes in a way that matters to privacy: a new storage key, a new way of receiving messages, a new provider that handles personal data. The date at the top of the page will move. The previous text is replaced by the new text on the page. We do not keep a public archive of old versions unless we say so. If you want the current version explained, write to [email protected] with the heading you find confusing. A good privacy policy is one a reader can finish. If a section has become denser than it needs to be, that is a reason to edit it, and we welcome that kind of note.
The contact path does not change with the prose. Sweet Elegance, 637 Veerasamy Rd, #01-121, Singapore 200637. Phone +65 9323 9161. Email [email protected]. Use "Privacy request" when you want access, correction or deletion, so the message is not folded into a general question about cakes. Include enough detail for us to find the earlier correspondence. We would rather ask one clarifying question than guess and disclose the wrong thread.
Everyday examples
You read three essays and leave. We hold no name for you. You close the storage notice. Your browser holds a flag and we still hold no name. You tick two gallery items. Your browser holds those ticks. You email [email protected] to ask whether the cheesecake page means a baked filling or a chilled one. From that moment we hold your address and your question, and we use them to reply. You write again a week later. We look at the first reply so we do not contradict it. You then ask us to delete the thread. We delete the messages and may keep a brief note that a deletion was requested and done. That sequence is the privacy policy in ordinary clothes.
A different example: you call +65 9323 9161 about a visit. We may write down the number and the question. The note is for the answer, not for a marketing list. You do not become a subscriber. A third example: you never contact us and you only look at photographs. The font request may have reached Google. The pages themselves did not open a file on you. If any of these examples does not match what you experienced, tell us. The policy should match the site, and a mismatch is something we correct.
What we do not collect
We do not collect account passwords, because there are no accounts. We do not collect card numbers, because there is no payment page, and we ask you not to send them anyway. We do not collect precise location from your phone. We do not collect contacts from your address book. We do not collect photographs of you. We do not run a comments section that would publish your words under an article. We do not run a newsletter signup. If a box on the site ever looks like one of those things, it is a mistake and the contact page is how you report it.
We also do not buy lists of dessert customers, and we do not upload our correspondence to an advertising platform so that ads can follow you. The pages can be reached from an advertisement without that machinery. The advertisement, if there is one, should describe the same patisserie and the same address: 637 Veerasamy Rd, #01-121, Singapore 200637. Landing here does not quietly enroll you.
How to read a long policy
Start with the introduction and the business identity so you know who "we" are. Read the section on the contact form so you know a draft is not a delivery until you send it. Read the section on local storage if you use the checklists. Read the PDPA section if you want something corrected or deleted. The rest is detail for the same promises: purpose, care, no sale of data, a real address for requests. You do not have to memorize it. You have to be able to find the promise when you need it, which is why the contents list sits at the top and why the email address is repeated near the end.
Children's privacy, visitors from outside Singapore, and the role of Google Fonts are the sections people skip and later wish they had seen. They are short relative to the whole policy. They say: do not send a child's data, you may still write to us from abroad, and fonts are a third-party request you can block. Together with the mailbox rules, they are the policy a person can actually use.
Retention in practice
A finished conversation about a page can be deleted once we are confident you have the answer and will not need us to repeat it. A conversation about a visit may be kept until the visit has happened and a short time after, so we can answer a follow-up. A privacy request is kept long enough to show what was asked and what was done. We do not keep messages "just in case" for marketing, and we do not measure their value as a list. If you want a shorter life for a particular thread, say so when you write. We can delete sooner than our usual habit when the law allows it.
Local storage is not part of this retention story, because we never receive it. It lives until you delete it. Server logs, if a host keeps them, follow the host's schedule. We describe that limit honestly rather than printing a number we do not control. The mailbox we do control, [email protected], is the place these sentences apply. The postal address, 637 Veerasamy Rd, #01-121, Singapore 200637, is the place a paper request applies. The phone, +65 9323 9161, is the place a spoken request applies. Three routes, one purpose: to answer you and then to let the answer go when it has done its work.
Keeping your own copy
You may keep the emails we send you. They are your record as well as ours. If you delete your copy and later want to know what was said, ask while we still hold the thread. If we have already deleted it, we will say so. We cannot reconstruct a message from memory and present it as the original. A privacy policy that promised perfect recall would be a fiction. This one promises a fair record for as long as the purpose lasts, and a straight answer when the record is gone.
19. Contact regarding privacy
Privacy questions can be sent to [email protected], raised by phone on +65 9323 9161, or posted to Sweet Elegance, 637 Veerasamy Rd, #01-121, Singapore 200637. The contact page can open an email draft if you choose the privacy inquiry type. Send the draft, or the message stays on your device.
Please include the email address or phone number where we should reply, and enough detail for us to find the information you mean. Do not send identity-document scans or payment card numbers. A company registration number is not printed on this site. The name, premises, phone and email in this section are the published identity for privacy contact.
Related documents: Terms & Conditions and Cookie Policy.