TAKEME · Help & information
Understand what you share, how TAKEME uses it, and the choices available to you.
TAKEME is operated by TAKEME TECHNOLOGIES (SSM Registration No. KT0622373-U). Our privacy and support contact is support.takeme@gmail.com.
This Privacy Notice explains how TAKEME collects, uses, discloses, stores and protects personal data in connection with the TAKEME marketplace and related services.
This notice covers account registration and sign-in, profiles, listings and photos, messages, offers, agreed deals, auctions and bids, in-app Updates, Saved and following, discovery, preferences, reports, support, policy acceptance and account-deletion workflows.
TAKEME helps buyers and sellers arrange their exchange directly. Current V1 does not process payment-card details through Stripe, seller payouts or integrated protected checkout, or provide integrated shipping/AWB, Seller Centre, live commerce or short-video commerce. Future services would require a further privacy review before collection starts.
This notice describes the reviewed web service and planned compliance architecture. It does not certify a future native application or introduce native push notification collection or future V2 analytics.
Personal data can identify you directly or remain linked to your account or marketplace activity. The categories below cover information you provide, supported activity records generated by the service and identity information supplied by the sign-in provider you choose.
You provide account information, profile details, listing text/photos and marketplace messages or offers when you use those features. Support emails and reports can contain information you choose to supply.
A profile photo, private address and saved search are optional. Account identity is needed for authenticated features; relevant item details and photos are needed to publish a listing. If you do not supply required information, the relevant feature cannot be completed. You can still browse approved public marketplace content.
Private address lines, postcode, city, state and country are account-only information. Saved meet-up names and general areas remain private until you explicitly select a meet-up snapshot for a listing. Removing a saved place does not automatically change an existing listing snapshot. Do not put a private home address, credentials or unnecessary sensitive details into public text, photos or messages.
Firebase Authentication handles email/password and Google sign-in. Account data includes your authentication/account identifier, email, connected provider identity, account status and relevant creation/sign-in timestamps. Google sign-in may supply a display name and profile photo associated with the identity you choose.
Firebase handles credentials and sign-in sessions. TAKEME does not store your password in marketplace profile documents or messages. Password-reset emails are authentication messages, separate from marketplace alerts. Account deletion or reauthentication does not delete your Google account.
Public browsing does not require an account. Login, refresh and browsing do not count as Privacy or Terms acceptance. Current explicit Terms/Privacy acceptance and 18+ confirmation are required before protected marketplace writes such as Sell, Chat, Offer, Bid, Save, Follow and uploads.
Your public display name, profile photo, membership information, general marketplace district/city and state, and available seller ratings/reviews or reputation may appear to marketplace visitors. A profile or rating is not proof of item authenticity or business registration.
Your account email, private address, private onboarding and policy acceptance records are not part of the public marketplace profile. Public seller projections use permitted marketplace fields; private addresses are not automatically copied to profiles, listings or discovery.
Structured location features use information you enter. They do not request device GPS or infer a precise live location. A public meet-up/general-area snapshot becomes visible only when you explicitly choose it for a listing.
Listings store the title, description, category, condition, price, photos, listing type, seller reference, chosen public location and status. Published listings and photos are public marketplace content; drafts are account-managed content.
Images are processed and stored to display listings and profile photos. Do not include unnecessary personal information in images. This notice does not promise that all uploaded images remove embedded metadata.
Published reviews can include ratings, predefined tags and comments about an eligible buyer or seller role. Private review submissions and deal details use authorised account or participant access. Authentic limited ratings/history may remain after identity minimisation under the deletion rules.
If you save a listing-promotion request, TAKEME stores the seller/listing reference, chosen package/type, example price/duration, request/payment-setup status and timestamps. Checkout, payment and paid activation remain unavailable; saving a request does not buy extra placement or take a payment.
TAKEME processes private participant conversations, plain-text message bodies, sender/participant references, timestamps, listing/deal/offer context, previews and unread counts to provide marketplace communication. These conversations are not public content. The current messenger does not support attachments, typing indicators or read receipts.
Offers/counters store participants, proposed or agreed amounts, status, expiry and supported payment-arrangement labels. Deals record participant confirmations, cancellation/dispute information and review eligibility. These are marketplace agreement records, not payment-card data or a platform payment receipt.
Auctions record starting amounts, increments, timing, bids, bidder references, current/final amounts and results. Public auction presentation can show amounts/results and limited bidder information without private account emails. Required history preserves genuine auction outcomes.
Relevant bounded message or deal context may be reviewed by authorised staff when necessary for a report, safety concern, dispute or support investigation. This does not mean staff routinely read all messages. Another participant can retain their own copies outside TAKEME.
TAKEME stores your Saved listings/auctions, followed sellers, explicitly saved searches and their supported filters/alert preferences. Those relationships and personal preferences are private; a public seller profile can show an aggregate follower count without exposing follower identities.
In-app Updates contain relevant listing/deal references, notification text, creation/read/open times, unread summaries and preferences. Optional supported alert categories can be managed in Settings; essential offer, deal, dispute and auction-win updates remain enabled.
These preferences affect supported in-app alerts. Native push, marketplace email/SMS alerts and daily digests are not active in the current web service. Authentication password-reset emails are separate.
TAKEME records relevant activity/operation identifiers, timestamps, account-linked rate-control counters, upload authorisations and operation outcomes needed for service reliability, safe retries and abuse prevention. Such identifiers can remain linked to an account; they are not automatically anonymous.
Authentication and hosting providers may process network, request and browser information necessary to deliver and secure their services. That provider processing is distinct from TAKEME marketplace records. Current app source does not implement device fingerprinting or a dedicated collection of exact IP addresses, advertising identifiers, device contacts or precise live GPS.
Operational logs should contain only information reasonably needed for security and troubleshooting. Provider/log detail and bounded retention require final review; this notice does not claim every technical record is erased by live account cleanup.
Support communications use the contact email you choose to write to. Reports can contain the reporter, target, reason, details, status and relevant listing, seller or bounded conversation/message context. Deal disputes can contain participant reasons and resolution records.
Authorised personnel may review relevant evidence and private administration notes where necessary for support, safety, fraud prevention, dispute handling or legal compliance. Ordinary unrelated users cannot access restricted reports, support evidence, administrative notes or deletion/security records.
Provide relevant, truthful information without unnecessary sensitive details. A report does not guarantee an outcome, response time, refund or automatic dispute resolution. Case evidence is subject to restricted, bounded retention rather than permanent default storage.
TAKEME stores private, server-authored evidence of explicit acceptance: the accepted Terms and Privacy versions, 18+ confirmation, server-controlled timestamps, web source and supported release context. It also keeps a bounded current eligibility record used to check protected marketplace actions.
Acceptance history is immutable during ordinary acceptance and reacceptance: new consent does not overwrite earlier valid evidence, and retries do not create fabricated consent. Historical records are still personal data subject to the approved account-deletion cleanup; immutable does not mean permanent retention.
Only explicit acceptance creates or updates consent evidence. Login, refresh, status checks or browsing alone never count as acceptance. Earlier valid evidence is preserved with its original timestamps where the reviewed migration applies; missing consent is not invented.
This evidence establishes current eligibility, preserves compliance evidence and supports future reacceptance. It does not include a birth date, identity document, IP address, browser fingerprint, cookies or authentication tokens.
The purposes are tied to the supported marketplace and necessary compliance/operation. This notice does not introduce broad advertising profiling or collection for unavailable features.
Relevant account, marketplace, acceptance and case records may be used to enforce the Terms, establish eligibility, respond to lawful requests, investigate fraud/security concerns and maintain records where applicable law requires it. Use and disclosure should be limited to the legitimate purpose.
exact statutory requirements, marketplace/operator duties, retention and deletion conflicts, breach notification obligations and DPO applicability. This notice does not claim a completed compliance certification or an appointed Data Protection Officer.
The service uses listing/profile content for public display and discovery, participant records for messages/offers/deals, auction data for bid ordering/results, and Saved/following/preferences for the supported account features and alerts.
Records of confirmations, reviews, notifications and operation identifiers support truthful marketplace history, safe retries and service reliability. TAKEME does not fabricate payment, shipment, bid or deal outcomes.
Private data is not made public merely because it is used to operate a feature. Account email, private addresses, inbox, acceptance evidence and personal preference records remain outside ordinary public marketplace projections.
For signed-in users, supported listing/auction views, submitted searches, category/filter actions, saves, bids, messaging actions, recommendation impressions/clicks, Not interested/Undo and completed-deal activity can generate marketplace signals.
Private interest profiles, records of items actually served and click/save attribution help rank relevant items, avoid repeated exposure, honour supported choices and measure marketplace feature activity. Authorised administration can use aggregate measures.
This is activity within TAKEME, not a record of browsing other websites. Private addresses do not drive public discovery projections. The current implementation does not build an external behavioural-advertising profile.
Ownership/participant checks, operation records and bounded rate-control records help detect or prevent repeated abusive messages, offers, bids, reports, listing/draft activity or uploads. Relevant reported content can be considered for a legitimate safety investigation.
Security/fraud evidence is not an indefinite default archive. Any explicit restricted hold requires a documented purpose, restricted access and expiry under the reviewed model. Final legal grounds and retention/deletion reconciliation remain subject to applicable law.
Firebase/Google Cloud provides Authentication, Cloud Firestore, Cloud Storage and Cloud Functions for identity, marketplace records, uploaded photos, authorised operations and scheduled processing. Google is also the sign-in provider where you choose Google authentication; Google-hosted profile photos may be displayed.
The reviewed hosting architecture uses Cloudflare Workers to deliver the website and process web requests. Netlify remains a temporary hosting/rollback provider during migration. Support and privacy enquiries use the published Gmail contact; this is not a claim of an integrated support-ticket platform.
Providers process relevant information to deliver, authenticate, host and protect the service. Their infrastructure, technical logs and backups have handling separate from TAKEME live marketplace cleanup.
final provider disclosure details, actual services active at public launch, processing arrangements and bounded provider/log retention. No unverified processing country or all-services location guarantee is supplied by this notice.
TAKEME does not sell personal data to advertisers. It does not sell personal data as a marketplace service. There is no active external advertising tracker or third-party marketing analytics SDK in the current web implementation.
Data sharing is limited to relevant marketplace visibility, participant communication, service providers and necessary lawful administration, safety or legal purposes. Publishing a listing does not make your account email, private address, inbox, acceptance history or preferences public.
Where applicable and necessary, limited information may be supplied to authorities under law or for lawful fraud/security investigations or relevant legal advice. This notice does not claim routine sharing with insurers, auditors or a corporate buyer where no such current practice is established.
Service providers may process or store data outside Malaysia depending on their infrastructure and service arrangements. A selected Functions region does not establish the location of every service, backup or operational log.
final international-transfer language, applicable conditions/safeguards, actual provider arrangements and processing locations. No country is named without verification and no claim is made that all data stays in Malaysia.
Active account/profile and marketplace data is held while needed for its supported purposes, subject to applicable law and the approved retention model. The deletion-related periods below are not a global lifetime for every active account record.
Cleanup removes or minimises personal live data and limits necessary pseudonymised marketplace history and restricted evidence. Pseudonymised records are not necessarily anonymous. An expiry field or pending cleanup is not proof that every physical copy has already disappeared.
Malaysian marketplace record-retention requirements and their reconciliation with existing deletion periods, the exact applicable records/start points, and any necessary statutory retention. This notice does not change backend schedules or silently extend records to a new statutory duration.
You can request account deletion in Settings or through the public account-deletion route after signing in and confirming ownership with the existing authentication provider. A request, pending state or failed attempt is not completed deletion. Production deletion execution remains off pending separate qualification and activation approval.
The implemented cleanup removes or minimises the public profile, private addresses, saved meet-up places, Saved/following/searches, preferences, notifications, personal discovery records and acceptance history. Safe listings/drafts and owned uploads are cleaned up when their stage permits. Necessary live auction context remains until obligations resolve.
Departing authored messages and copied previews are removed/redacted, identity becomes Deleted user, and necessary counterparty history is bounded. Reviews about the deleted profile are removed; limited genuine ratings/tags about surviving members can remain with departing identity/free-text minimised. TAKEME does not fabricate or rewrite marketplace outcomes.
Live bid-bearing auctions, unfinished deals, unresolved reports/disputes or uncertain legacy obligations can keep a request pending. Fraud/security investigations, legal holds or statutory duties may also lawfully delay or limit deletion, subject to reconciliation; this is not a claim that every such hold is already an automatic blocker.
Final success is shown only after required cleanup and Firebase Auth deletion succeed. Some data can be removed promptly and some retained or pseudonymised temporarily. Backups, logs and other users' copies may not disappear immediately; no immediate all-data erasure is promised.
Relevant report/dispute or fraud/security evidence can require restricted handling while a valid case or obligation remains. Explicit security/fraud holds require a documented purpose and expiry. Open report/dispute evidence can await valid resolution before its bounded closure-based expiry is set. A generic claim of statutory retention does not automatically resolve the necessary legal scope.
Protected backups and operational logs are outside synchronous live deletion. They should retain only what is reasonably necessary for security, troubleshooting, fraud prevention, disaster recovery and legal duties, for limited documented periods.
The approved restoration procedure requires deletion state/cleanup to be reapplied before restored deleted-user data becomes active again. Backups must not revive a deleted account except where technically necessary for disaster recovery or required by lawful security procedures. These are operational requirements, not a claim that every recovery path is already automated or every backup has expired.
legal holds, disputes, backups/log periods, restoration controls and statutory retention/deletion conflicts. This notice does not create an indefinite evidence store.
TAKEME uses technical and organisational safeguards designed to protect data, including authenticated and authorised access and restricted handling of private records. No online service can guarantee absolute security.
Keep credentials and verification codes private, use accounts you own and avoid unnecessary personal data in public content or Chat. Contact TAKEME if you suspect an account or privacy problem.
applicable breach notification obligations, incident responsibilities and DPO applicability. No final statutory response deadline, automatic breach notification system or absolute-security promise is approved by this notice.
Where applicable under Malaysian law, you may request access to or correction of personal data, withdraw consent where relevant, seek limits on processing provided by law, raise a privacy complaint or request account deletion subject to lawful obligations and retention limits.
Contact support.takeme@gmail.com with your request. A reasonable ownership/identity check may be needed before private data is disclosed or changed. Do not send passwords or verification codes. You can also use supported profile, preferences and deletion controls.
Withdrawing consent or declining current acceptance can affect protected features. Public browsing does not itself create consent. A privacy enquiry or withdrawal request does not promise automatic erasure of records required for a lawful purpose or by law.
final statutory-rights wording, applicable exceptions, request process and complaint avenues. This notice does not automatically promise GDPR-style rights, universal portability or an invented response deadline.
TAKEME V1 requires account users to be at least 18 years old (18+). Users below 18 should not create an account or use protected marketplace features. No child-account functionality is provided.
Signup requires an explicit 18+ confirmation. TAKEME does not currently collect a date of birth or independently verify age through identity documents or biometrics. Do not misrepresent your age or submit unnecessary information about children.
Firebase Authentication can retain sign-in state in browser storage where supported so the account session can persist. The SDK may use browser/session/cache mechanisms necessary to operate authentication. Signing out affects the supported session flow; provider and browser copies follow their handling.
The current web source does not enable a persistent Firestore offline cache, Firebase Analytics, marketing pixels or a third-party advertising tracker. Necessary provider delivery/authentication mechanisms are distinct from TAKEME's recorded marketplace activity. This notice does not introduce marketing cookies or cross-website tracking.
Supported marketplace activity is used for discovery and feature measurement as described above. final provider/browser-storage disclosure and any required choices at public launch. Any future analytics/cookie collection needs a new review before activation.
Privacy version 1.0 uses the central V1 policy source. The effective and last updated dates are 2026-10-12 and 2026-10-12, respectively.
Material changes should have a clear version, date and appropriate notice or consent as required by applicable law. New users must explicitly accept the current Privacy and Terms versions and confirm 18+ before protected writes; existing users with outdated acceptance may browse public content but must reaccept before protected actions.
Login and refresh never count as Privacy acceptance. Reacceptance preserves earlier evidence and supported profile/welcome state. Returning to an intended context does not automatically execute marketplace actions such as sending a message, bidding, offering, Save, Follow or publishing.
A Bahasa Melayu version of this Privacy Notice is also available. New payments, shipping, push, native SDKs or other new data practices require further disclosure review.
TAKEME TECHNOLOGIES. SSM Registration No. KT0622373-U. Privacy and support: support.takeme@gmail.com.
publishable address and the unresolved provider, transfer, statutory-rights and retention decisions described above.