1. Scope and responsibility
“PinoyFoods”, “we”, “us” and “our” refer to the provider of the PinoyFoods Daily service offered through the landing page reached from stratinvcapital.ae/pinoyfoods. The service provider is responsible for the purposes of the personal-data processing it controls in this web subscription flow. The service-support contact published on the page is support@startinvcapital.ae.
e& UAE operates your mobile account and carrier billing. The subscription gateway at cicscloud.in handles PIN and subscription requests. Hosting and network infrastructure support page delivery and processing. Their responsibilities depend on the activities they perform; this policy does not replace a mobile operator’s or independent provider’s own privacy notice.
This notice does not automatically cover a separately installed app, app-store billing, another PinoyFoods offer or all activity on a separate content portal. Read any additional notice displayed when you use those services. No ChatGPT or social-media account is requested by this subscription form.
2. Information handled by the subscription flow
- Mobile number: the UAE number you enter, normalised to a consistent format, so a PIN can be requested and the correct subscription can be identified.
- Verification input: the PIN you submit to confirm control of the number and request activation.
- Session information: a random session identifier, an encrypted temporary mobile number, timestamps, expiry, resend timing, attempt count and processing state.
- Consent record within the session: the time of the confirmation action and the version of the subscription terms presented for that action.
- Abuse-prevention information: protected derived identifiers for the number and network address, request counts and time windows.
- Technical connection information: information necessarily transmitted with a web request, such as an IP address and browser request headers, which hosting or network services may process.
- Language preference: your English or Arabic selection stored in your browser.
- Support correspondence: the contact information, messages, relevant charge details and attachments you choose to send to support.
The landing-page form does not ask for your name, card details, banking login, address, contacts list, photographs, microphone access or precise GPS location. Please do not include unnecessary sensitive information in a support request.
3. Where information comes from
Information comes directly from the form entries and choices you make, automatically from the browser and connection needed to serve your request, and from the subscription gateway’s responses. The gateway may return a result such as PIN sent, invalid PIN, active subscription, insufficient balance, ineligibility or an error.
That status information is used to display the next step or an appropriate message. The landing page does not need to read your SMS inbox: you receive the message on your phone and enter the PIN yourself. An operator or gateway may already hold separate customer, billing and subscription records under its own arrangements.
4. Why information is used
We use information to validate an entered number, request and verify the PIN, keep the request associated with the correct browser session, submit the confirmation action, and show the resulting service status. We also use limited session and security data to prevent rapid repeat requests, repeated PIN guessing, unauthorised cross-site submissions and duplicate processing.
Support information is used to understand your enquiry, locate the relevant service event, investigate an access or billing issue, respond to a privacy request and keep an appropriate record of how the matter was handled. Information may also be needed to meet a legal obligation or establish, exercise or defend a legal claim.
Reading these legal pages does not request a PIN, send your mobile number to the subscription gateway or activate a subscription. Entering information for one requested step does not authorise unrelated uses.
5. Consent and other lawful grounds
Personal data is processed only on a lawful basis permitted by the applicable UAE data-protection rules. Depending on the purpose, this may be your valid consent, steps you request towards a subscription, performance of the subscription arrangement, a legal obligation or another applicable statutory exception.
Where consent is the basis, you may withdraw it for future processing. Withdrawal does not make earlier lawful processing unlawful or remove processing required on another lawful ground. Optional marketing consent must be separate from the information necessary to fulfil your requested subscription. This policy itself is an explanation of processing, not a blanket consent to every possible use.
6. What happens to your number and PIN
When you request a PIN, the server sends your mobile number and the PinoyFoods service identifier to the subscription gateway. When you submit the PIN and confirm, it sends the number, service identifier and PIN for verification. The gateway and operator need this information to perform the requested subscription steps.
The mobile number held in the landing page’s temporary session is encrypted. The browser receives a random session cookie rather than the stored encrypted number. Where the interface shows a session number, it is masked. The PIN is used for the verification request and is not saved in the landing page’s session database.
After a successful verification, the encrypted mobile-number field is cleared from that local session record. This does not erase the operator’s billing records, gateway records or the SMS on your phone. Our application code is designed not to include the full mobile number or PIN in routine application log messages or browser page URLs.
7. Cookies and browser storage
| Item | Purpose and duration | Your choice |
|---|---|---|
| pfd_session cookie | Associates the PIN request with its verification session. Its normal lifetime is 10 minutes; a successful resend refreshes the session period. It is restricted to secure, same-site use in production and is not readable by ordinary page scripts. | Required to complete the PIN flow. Blocking or deleting it may require a new PIN request. |
| pinoyfoods-language local storage | Remembers English or Arabic on that browser. It remains until cleared or replaced. | Change language on the page or clear that site’s browser storage. |
These are the storage items intentionally used by the current subscription-page code. The legal pages do not add an advertising cookie or a tracking script. Hosting or network services can separately use necessary operational measures described in their notices.
Clearing browser storage does not cancel carrier billing, delete an operator record or make you a new subscriber. Use the SMS cancellation method to stop the subscription.
8. Service messages, analytics and advertising
The registered mobile number is used for subscription-related messages described on the landing page, including verification and service-status communications. These operational messages are different from optional promotional campaigns.
The current landing-page implementation does not include third-party advertising pixels or a behavioural analytics SDK. The browser’s language preference is not an advertising profile. We do not sell mobile numbers or PINs collected through this subscription flow.
If a future version introduces optional analytics, advertising or an unrelated marketing purpose, appropriate information and any legally required consent must be provided before that processing starts. Clicking Subscribe is not presented here as consent to all future marketing technologies. An external advertisement or website that sends you to this page may have its own separate privacy practices.
10. Processing locations and international transfers
Hosting, technical support and subscription infrastructure can involve processing outside the United Arab Emirates. This policy does not promise that every copy is stored only in the UAE or assign an unverified location to a provider.
Where a cross-border transfer is subject to UAE law, it must satisfy the applicable transfer conditions and safeguards. Depending on the circumstances, these may include an accepted protection level, contractual safeguards or another legally available transfer condition. You may contact support to request information about the arrangements relevant to your data.
11. Retention and deletion
PIN sessions: the current flow gives a session a 10-minute validity period, refreshed by a successful resend. An expired session can no longer be used to verify. Expired session records are removed during cleanup triggered by subsequent subscription requests, so logical expiry is not a promise of physical deletion at exactly the tenth minute. Successful verification clears the encrypted mobile-number field earlier.
Abuse-prevention records: request counters have short expiry windows, currently up to one hour for PIN-request limits and ten minutes for verification-attempt limits. Expired records are removed by the same request-triggered cleanup. The protected identifiers are pseudonymous, not treated as guaranteed anonymous data.
Browser preferences: the language selection remains on the device until changed or cleared. Cookie expiry follows the session behaviour described above.
Support, legal and separate provider records: correspondence should be retained only as long as necessary for the enquiry, applicable legal obligations or a live dispute. Operator billing, gateway records, infrastructure logs and backups follow the relevant provider’s applicable retention arrangements. The short landing-page session period does not promise deletion from those separate systems. No universal fixed retention period is asserted for them.
12. Security measures and your role
The subscription flow uses encrypted connections, encryption of the temporarily stored number, random session identifiers, restrictions on browser access to session cookies, origin checks and limits on repeated requests and verification attempts. Routine application error messages are designed to avoid exposing submitted numbers or PINs.
No internet system can guarantee absolute security. Keep your device and messages protected, use the intended service page, and avoid sharing an active PIN. Contact support and the operator if you suspect misuse. Security incidents must be assessed and handled with any notifications required by applicable law; this policy does not promise an unverified incident-response deadline.
13. Your privacy rights
Subject to applicable UAE law and its exceptions, you may request information and access, correction of inaccurate data, erasure where available, restriction or stopping of processing, portability where applicable, and review of qualifying automated decisions. You may object to direct marketing and withdraw consent for processing that relies on it. These rights have legal conditions and are not an unconditional right to erase every billing or dispute record.
We should explain any relevant limitation rather than treating a request as automatically rejected. We do not require you to waive privacy rights to read these pages. You may also raise a concern with the competent data-protection authority where the applicable law provides that route.
14. How to make a privacy request
Email support@startinvcapital.ae with the subject “PinoyFoods UAE — privacy request”. State what you want to access, correct, erase or restrict and the approximate date of the relevant interaction. Start with only the information needed to identify the issue; support may need proportionate verification before disclosing or changing an account-related record.
Do not send an active OTP, password, full card number or unnecessary identity-document copy. If someone acts for you, appropriate authority may need to be checked. Requests should be handled within the requirements of applicable law, with an explanation where further information or a lawful restriction affects the response.
If a request concerns data controlled independently by the mobile operator, such as its bill or SIM-account record, contact e& UAE through its official privacy or customer-support channels. If the published service email cannot be reached, the operator can assist with identifying the relevant subscription provider for an operator-billed transaction.
15. Optional information, cancellation and account choices
You can read the landing page and legal pages without submitting a mobile number. If you do not provide the number or PIN needed for the requested subscription step, that step cannot be completed. You may exit before confirmation.
To stop paid renewal, send C PFD to 1111 from the subscribed mobile number. A request to delete information, withdrawal of optional marketing consent, browser-data deletion or an email privacy enquiry does not automatically transmit that cancellation instruction. Equally, cancellation does not require immediate deletion of records that a provider must lawfully retain.
Once you have cancelled, necessary messages to confirm cancellation or resolve an existing complaint may still be sent. They should not be used as a pretext for unrelated marketing.
16. Children and shared mobile accounts
A minor should not authorise a paid mobile subscription without the legally responsible adult or authorised bill payer. The subscription form does not ask for a date of birth and should not be treated as a verified age-checking service.
If you believe a child used your number without authority, contact support and the operator promptly to review the subscription and associated information. Use the SMS cancellation instruction if you also want renewal stopped. Any age-appropriate access requirements of separate content remain relevant.
17. Automated checks and external services
The page automatically checks number and PIN format, session validity, timing, request limits and the subscription gateway’s status response. These checks can prevent a step or display an error. They are operational and security controls; they are not a credit score or a behavioural advertising profile created by this page.
If an automated error prevents legitimate access or you dispute the result, contact support for review. External content, operator apps and linked websites have their own terms and privacy notices. Review those notices before supplying further information; simply mentioning or linking a service does not make all of its processing subject to this policy.
18. Policy updates and further information
This version takes effect on 7 October 2026. Updates should describe actual changes to information collected, purposes, recipients, storage or customer rights. A materially new purpose must have a lawful basis and any required notice or consent before it starts. Publication of a revised policy does not retrospectively authorise an unrelated use.
For commercial details, read the PinoyFoods Terms & Conditions. For questions about this notice, use the privacy-request route above. Relevant official references include the UAE Personal Data Protection legislation. For an unresolved operator-service dispute, the TDRA complaint route is separate from a data-protection request.