Alyce

A model layer that genuinely ships and a product that stands without it. The intelligence is real rather than decorative: the vendor describes research that reads a recipient's public social profiles and proposes gifts matched to their interests outside work, and that research is confirmed in its own recipient help material rather than only in marketing copy, which is more than most vendors claiming personalisation can show.

Strip it out and what remains is still a complete platform: a curated marketplace, campaign structures with budgets and expiry, recipient choice landing pages, redemption card batches for events, record system integrations and pipeline reporting. That is the established platform pattern this index grades at the middle of the band, where the model improves a working product rather than constituting it. A buyer choosing this over a plainer gifting tool is buying the research layer, so establish what it produces on your own accounts before it decides gift spend.

The containment model is layered, documented and set before anything is sent. Spending authority is bounded in several independent ways described in the vendor's own guidance: an organisation is divided into teams, teams carry their own budgets, each campaign carries a budget that fixes the value of any gift that can be claimed, gifts carry expiry dates, the gifts available are curated to a list the administrator chooses, and who may send at all is a campaign setting rather than an open permission.

Batch prospecting sends let representatives personalise from a small set of defaults rather than choose freely. One human step is preserved at the point of change: when a recipient exchanges a gift the sender must approve the replacement, so a substitution cannot quietly alter what was sent or what it cost. It stops below the top band because nothing published states whether an approval step can be required before a first send, or who may raise a campaign budget once set.

The intelligence is the headline claim and nothing about it is disclosed. The vendor describes itself across its own channels as an artificial intelligence powered platform whose research identifies what a person cares about and recommends what to send them, and no provider, model family, version or approach is named anywhere reached.

Nothing states whether the recommendation is a model, a rules engine or a human curation step, what inputs are weighted, how confidence is judged, or what happens when the inference about a person is simply wrong. This matters more here than on a product that generates text, because the output is an inference about a named individual's personal interests, drawn from their social accounts, that then determines what arrives at their door.

The person profiled has no route to see or correct it. Ask what system produces the recommendation, what it is trained or built on, and how a recipient can have an inference about them corrected or deleted.

Multipliers without a denominator. The vendor's own company profile claims up to twice the named account penetration and five times the pipeline against traditional approaches, and the homepage advertises pipeline growth and return on investment figures, none of them accompanied by a sample size, a period, a comparison group or a stated method. A multiplier against unnamed traditional approaches is a claim about an unspecified baseline.

Against that, a substantial independent review corpus exists on a major software marketplace running to several hundred reviews with a high average, and named customers appear with job titles and employers. The vendor's site blocks automated retrieval at the robots level, so case study pages were not readable on this pass and this grade rests on what was reachable rather than on an established absence of measured evidence. Ask for acceptance rate, cost per accepted gift and influenced pipeline on a named customer, with the period and the control stated.

One recipient side control is shipped and stated plainly, and the compliance question specific to gifting is untouched. The control first: the vendor tells recipients that clicking the unsubscribe link will immediately end all automated contact, which is an unambiguous suppression commitment expressed to the person who benefits from it rather than buried in a customer facing term.

Invitations go out either through the platform or through the customer's own connected mail system, so where the sending obligation sits depends on which route a customer picks and the vendor does not say so. Absent altogether is anything on the regulated recipient problem: transferring an item of value to a public official, a healthcare professional or a procurement officer engages gift acceptance and anti bribery rules that vary by country and sector, and no screening, value threshold or jurisdictional block is described. Ask what recipient eligibility screening the platform can enforce and in which jurisdictions.

Two architectural protections for the recipient, and a clause in the same document that cuts against both. The protections are specific and contractual: a recipient's home address and telephone number are never passed to the customer who sent the gift, so the sender gets a delivery outcome rather than a person's home details, and recipient information is not made available to any customer other than the sender.

Those are real commitments in the operative instrument rather than assurances on a page. Against them, the same policy reserves the right to share personal information about gift recipients with third party advertising networks, exchanges and social media platforms so the vendor can serve its own advertising elsewhere. The people that clause covers did not choose this vendor, were profiled from their social accounts and accepted a gift from someone else.

A route to opt out of tracking based sharing is published under the California statute. Ask whether recipient personal information can be excluded from advertising sharing contractually, for all recipients rather than on request.

No purchased corpus sits behind this product and the vendor says so specifically. The identity data is supplied by the customer rather than bought: the vendor states it uses only the name, email and company details its customers provide, so there is no contact database, no enrichment product and no brokered list underneath the platform, and the goods catalogue is sourced through merchant partner networks the vendor states number in the thousands.

The delivery address, the most sensitive field in the transaction, originates with the recipient at the moment of claiming rather than being acquired anywhere. What holds it below the top band is the interest layer. The vendor builds a profile of a person's interests from their public social accounts, and no licence, provider, or lawful basis for that profiling is stated anywhere reached, which is the one place the provenance chain goes unnamed. Ask on what legal basis interest profiles are built on people who have no relationship with the vendor, and how long they are kept.

Four platforms are read and none of them are the vendor's. The recipient help material names the sources as a professional network, two general social networks and a visual discovery platform, and describes accessing a person's public profiles on them to drive gift selection.

What is not stated anywhere reached is the mechanism: whether access runs through a sanctioned interface, a licensed data provider or direct collection, whether the vendor holds any position on those platforms' terms, and what a customer's exposure is if access is withdrawn. Two of the four are general social networks rather than professional ones, which broadens the question rather than narrowing it, because a person's presence there is not offered in a commercial context.

Elsewhere the posture is ordinary and low risk: integrations to customer record and sales engagement systems run through each product's documented route, and fulfilment is the vendor's own partner network. Ask how profile access is obtained for each named platform and what happens to the personalisation feature if a platform withdraws it.

A tenancy boundary written into the operative document rather than described in marketing. The policy states that recipient information is not made available to the platform for use by others and is not provided to any customer beyond the one who sent that particular gift, which answers the question a pooled recipient dataset always raises: whether one customer's gifting activity becomes an asset the next customer benefits from.

For a platform whose value grows with the number of recipients it has profiled, a contractual refusal to pool is the commitment that matters, and few vendors in this category make it. It sits below the top band on two silences. Nothing addresses whether recipient profiles or acceptance history are used to train or tune the recommendation system, which is a different question from cross customer disclosure and is unanswered. And the acquirer has publicly described building a combined gifting dataset across its brands, with no statement here on whether this platform contributes. Ask for both commitments in writing.

The recipient is told what was done to them, in plain words, which almost nothing else in this index manages. A dedicated recipient help page states that the vendor accesses their public social profiles and names the platforms, explains that only name, email and company details come from the sending customer, gives a direct route for personal information removal, and tells them an unsubscribe link ends all automated contact immediately.

Agency at the gift itself is real rather than nominal: accept, exchange for something else, or send the value to charity, with the address supplied by the recipient. There is no synthetic sender and no ambiguity about which company is behind the gift. It is held below the top band by where the disclosure lives.

It sits on a support subdomain a recipient reaches only by going looking, and nothing indicates the invitation itself tells them their social accounts were read before the gift was chosen. Ask what the recipient sees about profiling at the moment of the invitation.

Named destinations with real depth on the two that are evidenced, and a surface that would not open to a machine. A customer record platform integration is documented to the level of a performance dashboard reporting gift activity against pipeline inside that system, which is deeper than a data push, and a sales engagement integration was announced by the vendor itself as a partnership with built in gifting inside cadences.

Marketing automation and further record system connections are described by independent sources. A status subdomain is published, which is a small but real operational artifact. The limit is retrieval rather than absence: the vendor's site refuses automated access at the robots level, so the integrations listing, any developer documentation and any interface reference could not be read on this pass, and none of that is established either way. Ask for the full integration list, whether a documented interface exists for sends and status callbacks, and whether access is gated.

The company's location is stated and the data's location is not. The vendor tells recipients directly that the company is headquartered in Boston while its people work globally, which establishes the governing jurisdiction for a buyer, and it states that gifts are offered for most countries with an exchange route when an item cannot ship to a particular location, so fulfilment reach is described in outline.

Nothing reached states where data is processed or held: no hosting region, no processing location, no residency election, no subprocessor list and no transfer mechanism for moving recipient personal data across borders, which carries weight here because recipients are profiled and shipped to internationally and because the policy contemplates sharing their information with advertising networks whose own locations are unstated.

The vendor's site blocks automated retrieval, so this reflects what was reachable. Ask for the hosting region, the subprocessor list, and the transfer mechanism for recipient data leaving its country of collection.

The security surface could not be read, and that is a retrieval limitation rather than a finding. The vendor's site refuses automated access at the robots level, so any security page, trust portal or certification claim on the primary domain was unreadable on both passes and nothing about its presence or absence is established here.

What was reachable first hand is thin but not nothing: a published privacy policy setting out disclosure limits and lawful request handling, a cookie statement, and a status subdomain indicating operational reporting exists. A third party vendor risk directory lists a long row of certification badges for this company, and that listing is not treated as evidence, both because directory listings do not evidence capability and because this one is internally unreliable, giving an image hosting address as the terms of service and pointing its privacy policy link at a terms page. Ask for the current examination report, its audit period and the auditor's name, and whether the parent group's certifications name this platform in scope.

Every purchase path is a conversation and the vendor says so itself. The recipient help material states the platform is built for enterprise use and directs anyone whose company wants it to a sales address, which is a first hand statement that the buying route is a sales conversation rather than a page.

Four independent commercial sources agree that no list figure is published at any level and describe a three layer structure of a platform licence, a pre funded balance covering gift cost and shipping, and optional professional services, with amounts said to vary by user count, use case and gifting volume. That structure is a third party account rather than a vendor disclosure, so unlike some vendors at this grade there is no published package description to credit either.

The vendor's site refuses automated retrieval at the robots level, so no pricing page was readable on either pass and nothing here asserts that a page does not exist. Ask for the platform licence, the markup applied to marketplace goods, and whether an unspent balance is refundable on termination.

The recipient can get out and the customer's route is unestablished. On the recipient side two exits are published and both are immediate or direct: an unsubscribe link that the vendor states ends all automated contact at once, and a named support address for personal information removal requests. That is more than most platforms offer the people in their database. On the customer side nothing was reachable.

No export format, no bulk extraction route, no interface for retrieving campaign, acceptance and delivery history, and no statement of what happens to records or to an unspent balance after termination. Gift acceptance history is the asset a programme accumulates and the thing that makes its reporting worth anything, so whether it can be taken out is the question that matters.

The site refuses automated access at the robots level, so this reflects what was reachable rather than an established absence. Ask for a documented export of campaigns, recipients and acceptance history, and the retention window after an account closes.

The address problem is designed out and the vendor discloses that tracking is not. Nothing ships to a guessed address: the recipient enters their own at the point of claiming, and where an item cannot reach their country they are routed to exchange it for one that can, so the two commonest physical failures are handled by the flow rather than by a support ticket.

Against that the vendor states plainly in its recipient material that because it works with thousands of merchant partners it cannot provide tracking details for each gift, and that tracking may be obtainable on request. That is a candid disclosure of a real limitation and it is worth crediting as a disclosure while recording it as a gap, because a sender running a paid campaign cannot confirm receipt as a matter of course.

The whole model also depends on one invitation email arriving, and nothing published addresses sending domain, authentication or inbox placement. Ask for the acceptance rate, the invitation open rate, and what happens to an unclaimed gift when it expires.

The buyer is named narrowly by the vendor itself and the reach around it is described loosely. The vendor tells recipients that the platform is built for enterprise use, and independent accounts place its footprint in mid market and enterprise technology companies, with the addressed teams being marketing, sales and customer success. There is no entry tier, no self serve route and no small business path, so the segment is genuine but narrow.

Geographic coverage is stated as gifts for most countries with an exchange fallback where an item cannot ship, and no country list, regional restriction or fulfilment limit is published anywhere reached, while independent reviews describe international fulfilment as a relative weakness against competitors. Campaign formats do cover distinct motions well, spanning one to one gifting, batch prospecting and numbered redemption cards for live events. Ask for the shippable country list and the fulfilment times outside the United States.