Privacy policy

Last updated: 11 November 2026

This policy explains what personal data Striker handles, why, who helps us handle it, how long we keep it, and how you can ask us to delete it or exercise your other rights.

Who we are

Striker is a product of Hosho Private Limited (UEN 202511998N) ("Hosho", "we", "us"), 60 Paya Lebar Road, #07-54 Paya Lebar Square, Singapore 409051. Striker answers sales enquiries that businesses receive in Instagram and Facebook Messenger direct messages, in comments on their Instagram and Facebook posts, and in other chat channels, on those businesses' behalf.

• Email: support@hoshoai.com
• Data Protection Officer: Greg Bandak, greg@hoshoai.com. Contact him about anything in this policy, a request about your data, or a complaint.

Two kinds of people, two roles

• Merchants. A merchant is a business that signs up to Striker and connects its Instagram professional account. For merchants' account data (staff names, logins, settings), Hosho decides how the data is used and is the controller.
• Shoppers. A shopper is a person who sends a message to a merchant. Striker reads and answers that message for the merchant, under the merchant's instructions. For shoppers' data, the merchant is responsible for it (the controller, or under Singapore's Personal Data Protection Act 2012, the "organisation") and Hosho handles it on the merchant's behalf (a processor, or under the PDPA, a "data intermediary").

If you're a shopper, the merchant you messaged is your first point of contact. You can also contact us and we'll pass your request to the merchant.

What data we handle

About shoppers

• The ids that Instagram, Facebook (a Page-scoped id) or another platform gives us for you, and your username and display name if the platform shares them.
• The messages you send to the merchant and the replies sent back, with their times.
• If you comment on one of the merchant's Instagram or Facebook posts: the comment's text and time, the post it's on, and the one private message Striker may send you in reply (platforms allow a single private reply per comment, within 7 days). If you reply to that message, the conversation continues like any other direct message.
• Which ad, post or link started the conversation, if the platform tells us.
• Whether you clicked a link Striker sent, and, if you then bought something, the order number, value and currency. To match an order to a conversation we use a hashed (scrambled) copy of an email address or phone number, never the plain value, and we keep it only on an order that matched a conversation.
• Whether you asked not to be messaged again (so we can respect that).
• Notes Striker's systems make about a conversation, such as its topic, whether it was handed to a person, and the reply that was drafted.
• If the merchant saves an answer to a question you asked, the wording of your question, with any email address or phone number masked.

We do not collect your Instagram or Facebook password. If you type a payment card number into a chat, Striker removes it before the message is stored or processed, and asks you to use the merchant's secure checkout instead.

About merchants and their staff

• Business details: name, type of business, website, settings, knowledge base, product list and rules.
• Staff details: name, email address, role, a hashed password, the time of last login, and Slack user ids if the merchant connects Slack.
• Connected accounts: the Instagram account id and username, the id of the person who connected it, and an access token. Access tokens are stored encrypted.
• A record of actions taken in Striker (for example settings changed or conversations opened), for security and accountability.

Why we use it

• To answer enquiries for the merchant. Striker reads a shopper's message and drafts a reply using only the merchant's own facts (its knowledge base, catalogue, availability and rules).
• To remind you once about a link. If Striker sent you a link to buy or book and you haven't clicked it or replied, it may send you one reminder in the same chat, within 24 hours of your last message. Never more than one per conversation, and never if you asked not to be messaged.
• To hand over to a person. When a conversation needs a human (for example a complaint, a large booking, or when you ask for a person), Striker passes it to the merchant's team, in Striker's inbox or the merchant's own Slack workspace. If the merchant has Meta's Human Agent feature, the team may reply for up to 7 days after the shopper's last message; otherwise replies are limited to Meta's standard messaging window.
• To measure results for the merchant. We work out which conversations led to a sale, so the merchant can see what its ads and replies achieved. The merchant may choose to report purchases to Meta through Meta's Conversions API: the order value and currency, with the id Instagram (or Messenger) uses for you in the merchant's messages. Meta's messaging purchase events use that id as it is, not hashed; your email address and phone number are never sent. A small share of shoppers may be left unanswered by Striker (the merchant answers them as usual), to measure whether Striker makes a difference.
• To keep the service safe and working. Security monitoring, preventing abuse, fixing faults, and limiting costs.
• To run our relationship with merchants. Accounts, support and billing.

We use a merchant's conversations only to provide Striker to that merchant. We do not sell personal data, use it to build advertising profiles, or combine different merchants' conversations to train a shared AI model.

On what basis

• Singapore (PDPA). Shoppers' data is collected and used for the purposes above, which a shopper is told about when Striker introduces itself as the merchant's AI assistant, and which a shopper agrees to by messaging the merchant. Merchants decide how their shoppers' data is used and are responsible for having a basis to do so; Hosho uses it only as the merchant instructs. For merchants' and staff data, Hosho relies on consent given when the account is set up, and on the PDPA's exceptions for business improvement and legitimate interests (security, fraud prevention, fixing faults).
• UK and EU (GDPR). For merchants' and staff data, Hosho relies on the contract with the merchant (running the account) and on its legitimate interests (security, preventing abuse, improving the service). For shoppers' data, the merchant chooses the basis (usually its legitimate interest in answering the enquiry a shopper started, or taking steps the shopper asked for before a purchase).

How AI is used

• Replies are drafted by AI models (DeepSeek V4.1 Flash, with GLM-5.3 as a backup), reached through OpenRouter and run by hosting companies in the US and EU. The models' makers (DeepSeek and Zhipu, in China) don't receive any data: the hosts run the models on their own servers. Striker's own code checks every reply against the merchant's facts before it's sent, and decides when to hand over to a person, which links to send and which discounts are allowed.
• Striker tells shoppers that they're talking to the merchant's AI assistant, at the start of a conversation and again after a person has replied. You can ask for a person at any time.
• Striker doesn't make decisions about you that have legal or similarly significant effects. Prices, offers and policies come from the merchant's rules.
• Striker only uses hosts that don't train on the data we send and asks OpenRouter to route only to hosts that keep nothing once the reply is made (zero data retention). Before a message goes to the AI, Striker replaces any email address or phone number in it with a placeholder, and removes payment card numbers, Singapore NRIC/FIN numbers and bank details completely.

Who helps us (processors)

We use these service providers to run Striker. Each only gets the data it needs for its job.

• Render: hosts the Striker application. Region: Singapore.
• Supabase: hosts the database. Region: Singapore.
• OpenRouter (US): routes each AI request to an approved host.
• AI hosting companies (US and EU): run the AI models that read messages and draft replies. Only these may be used: DeepInfra, CoreWeave, Fireworks, Together, DigitalOcean, Parasail, Nebius, Baseten, Crusoe and Modal.
• Meta (Instagram and Facebook Messenger, and later WhatsApp): delivers messages and comments; receives purchase events if the merchant turns that on.
• Slack: if the merchant connects its own Slack workspace, conversations handed to a person are shown there.
• Shopify and booking systems: if the merchant connects them, to check availability and match orders.
• Google: if a merchant's staff sign in with Google (their name and email address only).
• The merchant's own systems: a merchant can have Striker send events about its conversations to tools it chooses (for example a CRM), including message text if it turns that on. Those tools are the merchant's.
• Sentry (if enabled): error reports, with message text and contact details removed.
• Langfuse (EU): a record of how each reply was made, so Hosho can find and fix mistakes. Contact details and payment and ID numbers are masked first, it's kept for 30 days, and it's deleted with the rest of a shopper's data.

This is the full, current list. We'll update this page before adding a new processor that handles personal data.

International transfers

Striker and its database are hosted in Singapore. To draft replies, message text (with contact details masked) goes to AI hosts in the United States and the European Union, and Slack, Sentry, Langfuse (EU), Google and Meta may handle data in their own regions.

When personal data leaves Singapore, the PDPA requires the recipient to protect it to a standard comparable to the PDPA. We rely on our providers' contractual commitments for that (their terms of service and data processing terms), and choose providers whose terms commit them to keeping data secure and not using it for their own purposes. For shoppers in the UK or EU, transfers rely on the providers' standard contractual clauses or an adequacy decision where one applies.

How long we keep data

• Conversations (messages, replies and the notes about them): for the period the merchant chooses after the conversation's last activity: 30, 90, 180 or 365 days (90 for new merchants unless they change it). Then they're deleted automatically.
• Raw messages as received from the platform (kept briefly to fix faults): 30 days, unless the merchant sets a different period.
• Shopper records with no remaining conversations are deleted at the same time as the conversations. If you opted out, we keep that note so we keep respecting it, unless you ask us to delete your data.
• Order records stay with the merchant as its financial record; the link to the conversation is removed when the conversation is deleted, and the contact details kept with the order are removed when your data is deleted.
• Background task records: 14 days after they finish.
• Conversations with someone who may be a child (see Children below): 30 days after the last activity, whatever the merchant's period.
• Slack copies of a conversation handed to a person are deleted when the conversation is deleted.
• Security and audit records (who did what in Striker; no message text): 24 months.
• AI usage and cost records (no message text): 24 months.
• Notices to merchants: 12 months. Reporting events: 30 days.
• Records of how replies were made (Langfuse): 30 days.
• Records of data requests (a code, a scrambled id and what was done, as proof we handled it): 3 years.
• Backups: the database's backups are kept for a short period and then overwritten, so deleted data leaves them within days.
• When a merchant disconnects an Instagram account, it can choose to delete that account's conversations too; when the account is removed from Striker in Instagram's or Facebook's settings, they're always deleted.
• When a merchant leaves Striker, we delete its data, including its conversations and stored access tokens.

Deleting your data and your other rights

Depending on where you live, you may have the right to ask for a copy of your data, to correct it, to delete it, to object to or restrict how it's used, and to receive it in a portable form.

• Ask the merchant. Message the merchant in the same chat. It can find your conversation and send you a copy or delete it straight away.
• Email us at support@hoshoai.com with the merchant's name, roughly when you messaged it, and the words of one message you sent (Instagram often doesn't show us your username). We may ask you to confirm it's you.
• Instagram or Facebook users can also remove Striker from their account's apps and websites settings. Meta then sends us a data deletion request and you get a confirmation code and a status page. Meta's request doesn't always identify your conversations; if the page says "No match found", ask the merchant or email us as above. See how to delete your data.
• Because the merchant controls shoppers' data, we tell the merchant about every request we receive about its shoppers.

Under Singapore's PDPA you can ask what personal data about you is held and how it has been used and disclosed in the past year, and ask for it to be corrected. We'll respond within 30 days; if we need longer, we'll tell you within those 30 days when we will. We may charge a reasonable fee for an access request, and we'll tell you the amount first.

If you're not happy with our answer, contact our Data Protection Officer (above). You can also complain to the Personal Data Protection Commission in Singapore (pdpc.gov.sg), or, if you're in the UK or EU, to your data protection authority (in the UK, the Information Commissioner's Office).

Requests from public authorities

We disclose personal data to a public authority (for example the police or a regulator) only when the law requires it. When we receive a request:

• we check that it's lawful and properly made, with legal advice where needed, and challenge requests that aren't;
• we disclose only the minimum the request lawfully requires;
• for shoppers' data, we tell the merchant concerned, unless the law forbids it;
• where we're allowed to, we tell the person whose data was requested;
• we keep a record of every request and our response.

In the last 12 months we have received no such requests.

If something goes wrong

If personal data is lost or exposed, we tell the merchants affected without undue delay so they can act. Where Hosho is responsible for the data and the breach is serious enough, we notify the Personal Data Protection Commission within 3 calendar days of finding that it must be notified (and, for UK or EU data, the relevant authority within 72 hours), and we tell the people affected.

Security

Each merchant's data is kept separate from other merchants' data by the database itself. Access tokens are encrypted. Connections to our service use HTTPS, and messages from Meta are checked to make sure they really came from Meta. See Security for how to report a vulnerability.

Children

Striker is not meant for children. Instagram requires its users to be at least 13 years old. If a message suggests the sender may be a child, Striker hands the conversation to a person at the merchant. From then on Striker sends them no reminders, doesn't report their purchases to Meta, and doesn't let their words be saved as answers. Those conversations are deleted 30 days after their last activity. We treat anyone under 13 as unable to agree to how their data is used, and if we learn that we hold a child's data in breach of the law, we'll delete it.

Changes to this policy

We'll post any change on this page and update the date at the top. If a change is significant, we'll tell merchants by email before it takes effect.

Contact

Hosho Private Limited (UEN 202511998N), 60 Paya Lebar Road, #07-54 Paya Lebar Square, Singapore 409051.

Questions about this policy or your data: our Data Protection Officer, Greg Bandak, at greg@hoshoai.com, or support@hoshoai.com.