Apple MacBook Compatible – Premium Black Privacy Screen and Blue Light Screen Protector– Anti-Glare, Anti-Scratch, Blocks 96% UV (Latest 13 inch MacBook Pro & 2018 MacBook Air, Black)

TOP QUALITY & EXACT FIT FOR MacBook Pro 13 late mid 2016-current – Our Privacy Filter is a perfect fit for the MacBook Pro 13 late 2016 to current date model (compare screen dimensions to 2nd photo before purchasing). Unlike other privacy screen protectors, ours has 8 layers of film that help ensure your privacy and also provides other important benefits to you. Not designed for touchscreens. Be more comfortable & secure in entering your passwords and viewing personal content. SUPERIOR PRIVACY–Perfect for open office settings, universities, financial institutions, health care providers, and corporate travel. Stop giving access to your confidential information to everyone around you outside the 60 degree viewing angle. Akamai Laptop Privacy Screen Filter helps achieve this by limiting the viewing angle of your screen to a straight position so only you can see the contents of your laptop screen while people on either side of it only see a darkened laptop screen. PROVIDES EYE & SCREEN PROTECTION – Akamai Privacy Screen for Laptops not only provides privacy but also protects your eyes by filtering out 97% UV and curbing blue light by 70%, which can otherwise have an adverse impact on your eyes. The screen filter is reversible, giving you the flexibility to choose matte or glossy – Place the matte side facing you for reducing extra glare. Our Laptop Privacy Screen also helps keep your screen safe from dust and scratches.

ASIN

B07KJT2DBY

Embedding

CLIP ViT-L/14 · 768d

Distance metric

cosine

Doc fetch

86ms·cache hitGET /v2/namespaces/amazon-products/documents/B07KJT2DBY

Similar query

48msre-embed title → /query

Doc fetch goes through Layer's Aerospike pull-through cache; cache hit served the row without touching turbopuffer. The similar query re-embeds this product's title with CLIP-text and runs a vector query — queries don't go through the doc cache, so no cache header is set.