內容簡介
Hedomi Tarot 是一款免費且功能完善的 WordPress 塔羅牌閱讀外掛，提供本地閱讀功能，無需擔心功能鎖定或試用限制，讓使用者輕鬆進行塔羅牌解讀。
【主要功能】
• 塔羅牌分類與牌型文章類型
• 正位與逆位解釋
• 無限位置的牌陣建構器
• 手動與自動選牌功能
• 響應式前端與卡片揭示動畫
• 可選的 OpenAI 個性化解讀
外掛標籤
開發者團隊
原文外掛簡介
Hedomi Tarot is a free, fully functional tarot-reading plugin for WordPress. The WordPress.org build includes its local reading functionality without feature locking or trial restrictions.
Features include:
Deck taxonomy and tarot card post type.
Upright and reversed meanings.
Keywords and optional Yes/No classification.
Spread builder with unlimited positions.
Visual drag-and-drop position preview.
Manual and automatic card selection.
Optional reversed cards and configurable probability.
Secure AJAX validation with nonce and deck verification.
Responsive frontend and card-reveal animations.
Reading cards or tabbed interpretations.
Shortcode: [hedomi_tarot id=”123″]
Optional OpenAI personalized interpretations using the visitor question and the administrator’s card meanings.
Required visitor consent for AI personalization, configurable local AI abuse protection, connection test, and traditional-reading fallback.
The plugin does not include copyrighted card artwork or interpretations. Site owners must provide content they have the right to use.
OpenAI is an optional external service. Traditional readings work without OpenAI and without an API key.
External services
Hedomi Tarot can optionally connect to the OpenAI API to generate personalized tarot interpretations. OpenAI performs the interpretation on its external servers. This service is not required for traditional readings.
The connection occurs only when the site owner configures an OpenAI API key, enables AI, and an AI reading is requested. The visitor must explicitly confirm consent before the question and spread data are sent to OpenAI.
For an AI reading, the plugin may send the visitor question (if provided), spread title, selected card names, card orientation, spread position names and context, card keywords, Yes/No metadata, site locale, card meanings entered by the site administrator, and any additional AI instructions entered by the administrator. The OpenAI API key is sent in the server-to-server Authorization header. It is not exposed in frontend JavaScript. Requests set the OpenAI store parameter to false; OpenAI’s processing and retention practices remain governed by its own policies. WordPress authentication cookies, authentication keys, salts, and session identifiers are not sent to OpenAI.
When the administrator enables the optional per-visitor AI abuse-protection limit, anonymous requests use a SHA-256 hash of the visitor IP address as a temporary local rate-limit key. The raw IP address is not stored by this feature, the hash is not sent to OpenAI, and the transient expires within one hour. This rate protection affects only optional AI personalization and never blocks traditional readings.
OpenAI Terms of Use: https://openai.com/policies/terms-of-use/
OpenAI Privacy Policy: https://openai.com/policies/privacy-policy/
